System forms

Truth systems take
the shape of their work.

The architecture stays consistent. The domain changes what counts as evidence, which facts must move together, who reviews the change, and which read surface is worth keeping.

Shared grammar

The domain changes. The discipline does not.

  1. 01Evidence

    Preserve what a source can actually establish.

  2. 02Governed change

    Propose an exact, attributable transition.

  3. 03Current account

    Advance only after the right review.

  4. 04Bounded read

    Show each reader what they need to act.

Three durable patterns

Different domains. Different useful forms.

These generalized patterns were distilled from first-party systems. They explain what is possible without turning private state into a public case study.

01

What needs attention now, and what changed?

Coordination truth

A living account between changing outside intent and operating reality.

Use this form when requests, plans, and reported outcomes arrive through imperfect channels and one responsible person must reconcile them before others act.

Evidence
Messages, spreadsheets, orders, system extracts, call notes, and operator reports.
Governed change
An attributable change set reconciled against the whole account and reviewed by the responsible operator.
Current account
Current obligations, operating state, disagreements, unknowns, and the reason each fact moved.
Useful read
A focused worksheet or communication package containing only what its reader needs to decide or report.

GuardrailThe outside surface is a bounded read, not a window into the full working system.

02

What happened financially, and is the period closed?

Financial truth

An evidence-backed ledger whose corrections and closes remain attributable.

Use this form when source documents must become a balanced current account and prior periods must remain stable without hiding later corrections.

Evidence
Receipts, invoices, statements, contracts, exports, and other bounded financial sources.
Governed change
Balanced, dated journal entries that cite evidence, followed by an exact reviewed close for the period.
Current account
The ledger projection, open reconciliation, explicit unknowns, and preserved close packets.
Useful read
Trial balances, financial statements, account detail, and a close narrative a reviewer can inspect.

GuardrailAn AI peer can prepare and reconcile; acceptance remains bound to the exact entries and balances under review.

03

What remains true across changing projects?

Organizational truth

A slower account of identity, authority, relationships, decisions, and open questions.

Use this form when important conclusions cross project boundaries or outlast the repositories and conversations that first produced them.

Evidence
Official records, direct decisions, owning repositories at exact revisions, and external statements within their authority.
Governed change
A bounded domain record with citations, uncertainty, and an exact before-and-after change reviewed as one transition.
Current account
A compact selection of accepted organizational records with their fuller meaning and history still recoverable.
Useful read
A clear human map and compact AI context for identity, authority, portfolio relationships, and unresolved questions.

GuardrailIt records stable consequences, not a second copy of product status, infrastructure, or operational detail.

A pattern is not a template

A real implementation must earn its own boundaries.

Each system still has to define its domain, source authority, reviewer, invariants, correction path, and failure posture. The reference architecture supplies the grammar, not those answers.