K06 assurance and procurement architecture

Assurance Dependency Graph

Direct answer

The K06 graph prevents a current assurance claim from surviving when mandatory evidence becomes stale, unavailable, invalid, revoked, superseded, or defeated. Its reference evidence is synthetic and does not describe a live facility.

Stable record: K06-PAGE-ASSURANCE-GRAPH
Claim status: PROJECT TECHNICAL PROPOSAL
Last reviewed: 2026-08-16
Research cutoff: 2026-08-16
Source type: GOVERNED PROJECT KNOWLEDGE
Currentness: Current for release 2.1.0; external sources require periodic revalidation.
Correction state: No unresolved public correction recorded for this release.
Machine record: Static JSON record

Authority and evidence boundary. K06 publishes reference architecture, source review, machine-checkable dependencies, procurement scope, and test-evidence formats. These records do not certify a facility, award a contract, authorize an operation, prove deployment, establish current operation, or transfer regulatory or command authority.

Readable layered dependency map

The visual order is deliberately linear rather than radial: top claim → assurance claim → control or contained test → evidence. No single technical fact is allowed to prove every other status.

Top claim

1 records

One bounded mission-and-safety proposition

Assurance claims

10 records

Authority, separation, autonomy, physical protection, power, cooling, recovery, and evidence

Controls

32 records

Vendor-neutral requirements with qualified source mappings

Contained tests

14 records

Non-actionable evaluation scenarios inside declared safety envelopes

Evidence

51 records

Current, stale, unavailable, invalid, revoked, or superseded records

1Top Claim

10Assurance Claim

32Control

14Test

51Evidence

Claim dependency summary

Assurance claims and their declared support paths
Claim	Controls	Tests	Defeaters
AC-K05-C01 — Authority and mission boundary is explicit	4 controls	1 tests	5 named defeaters
AC-K05-C02 — High-consequence events are identified and bounded	4 controls	1 tests	5 named defeaters
AC-K05-C03 — Deterministic separation protects safety functions	4 controls	2 tests	5 named defeaters
AC-K05-C04 — Identity, firmware, and management planes remain trustworthy	7 controls	2 tests	6 named defeaters
AC-K05-C05 — Autonomous defense is bounded, causal, and reversible	6 controls	3 tests	6 named defeaters
AC-K05-C06 — Sensor and model disagreement cannot directly control force	4 controls	3 tests	6 named defeaters
AC-K05-C07 — Power, cooling, and timing failures do not defeat protected functions	7 controls	5 tests	5 named defeaters
AC-K05-C08 — Recovery is clean, evidenced, and repeatable	3 controls	1 tests	6 named defeaters
AC-K05-C09 — Evidence supports readiness without overclaiming	7 controls	3 tests	6 named defeaters
AC-K05-C10 — Authorized external effects remain separate from facility defense	4 controls	1 tests	6 named defeaters

Propagation rules

PR-K06-01. When evidence state is STALE or SUPERSEDED, dependent control and test become DEGRADED; claims using them cannot remain SATISFIED without independent current support.
PR-K06-02. When evidence state is INVALID or REVOKED, dependent control or test becomes FAILED; mandatory supporting claims become FAILED.
PR-K06-03. When evidence state is UNAVAILABLE, dependent state becomes UNRESOLVED unless another explicit evidence path is current.
PR-K06-04. When a claim defeater is active, that claim becomes FAILED regardless of positive evidence until the defeater is resolved.
PR-K06-05. When authority or deterministic-safety claim fails, top claim becomes FAILED; other claim degradation yields top-claim DEGRADED.

Machine-checkable records

Dependency graph JSON · Deterministic fixture evaluation · Failure reports

Node types: TOP_CLAIM=1, ASSURANCE_CLAIM=10, CONTROL=32, TEST=14, EVIDENCE=51. Edge types: DECOMPOSES_TO=10, SUPPORTED_BY_CONTROL=50, VERIFIED_BY_TEST=22, REQUIRES_EVIDENCE=36, PRODUCES_EVIDENCE=15.