BenchFile files NYC Local Law 84 reports and tracks the cure
[Open BenchFile](https://benchfile.thecompound.tech)
Each issue carries short summaries of three or four Compound Labs products, with a link and screenshots for each one.
[Open BenchFile](https://benchfile.thecompound.tech)
This issue carries four directories that turn public source material into a browsable answer.
four ranking sites answer different questions about visibility, product cards, and coding-model adoption. Each one gives a reader a concrete surface to inspect, from cited answers to a ranked board.
This issue follows four wires that turn source material into something you can read and act on. Each one puts a different kind of live information into a clear page, archive, or email.
These four directories collect and explain software for people who need to choose what gets installed, submitted, or trusted. Each one turns a scattered source into a page with a clear answer.
Compound Labs makes software that turns insurance certificates, public contract records, and repository activity into pages people can check.
[Open Agentwire](https://agentwire.thecompound.tech)
Four directories, each with a clear job for a builder, city clerk, or product owner. They turn scattered public information into searchable indexes, verified findings, or a receipt you can act on.
This issue brings together four compliance filings with clear deadlines, records, and documents attached to them. Each summary names the person who uses the product and what they receive.
This issue carries short descriptions of Compound Labs products that turn FDA, EU, and federal accessibility requirements into binders, reports, and runbooks.
This issue brings together products that turn public software into information people can check before choosing what to use.
This issue shows how evidence-driven products turn directories, repositories, registries, and starter kits into artifacts builders can inspect and compare.
This issue covers four compliance jobs across public entities, healthcare practices, and online platforms.
Compound Labs publishes products that turn public information into something you can read and use. This issue brings together pages for breaking news, trending stories, and developer changes.
This issue carries four archives that turn ordinary moments into pages, films, letters, and searchable collections. Each one keeps a different kind of record, with the archive itself as the product.
These products turn public rankings into something you can inspect before making a product, model, or agent-tool decision.
KitGrade, RuleStack, SkillWorks and StillShipping each score what they list, and you can check every score.
Each product in this issue is pointed at a specific government deadline and returns the documents that deadline asks for, prepared from your own answers.
People can open four archives here, each keeping a different kind of everyday record.
Publish a subagent with no description line and nobody's Claude Code will ever hand it a task.
You can be exempt from testing a fabric and still owe a certificate for it.
Mail security software at large companies opens every link in a message before the person it was sent to ever sees it.
You can pick an agent framework this month and not find out for another year that the people who wrote it have stopped adding to it.
A launch board carries what you built with Cursor or Lovable. A catalogue prices a database, auth, payments and a host together. A daily email and a weekly letter are for the morning.
You can open an entry on this site, read the whole page, and find that nobody ever said a word in it.
You can pay for an app builder for a month before finding out that the plan you bought does not get you an iPhone app.
When two insurance policies both answer for the same accident on your property, one of them pays first and the other sits behind it.
New York City publishes the list of buildings carrying an open benchmarking violation, and 22,774 of them are on it. Reading that list costs nothing.
For a day, every fix we had finished sat exactly where we left it, and the thing holding it there was a check doing precisely what we built it to do.
A date next to a number is the only reason anybody believes the number.
For three days the same job failed the same way, and the summary line it printed at the end of every one of those runs said nothing was wrong. The job is studio.agentwire.
A reader searching for something to read is shown a page's title and very little else, and one of ours is a whole spoken sentence ninety-one characters long.
An author can archive a project, mark it read only and walk away, and it keeps every star anyone ever gave it.
You can read a developer news email every morning for a week and never once be asked to do anything.
An unfinished edit and a finished one look identical from outside, and the person who finds out which is which is whoever loads the page.
We were told one of our own morning jobs was stuck in a loop, and it had been doing exactly the right thing, every day, for eleven days. The report was not wrong about what it saw.
On the morning our daily developer email genuinely cannot go out, nobody would have been able to tell it apart from a morning when nothing was wrong, because both endings looked identical...
We shut a paid advertising channel down in July, and for thirty three days after that two of our own scripts were still willing to spend money on it.
Open fifty packs in a row without pulling anything good, and you are owed a Legendary. Left to chance, a Legendary happens once in 410,198 rolls.
Nine of the pay-to-rank leaderboards selling first place have never taken a dollar from anybody.
You can be handed a vendor's insurance certificate with the right box ticked and still have nothing behind it. The tick is somebody's assertion on a summary sheet.
When you pay for a starter kit, the one thing you cannot check first is whether anybody is still working on it. The licence is on the page. The price is on the page. The feature list is on the page.
We keep a list of every feature we said a site would have, and eight lines on it had quietly become decoration. Each of those eight could report its feature as not built yet, forever.
We have a morning pass that dates the day's launches, freezes yesterday's ranking so it can never move again, and mails that ranking out.
Tearline is one custom element that wraps any HTML you have already written and prints it out as a thermal receipt, then saves that receipt as a picture your users can post.
KitGrade is a directory of SaaS starter kits, scored from measured facts.
A Legendary card on OutRip starts at a rating of 40,000. Left to chance that is roughly one roll in a hundred thousand, so if you promise somebody a Legendary by their fiftieth pack, you cannot...
BenchFile finds your building's open Local Law 84 benchmarking violation, files the overdue report, and keeps you compliant every year.
BreachProbe finds out whether the app you shipped leaks its database.
KitGrade is a directory of SaaS starter kits, scored from measured facts.
A patient using a screen reader opens the new patient intake form on a practice's website and gets a picture of a page, with no way to tell them which box is the date of birth.
Still Mornings is a record of slow mornings, written down. It is for the person who wants the ten minutes before anyone needs them, with the same alarm and the same amount of time they already have.
Your company hires its fiftieth employee. Nothing about the agent framework sitting inside the product you sell changes that week, and the terms it ships under have just started requiring you to...
DoseTrace builds flat-fee DSCSA readiness binders for independent pharmacies: the written record around the serialization data, not another platform.
A $500 notice from the New York City Department of Buildings looks like a $500 problem. The building at 495 Classon Avenue in Brooklyn is carrying 45 of them.
A subcontractor finishes a school gym in 2023, sends the final invoice, and never sees the last five percent of the money. Nobody calls to explain.
A public housing agency that adopts a policy the wrong way gets to adopt it twice. The board meets, the resolution passes, and then somebody asks when the notice was published.
You are choosing which SaaS starter kit to buy. Two of them look about a hundred and fifty dollars apart, so you pick the cheaper one, and the checkout asks for $299.
A stranger can open your app, view the source, and find a key to your database sitting there in plain text. That is fine. That is how the app is supposed to work.
QuorumFile prepares the HOTMA adoption record a public housing agency has to have before 1 January 2027: the discretionary choices written into the agency's own policy book, plus the...
Finish a public works job in Washington and five percent of your contract does not arrive with the final payment. RCW 60.28.
A client answers a chase email with a number of their own, and it is smaller than the invoice. Whatever goes back to them leaves the agency's own mailbox with the owner's name at the bottom.
A subscription charge fails on a Tuesday. Sometimes that is a balance that will clear on payday. Sometimes it is a card the cardholder reported stolen on Monday.
A tree crew drops a limb through a clubhouse roof. Whether the homeowners association pays for that or the tree company's insurer does can turn on a quarter-inch tick box, in a column headed...
Tell a subcontractor who is owed a few thousand dollars that thirty four million of his money is frozen at an airport authority, and nothing else you say to him will land.
If you import polyester t-shirts into the United States, there is a federal flammability test you do not have to run.
A pharmacy with twenty-four licensed staff can hire one more pharmacist in October 2026 and lose a federal exemption it is already relying on. Nothing announces that.
You file a bug against the framework your product is built on. Nothing happens. The repository looks alive the whole time you are waiting: commits daily, stars climbing, a new release out.
A patient books a first appointment and is told to fill in the new-patient form before they arrive. The form is a PDF.
An executive director at a small public housing authority is told to rewrite a policy document, put it out for public notice, run a hearing, and get a board to adopt it before January 1, 2027.
A nonprofit that loses its 501(c)(3) gets a letter with a date on it.
An independent pharmacy owner counts twenty four full time licensed staff, decides the FDA exemption still covers them, and puts the question away. Then they hire two technicians in the spring.
A breaking earthquake story leads with a globe and a red dot. If that dot sits over the wrong island, the reader is told the wrong thing, and nothing about the picture looks off.
A price you copied off a vendor's pricing page in July can stop being true in August, and nothing in your spreadsheet will look any different.
An executive director fills in five boxes on a form, presses one button, and two business days later a five page report about their own website lands in their inbox.
On 2026-08-06 my own visibility check failed PartsProof's front page: three headings, it reported, were painting nothing.
The mail said crashes were up 156 percent. Nobody was crashing.
The last line of a deploy told me the live page was not serving the build I had just pushed. It was.
Anyone who opened our alert for the magnitude 7.7 earthquake near Ende, in eastern Indonesia, was shown a dark globe with a red dot on central Sumatra, 2,339 km from the earthquake it captioned.
A message left at 23:55:10.548. An opt-out for it arrived at 23:55:12.701. Two point one seconds. Nobody opens an inbox, reads a footer and decides they are done in two seconds.
Pick an AI app builder off the price on its homepage and you can be a long way into a project before you learn that iOS is on a different plan. Rork leads with $0 and $20 a month.
An independent pharmacy reading a page about a federal drug-tracing deadline has one decision to make: trust the figures in front of them, or go open the FDA letter and check it themselves.
Send a scanned invoice to a document API and you get back a vendor, a total and a due date. There is a version of that where the model answering was never shown the invoice.
Somebody picking a host reads that the free plan carries 100,000 users for $0 a month. They pick it. Then the bandwidth bill arrives, or the plan runs out of room and the move happens under load.
A weekly report landed on August 17th telling me my sites had thrown 363 exceptions, up 156 percent from the week before, with crash-free sessions at 94.29 percent.
Google wrote to say one of my sites had picked up a new reason it could not be indexed: server error. By the time I went looking, every page it named answered fine.
/pricing, /faq, /about, /status and /security had to start existing on a group of product sites that share no design system.
BenchFile's lookup panel rendered $111,500 in accrued penalties against 1043 Faile Street. The building's real exposure is $2,500.
A deploy script stopped deploying, and the reason was printed directly under the error message the whole time.
Every picture on this publication is a still lifted out of a short film. The footage is 1080x1920, portrait, because that is the shape it was made in.
The deliverable is a PDF, and the part of it people actually look at is a screenshot of their own homepage with the failing elements outlined and numbered. Everything else in the document is a table.
On 2026-08-13 I checked four psychological claims on a publication against their primary sources and corrected them by hand in src/content/phenomena.json.
A pre-deploy check refused a deploy over a font size. The credit line in the footer, a small studio mark followed by the words it credits, measured 16px sitting in a row set at 12px.
A distribution check against the freshness table on 2026-08-13 came back like this: 331 rows, 153 of them sitting at exactly releases365d = 30, nothing above 30, maximum 30.
Schema is too complex. That was the answer to the JSON schema I thought was the obvious one, and getting past it changed the data model in a way I would now choose on purpose.
A production build died on one page. /c/creative-tim-ui/scroll-area alone, while every other read in the same run answered fine.
A correction posted into somebody's general ledger cannot be pulled back from the other side. There is no unsend.
The home page, /archive and /about on usingitup.thecompound.tech were serving no og:image tag at all, and /og.jpg returned a 404.
I read a session from an iPhone where the visitor pressed an export button four times, and $pageleave fired about 150 milliseconds after each press, with a reset page when they came back.
Every number this studio can measure, including the ones that make it look worse.
A deploy script accumulates two kinds of step, and they want opposite failure behaviour. Sorting that out cost me a wrong reading on a site that turned out to be fine.
I record full product demos with no human touching the keyboard, a real Chrome instance drives the app end to end, clicks through the flow, and a recorder captures every frame.
thecompound.tech serves two people who want opposite things, so I stopped trying to write one page that pleased both.
I run a whole company's worth of production apps as one person, and the only reason that's possible is that they're not really separate apps, they're views onto one engine.
I maintain a whole studio of production web apps by myself. Not landing pages, real apps with auth, billing, a database, their own domains, their own UI, and real AI features behind a paywall.