DILIGENCE / ARCHITECTURE

Conceptual architecture before temporary implementation.

This page describes the stable end-state boundaries. Versioned build records describe whichever technologies currently instantiate them.

Intake and trust classification.

Adapters snapshot sources, record hashes and provenance, classify trust, normalize records, and place changes into queues. Change intake and command execution remain distinct concerns.

Trace-first acquisition and verification.

Candidate claims and relationships are proposed from code, contracts, tests, traces, diffs, artifacts, and cited worker support sets. Acquisition records provenance and support edges before graph structure is trusted. Agent-generated structure remains unverified until claim-specific evidence supports it.

Write ownership stays explicit.

The authority engine admits scoped changes to the Ratified Intent Graph. Verification processes update claim state in the Evidence-Backed Reality Graph. Reconciliation writes current orders to the Active Execution Graph. Every consequential decision and side effect appends to the Immutable Evidence and Command Ledger. No worker or evidence record writes ratified intent directly.

Execution routes locally or remotely.

A normal command enters the proxy and policy router. Lightweight permitted work can remain local; heavy builds and tests can run in isolated remote capacity. Both routes return an immutable evidence envelope before a current-epoch manager gate can perform an official side effect.

The control loop has stops.

Contradictions, missing support, stale epochs, policy denial, poisoned evidence, exhausted repair budgets, repeated failures, and non-converging plans stop or quarantine advancement. Idempotency keys prevent a replayed event from duplicating an official effect.

These are intended end-state boundaries; dated Build Records show which behavior has been demonstrated.

Boundary-to-record map.

Each conceptual box maps to normative intent and a dated implementation posture.

Intake and trust classification

Specification
Intended Open normative section
Build Record
Unproven Open dated record

The predecessor reported adapter and provenance behavior, but no immutable source revision or artifact is available to verify this boundary.

Trace-first acquisition and verification

Specification
Intended Open normative section
Build Record
Unproven Open dated record

The recovered material describes this end-state boundary; it does not include a reproducible graph-acquisition artifact.

Write ownership

Specification
Intended Open normative section
Build Record
Unproven Open dated record

The predecessor reported manager-owned state changes, but the private source and test artifacts needed to demonstrate enforcement are unavailable.

Local and remote execution routing

Specification
Intended Open normative section
Build Record
Unproven Open dated record

The predecessor reported a local proxy and remote stub; it does not supply reproducible evidence for the intended remote build plane.

Stop conditions and idempotency

Specification
Intended Open normative section
Build Record
Unproven Open dated record

The normative stop rules are reviewable, while their implementation and failure behavior remain unverified without source and run artifacts.

Evidence posture.

Intended behavior, demonstrated records, and unproven claims remain separate.

Intended

The ownership, routing, and stop boundaries on this page are normative end-state architecture, not a current-stack inventory.

Inspect the record

NEXT RECORD

See what is built