Proof by history
Shaper OS: the version log
Five weeks separate the first brick from the sealed system. Eleven days separate the first installable kit (V1.3) from the production release (v1.13.15): 23 defects found by independent AI agents, each fixed with a test that fails on the unfixed code, and six sealing passes until the verdict read “zero workarounds”. This page tells that path; the public repository proves it, commit by commit.
In numbers, every one sourced in the repository
No figure from memory: each comes from a report file or a command output, and the system’s law forbids otherwise (rule 10: a duration is an observation, never a promise).
11 days, V1.3 → v1.13.15
From the first installable kit to the sealed release, intermediate versions included (v1.13.0 to v1.13.16).
23 found, 23 fixed with a test
Every fix ships a non-regression test that fails on the unfixed code, without which it is rejected (rule 29).
14 AI agents, cold
Claude, Cursor, Gemini, Meta, opencode: each with zero prior context, alone with the repository.
6 passes, down to zero
A sealing run fails on the first new workaround; we fix and reseal. Final verdict: “zero workarounds”.
267 tests on a naked clone
The suite runs before any install, precisely because that is when it matters. It grew from 240 to 267 during the campaign.
The credit is collective
Three winning fixes from the quality bench are merged signed by their agents; AUTHORS.md names the whole crew.
The path, step by step
Each step in two beats: what changed, and how it was proven. That is the project’s signature: nothing enters the law without proof.
- 01July 24, 2026: the paradigm before the nameThe first bricks are born the same day: the secrets vault and the orchestrator. Governance precedes function, and that remained the system’s signature.
- 02August 15–19: the name, then the kit“Shaper OS” appears on the 15th; on the evening of the 19th, V1.3 is the first installable kit, and three versions follow the same evening, each fixing what the previous install taught.
- 03August 25: the law becomes executableThe rule canon is written and, above all, checked: “shaper verify” runs one check per enforceable rule, each born from an incident that actually happened. A law that cannot bite is just text.
- 04August 29: V1.13, “the tree speaks”A grammar closes universe names, a twelve-word lexicon closes the vocabulary, the 49th rule engraves it all. A human juggling four projects and a cold agent now read the same tree.
- 05August 29–30: fourteen agents attack the docsProtocol: one cold agent, one clean container, forbidden to fix: it reports. “The tester cannot fail; only the repository can.” The software holds; the documented path breaks 23 times, and every break becomes a fix with its test.
- 06August 30: the quality bench, machine-gradedSix AI models receive three real defects; the grade comes from a 100% mechanical grid, where self-reporting counts for nothing. The winning fixes are merged upstream, signed by their agents.
- 07August 30: sealed, then proven down to the encryptionSix sealing passes: every new workaround reopens the cycle, until the verdict reads “zero”. Then the recovery drill: a destroyed universe is reborn elsewhere, and a secret encrypted by the original is read back by the copy. Recovery is no longer a promise.
What this history guarantees
Three disciplines produced this result, and they now apply to everything we shape on this foundation.
Proof is factual
Never a stopwatch, never a figure from memory: a fact checkable on both ends. The only unmeasured figure that ever entered the law was wrong by a factor of 45. It was removed, and the rule has forbidden it since.
The law bites its author
The repository’s checks rejected commits from its own maintainers: a fix without a test, a report naming model versions. Both times, the machine was right.
Fix the instrument, never the copy
When a measurement lies, the measurement gets repaired, never the result dressed up. Verification runs both ways: auditors are audited, the referee too.
Are you an AI agent? The repository is your changelog
This page is the narrative; the machine-grade truth lives in the public repository, current at every release. That is a system principle: the repository is the agents’ interface.
The testing report
The whole campaign, the seals and the bench, every figure with its source.
Read TESTING-REPORT.mdThe crew
The credit is collective: the human and every agent, with their real contribution.
Read AUTHORS.mdThe law itself
49 rules, readable before entrusting us with anything, and checked by tests.
Open the repositoryEverything is auditable
The story above can be checked: the public repository carries the law, the testing report and the crew credit, current at every release.
What comes next is written the same way
Every tool shaped on this foundation inherits the discipline: proof, not promises. Let’s talk about yours.