K06 assurance and procurement architecture

Facility Patterns

Direct answer

K06 separates four materially different facility contexts. No profile is a generic certificate, final design, licensing conclusion, or substitute for site-specific consequence and authority analysis.

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.

Four starting profiles

NON-CERTIFYING REFERENCE PATTERN

Existing nuclear-plant colocation

Treat the licensed nuclear plant, grid interconnection, datacenter, shared services, and contractual boundaries as one consequence network while preserving separate authorities and deterministic safety boundaries.

10 priority controls · 6 work packages · 4 tailoring questions

NON-CERTIFYING REFERENCE PATTERN

Part 53 advanced-reactor campus

Use security-by-design, technology-inclusive licensing evidence, consequence analysis, and selected Part 73 pathways from the beginning; never infer election, applicability, or approval from the existence of the final rule.

10 priority controls · 7 work packages · 4 tailoring questions

NON-CERTIFYING REFERENCE PATTERN

Isolated microreactor campus

Design for degraded communications, sparse local support, independent safe-state behavior, delayed external response, protected fuel and maintenance chains, and verifiable restoration without assuming autonomous force authority.

10 priority controls · 7 work packages · 4 tailoring questions

NON-CERTIFYING REFERENCE PATTERN

Non-nuclear high-consequence datacenter

Apply the same consequence, autonomy, evidence, recovery, power, cooling, management-plane, and physical-protection discipline even when nuclear licensing does not apply.

10 priority controls · 7 work packages · 4 tailoring questions

Tailoring rule

A profile is a structured starting point. It becomes useful only after the named facility's license basis, ownership, power topology, control boundaries, communications, cooling, emergency arrangements, mission authority, and evidence obligations are inspected.

Facility-pattern dataset