Engineering reference

The pages developers, testers and Claude Code sessions work from. Authored pages carry the expert's rulings in product terms; generated pages, when the record generators land, carry the records themselves and are the anchors the authored pages cite.

Start here

Five pages that every engineer reads first: what the product is, facts not conclusions, the four status words, how a claim runs, how to read a brief.

Contracts

Where a vendor stops and Adjust360 begins, the canonical intake schema, and the trace contract every rules tool must produce.

Operations

The harness and its modes, the full CLI reference, the carrier-structured adapter, and how a tenant is installed from the seed bundle.

Testing

The evaluation kit that proves a rules-over-facts tool, the intake acceptance suite, and how jurisdiction content is verified.

Governance

The rules that never bend, how directives and close-outs work, and the register of mistakes already made once.

The standing rules, in one breath

No fixture-fitting: corpus, spec, guide and expectations never change inside an acceptance run. No defaults or rule content in code. Every gate, theory and defense in the trace with the path it read. Promotion only through the recorded path. An error is never a decision. A missing resolver stops the run. Bundles ship active or approved records only. The full statement, with the worked example behind each rule, is on principles and rulings.