K06 assurance and procurement architecture

Procurement Work Packages

Direct answer

The K06 package sequence converts a broad request for critical-datacenter protection into bounded, inspectable work with explicit acceptance evidence and exclusions.

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.

Work-package sequence

WP-K06-01

Mission and authority analysis

Define the protected mission, competent authorities, asset scope, allowed actions, prohibited outcomes, decision rights, deconfliction, and evidence obligations before technology selection.

5 deliverables · 5 acceptance-evidence classes · 0 dependencies

WP-K06-03

Cyber-physical architecture assessment

Assess separation, identity, management planes, OT, power, cooling, timing, physical sensing, autonomy, evidence, and recovery against the consequence model.

5 deliverables · 4 acceptance-evidence classes · 2 dependencies

WP-K06-05

Evaluation-range design

Design an isolated, effects-bounded range or digital twin that can test claims without exposing production systems or reusable attack procedures.

5 deliverables · 5 acceptance-evidence classes · 2 dependencies

WP-K06-06

Model and autonomous-agent assurance

Evaluate model provenance, data lineage, adversarial robustness, tool authority, memory boundaries, drift, fallback, and runtime constraints.

5 deliverables · 4 acceptance-evidence classes · 2 dependencies

WP-K06-07

Critical-function recovery exercise

Demonstrate clean restoration of minimum viable mission and safe functions under isolated, degraded, and compromise-assumed conditions.

5 deliverables · 4 acceptance-evidence classes · 2 dependencies

WP-K06-08

Assurance evidence package

Assemble claim-to-control-to-test-to-evidence traceability, provenance, currentness, signatures, limitations, defects, and decision receipts.

5 deliverables · 5 acceptance-evidence classes · 7 dependencies

WP-K06-09

Independent verification

Challenge the assurance argument, replay evidence, test mappings, inspect defeaters, and record disagreements without inheriting the delivery team's conclusions.

5 deliverables · 4 acceptance-evidence classes · 1 dependencies

WP-K06-10

Post-deployment observation

After owner-confirmed deployment, observe actual configuration, reachability, headers, service identity, operating evidence, incidents, drift, and recovery readiness against the approved manifest.

5 deliverables · 5 acceptance-evidence classes · 2 dependencies

Contract boundary

The work packages describe scope and acceptance evidence. They do not constitute a proposal price, contract award, legal opinion, security plan approval, classified tasking, authority to access a target, or authorization to employ force.

Complete work-package dataset