OctoView LabsThe laws we build under
Topos is not a collection of features. It is a small set of laws, enforced mechanically, that together make an autonomous system answerable. We publish the laws and keep the machinery closed. The laws are the product; everything else is implementation.
1. Nothing exists unless it exists in the ledger
There is one append-only record, and it is the only source of truth. Every dashboard, report and status view is derived from it and can be rebuilt from it. A fact that lives anywhere else, in a chat transcript, a comment, or someone's memory, is not a fact the system knows. This sounds austere until the day someone outside the engineering team asks what happened, and the answer can be replayed rather than reconstructed.
2. Operators sign policy acts; machines sign facts
The machine records what it did. It never grants itself permission to do it. Widening a scope, overriding a limit, approving a design, changing a rule: each is a policy act, and each requires a named human's signature before it takes effect. The signature is a durable record, not a checkbox. Accountability is a property of persons; a process cannot carry it, and a system that pretends otherwise is hiding a person somewhere.
3. "Done" is a verdict, not a claim
The agent that performs work does not get to certify it. A separate verifier re-derives the result; adversarial review attacks designs before they are built. A claim of completion must carry evidence, a content hash, a re-executed test, a reproduced refusal, or it is turned away at the boundary. Turned away, not corrected: the system refuses to record what cannot prove itself.
4. Refusals stay on the record
Most systems hide their losses. Ours is architecturally required to confess them. Every claim refused, every override, every retraction is preserved alongside the successes. That is what makes the record credible. Evidence that only ever says yes is not evidence, and an audit trail with no failures in it has been edited.
5. A gate that cannot catch a planted crime is theater
Every enforcement mechanism must periodically prove it can fire, by being shown a known violation and refusing it. We call these canaries. A test suite that passes under any mutation of the code it tests is not a test suite; a watchdog that reports health without measuring it is worse than no watchdog, because it converts an unknown into a false reassurance. Verification machinery is held to a higher standard than the code it judges, because it is the part everyone else trusts blindly.
6. The referee is locked against the players
The agents that work under the rules cannot edit the rules. Gates, validators and enforcement configuration are constitution-locked: changing them requires an operator's signed approval, checked mechanically at the door. A gate an agent can weaken in order to go green is not a gate. This is the difference between a system with guardrails and a system with suggestions.
7. Every declared thing must have a reader or an expiry date
Fast-built systems accumulate machinery that is declared but never connected: rules enforced by nothing, configuration read by no code, checks that run nowhere. Unconnected code does not crash. It agrees with you, which is why nobody notices. Our rule: anything declared must either have a consumer, or carry a signed date after which the build fails until someone renews the deferral or wires it in. Unfinished machinery is allowed. Unfinished machinery that is silent about it is not.
8. The only tractable prediction is survival of the recorded past
A machine that alters itself must predict its own future behaviour, and simulating futures regresses infinitely; settlement engineering learned this decades ago. So we point the simulation backward: a proposed change must survive replays of every recorded failure before it is allowed to exist. The ledger makes this possible; it already holds everything that ever went wrong. The full argument is in the essays.
9. Assumptions stand trial
Every design must name the assumption it is compensating for, and say when that assumption was last tested. Adding a third mechanism to protect a component requires first arguing why the component deserves to survive. This keeps the system honest about a failure mode that pure discipline never catches: machinery accreting around a belief nobody has checked in months.
10. The human is the constitutional layer
Under all of it, one person or a small set of persons holds signature authority, and the system is built so that authority cannot be delegated away silently: not to an agent, not to a process, not to a default. AI does the hands. The professional keeps judgment and liability. We believe this is not a transitional arrangement to be engineered away, but the permanent shape of trustworthy autonomy in regulated work.
What this costs
These laws make the system slower to build and bruising to operate. Work gets refused. Days end with zero shipped lines and a longer defect list, because the machinery went looking. We consider that the point: the alternative is a system that looks healthy from every dashboard while quietly not working, and in the industries we serve that alternative eventually has a court date.