CONTRACTS
The contract, live
The reasoning contract, live and machine-readable: the grammar every act is written under, the full record schema, and a public compile gate you can submit a record to right now. These are endpoints, not documentation. What the site describes in prose, these serve as structure.
§ 01
Contracts
The published contract
Everything an act must be is published here as machine-readable structure: the DER schema field by field, the ADS grammar, the governance conjunctions with their exact conditions, and a fully worked example record. These surfaces were verified field by field against the live system's own prompt contract. They are what the model is held to, in the form a machine can consume.
One of them is executable. The compile gate at /_functions/compile takes a DER-shaped payload from anyone, no authentication, and returns a deterministic PASS or a field-level COMPILE_ERROR. It checks structure: required blocks, the PRIMUM and Absolute Value Guard conjunctions read from typed fields, declaration integrity present as explicit booleans, signals cited and linked. It does not reason, does not call a model, and does not write anywhere. It is the admission test, runnable by anyone, against the same conditions the system holds itself to.
This layer is deliberately separate from the machine it describes. The reasoning pipeline, the ledger, and commit authority live on the system's own infrastructure; these endpoints neither call it nor are called by it. What that separation buys is a contract that can be read and tested with no access to anything: a developer can validate a record's structure against the gate without the kernel, and a crawler can ingest the grammar without an account. The specification is open for inspection and independent implementation. The kernel that enforces it in production is licensed, so the gates cannot be removed.
§ 02
Endpoints
Machine readable contracts
Start here. The system descriptor, foundations, governance constants, and the full endpoint map.
The reasoning grammar: required structure for a valid record, the ADS criterion shape, governance conjunctions, schema, and the worked example. This is the contract the model is shown.
The record specification: every field, type, and rule a Decision-Evidence Record must satisfy, with the golden example.
The governance conditions in full: both harm conjunctions stated exactly, the ILJO sequence, and how scoring is computed at the gate rather than declared by the model.
The cognitive architecture: two zones, proposer and processor. The model affirms its position; the gate holds the authority.
POST a record, get a verdict. Deterministic structural validation, open to anyone, no authentication. A COMPILE_ERROR names the specific failing field.
The machine-readable index for AI agents and crawlers, plain text, the whole contract in one fetch.