- Entry date
- 1 June 2026
- Category
- Method
- Access
- 🔓 Public
A patent only gets filed if a grep on the real codebase actually finds the claimed code. That one rule is the whole ledger, in miniature.
- v1.6
- the ledger schema version, in NovaOS terms
- grep-confirmed
- the bar for filing any patent claim against real code
- 32 → 1 RTX 3090
- a corrected fantasy, propagated to every sibling project
- empty, flagged
- how an empty model slot / zero checkpoints gets recorded
Honest evaluation
The ledger's rules aren't just stated policy — the record shows two of them (the GPU correction, the empty-checkpoint flag) actually catching something real.
The evidence — full reasoning behind the verdict
Verdict: proven. The ledger's specific, checkable rules — grep-confirmed patent filings, no calling a partial build "shipped," flagging an empty checkpoint rather than hiding it — aren't just stated as policy; the record shows two of them catching something real: the 32-GPU correction, and a separate project's own file stating plainly that its model slot is empty.
It landed here because each rule is mechanical rather than a matter of judgment. "Does a grep on the real codebase confirm this source path" is a yes/no question, not a subjective call, which is exactly why it can be enforced consistently and why it caught what it caught. The 32-GPU correction wasn't a case of someone deciding retrospectively that the number "felt inflated" — it was a rule (verify the claim against reality) doing its job.
The honest limit is structural, and the file names it itself: a self-imposed ledger is only as good as the team's willingness to keep enforcing it, and the same team that builds the record also audits it. What would prove or disprove it further is exactly that limit being tested — a claim slipping past the grep check, or an empty-slot situation going unflagged somewhere in the portfolio, would show the rule is honored in the cases audited here but not universally; catching a third example elsewhere in the archive, under the same rule, without prompting, would extend the proof.
Every fast-moving technical record eventually has to answer an uncomfortable question: did that actually happen, or did someone just write it down like it did? This is the schema built to keep the answer honest.
What it was
A ledger format — schema v1.6 in NovaOS terms — that runs across the whole 2026 portfolio, enforcing a small number of specific, checkable rules: a patent claim is filed only if a grep against the real codebase actually confirms the source path it claims to describe; a spot value is never labelled an exponential moving average unless it genuinely is one; a partial build is never called "shipped"; an empty model slot or a missing checkpoint file is flagged in the record, not quietly omitted.
What we built
ResearchThe clearest working example is a correction, not an invention. A council review caught a fantasy in the record — a claimed 32×RTX-3090 GPU federation — and struck it, replacing it with the true figure: one single RTX 3090, alongside an honest 12-15 month timeline and a stated capability claim of "70-80% of a top-tier model on routable tasks" instead of an inflated one. The correction didn't stay local. It propagated to every sibling project that had inherited the same inflated assumption.
A second example shows the same discipline applied to an absence rather than an inflation: one project's own record states plainly that its model slot is empty — zero checkpoint files for a named training run — flagged as a launch-critical risk on the record, rather than glossed over or left implicit.
What we learned — including the honest negative
This ledger is offered as a portable, open standard, on purpose — worth publishing rather than protecting, because the credibility it buys is worth more shared than hoarded. Grep-confirmed patent filings, in particular, are a specific defence against a real, named risk: filing a claim that sounds like it describes shipped code when it doesn't.
The honest limitation is structural: a ledger like this only works if someone actually enforces it, and this one is self-imposed — the same team that builds the record also audits it. That's a real constraint on any self-audited system, and naming it plainly is more useful than pretending the ledger is somehow self-enforcing.
Where it went / status
Active and applied across the current portfolio, most visibly in the 32-GPU correction's propagation to every project that had inherited the error. It runs directly alongside, and feeds into, the council-and-gate decision process — the ledger keeps the record honest; the council decides what to do about what the record says.
What is still open — kept visible
The honest edges, next to the wins. This is what turns 🔬 into 🟢 — honestly.
- A ledger only works if someone actually enforces it — this discipline is self-imposed and relies on the same team auditing itself, a real limitation of any self-audited system.
- It is offered as an open standard on purpose, not protected as IP — the trade-off is giving up a possible differentiator for wider, sooner trust.
- The corrections a ledger like this catches are only as good as how consistently it's applied across every sibling project, not just the one under direct review.
Proofs & sparks
We demonstrate rather than assert. Each ✅ proof is a visible result with a hard figure.
- The register's own honesty audit34 of ~133 grep-confirmed · 0 filedof ~133 claim rows only 34 have a grep-confirmed source file, one "paper tiger" was caught, and none are filed — the honesty machine catching itself.
- The honesty is the flex — The showcase is "four capabilities felt, eight lanes proven," every cell tier-tagged with its gap visible — the honesty is the flex.
Where this connects
Sources
- vocabotics project audit — Honesty Ledger schema v1.6 (grep-confirmed patents, the 32-GPU correction), Jun 2026vocabotics internal project history · as of June 2026