Documentation is not after the journey. It is alongside it — read it slowly. Three products, three short shelves: each one a careful description of how a tool moves, what it records, and what it will not do without your say-so.
Each entry is a short, dated note. Long enough to be useful; short enough to be read before the next meeting. Tread carefully — the notes are versioned.
A handful of ideas show up in every product — the same chain of logic, the same canonical language. Read these first.
Every product carries an append-only, hash-chained audit. Identical payloads produce identical hashes under RFC 8785 canonical JSON — across Rust, Python, and WASM.
Every finding cites the rule it fired on, the input that triggered it, and the confidence assigned. No black-box verdicts.
Identity is a principal with scopes; access is a role with permissions; everything is logged with the principal that performed the action.
Disclosure, redaction, and classification rules are versioned, signed policy bundles — not application code. The bundle is itself audited.
Across Redline and Fieldbook, obligations are classified by modal verb — shall, must, should, may — with statutory basis and confidence carried along.
Privileged actions — first-of-session reads, bulk exports, overrides, reclassification — require a second factor and emit a dedicated audit event.
