Compound Labs
Get the newsletter
THE STANDUPAnthropic fixes Claude 5.1 error spikesERROR SPIKES, FIX DEPLOYEDCOMPOUND MASTODONSkillWorks records inactive files beside their roster status22 INACTIVE FILES STILL LOADCTXWINDOWContext Window tracks AI lab changes and filters their evidenceFILTERS KEEP EVIDENCE TOGETHERAGENTWIREmicrosoft/agent-governance-toolkit - AI Agent Governance ToolkitPOLICY ENFORCEMENT FOR AI AGENTSCOMPOUND FACEBOOKCompound Portfolio restores its sweep after a missing module stops desk dataSWEEP RESTORED, DESK DATA WRITTENBLOCKDEXBlockDex shows no destination for captured rows with rejected slash names31 ROWS, NO DESTINATIONCONTEXT WINDOWOpenAI adds 1024p image pricing: $0.50 and $0.251024P IMAGE, $0.50 AND $0.25COMPOUND BLUESKYCompound Labs renamed job labels so job-run finds breaker stateBREAKER STATE, NOW FINDABLECTXWINDOWContext Window tracks document changes but failed mobileMOBILE WORKFLOW, ONE COLUMNAGENTWIREMineDojo Voyager: Open-Ended Embodied AgentOPEN-ENDED EMBODIED AGENTFOUNDER BLUESKYdeploy.sh now fails false Vercel production landingsFALSE LANDINGS NOW FAILCOMPOUNDlast known fixes redirect tracking after migrationSTUDIO SOURCES NOW SAY COMPOUNDCONTEXT WINDOWOpenAI adds sora-2-pro pricing720P VIDEO, $0.15, $0.30FOUNDER LINKEDINdeploy.sh now stops failed promotes from marking production landedFAILED PROMOTES NO LONGER LANDUSINGITUPUsing It Up records a receipt fixing a wobbling wooden tableONE RECEIPT, TABLE STAYED LEVELCOMPOUNDpnpm v12.4.2POSIX BIN SHIMS REPLACEDFOUNDER PEERLISTCompound Labs' deploy runner rejects failed promotesFAILED PROMOTES NO LONGER LANDTRUSTDESKTrustDesk fixes host migration redirects while keeping /api/ outOLD HOST, 308; API STAYS LIVE
Independent product R&D labFounded and run by Isaiah Kim, @kyisaiah47Newest commit Sep 16, 2026, AgentwireNewest writing Sep 16, 2026Site changelog Sep 16, 2026
Compound AI OpsCOMPOUND X6 September 2026

CRA reporting starts Sep 2026; $750 pages file every dated claim

CRA reporting starts Sep 2026; $750 pages file every dated claim

BenchFile finds your building's open NYC benchmarking violation and files the report that clears it

BenchFile finds your building's open Local Law 84 benchmarking violation, files the overdue report, and keeps you compliant every year. It is for a New York City building owner or managing agent with a property over 25,000 square feet, which is where the city's reporting duty starts.

You type the address. Back comes a panel naming the violation number from the city's own record, the owner and floor area from the property file, what has accrued so far, and the date the next $500 notice posts. Then we file the overdue report through ENERGY STAR Portfolio Manager, request the utility data authorisation on your behalf, and file it again before 1 May every year after that.

$149 once to clear the violation that is already open, then $49 a year to keep the building filed. For a covered building with nothing outstanding, the annual line alone is $49. Stripe charges both, and neither is a quote.

Watch the BenchFile, Clear your benchmarking violation, and keep it clear demo

The $500 does not stop at one

The city's penalty is $500, issued quarterly until the report is submitted, up to $2,000 a year. It does not let one notice grow. It issues a new one, dated 1 May, then 1 August, then 1 November, then 1 February, which is why a long delinquent building carries a stack of separate violation numbers instead of one old one.

The $2,000 ceiling is counted for each building. A single tax lot can hold more than one building, and every one of them is on the hook separately.

BenchFile penalty payment guidance page with numbered steps for resolving an overdue benchmarking report, Specific, actionable process (LE94 benchmarking) with numbered steps users can follow directly.
BenchFile penalty payment guidance page with numbered steps for resolving an overdue benchmarking report, Specific, actionable process (LE94 benchmarking) with numbered steps users can follow directly.

Eleven notices in a day, four quarters running

Read out of the city's open violation table, dataset 855j-jady, on 2026-08-27. One tax lot in Queens, counting only the benchmarking notices still open against it.

Issue dateNotices still open on that one lotIssued that day
2018-02-0211$5,500
2017-11-0211$5,500
2017-08-0211$5,500
2017-05-0211$5,500
2019-05-021$500

Same lot, same owner, one calendar date, eleven notices. By the 2019 quarters the still open count is down to one, so ten of those addresses were dealt with and one was not.

Why the check asks the city to do the counting

A page of results is not a count. Our lookup runs two queries against that table: one for the notices a person can read, capped at 25, and a separate count over every open notice matching the building. The money comes off the count. One Brooklyn address in that table carries 45 open notices, which is $22,500 and is nine pages past where a reader would have stopped.

Each notice is priced flat at $500, because it is a charge that has already been issued rather than a meter still running. The panel prints the violation numbers alongside the total, so a managing agent can lay them against the notices already on the desk and see which ones match.

Check your building: https://benchfile.kynth.studio/kd?utm_campaign=kynth

---

One shipped product, taken apart, once a month. What it does, what it cost to build, what the pipeline behind it looks like, and what the numbers did, read off the repository and the live site, not written from memory. Join the list.

What each account said

Cyber Resilience Act reporting starts 11 September 2026. Your page will print that date long after it moves. Landing in 3 Days is one production page, designed, built and deployed. You pay $750, and we file every dated claim with its source. You get the page and the source behind every date on it. When a deadline moves, you can see which line on your page is now out of date and fix that one, without reading the whole thing again to work out where the number came from. #software
X