--- id: capability.railiance.bootstrap-sequencing owner: railiance-bootstrap status: draft domain: infotech maturity: discovery: current: D3 target: D5 confidence: medium rationale: Owner scope, neighboring responsibilities, concrete use cases and limitations are documented; no exhaustive or generalized maturity claim. availability: current: A0 target: A0 confidence: medium rationale: 'Source interface assessed 2026-10-14: Bare-VM to estate sequence and handoff contract. Availability describes the delivery form, not production acceptance. End-to-end unattended rebuild is not established.' external_evidence: completeness: level: C1 confidence: low basis: Source artifacts establish a bounded capability; no independent consumer-completeness assessment in this review. reliability: level: R0 confidence: low basis: No longitudinal consumer reliability measurement established by this review. name: Bootstrap sequencing contracts summary: Bare-VM to estate sequence and handoff contract. tags: - security - netkingdom - framework-reuse discovery: intent: Bare-VM to estate sequence and handoff contract includes: - Bare-VM to estate sequence and handoff contract excludes: - End-to-end unattended rebuild is not established use_cases: - 'U10: Operator recovers identity, custody or data with independently held recovery material' - 'U14: Framework adopter validates and reuses selected contracts, tools and reference compositions' availability: current_level: A0 target_level: A0 current_artifacts: - SCOPE.md - docs/identity-recovery.md - tools/cmd/railiance-identity-recovery consumption_modes: - informational relations: related_to: - capability.security.iam-tooling-suite - capability.security.bootstrap-recovery evidence: documentation: - SCOPE.md - docs/identity-recovery.md consumer_guidance: recommended_for: - Operator recovers identity, custody or data with independently held recovery material - Framework adopter validates and reuses selected contracts, tools and reference compositions not_recommended_for: - End-to-end unattended rebuild is not established known_limitations: - End-to-end unattended rebuild is not established - 2026-10-14 architecture review estimates operational maturity separately; a registry entry does not authorize execution or establish deployment. - Identity recovery handoff delegates isolated verification to NetKingdom; offline provider retrieval and production import remain owner-run recovery steps, not automated bare-VM restore. --- # Bootstrap sequencing contracts Bare-VM to estate sequence and handoff contract. ## Reuse boundary End-to-end unattended rebuild is not established. ## Supported use cases - U10: Operator recovers identity, custody or data with independently held recovery material - U14: Framework adopter validates and reuses selected contracts, tools and reference compositions ## Evidence and integration - [SCOPE.md](../../SCOPE.md) Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists. Identity recovery handoff: [docs/identity-recovery.md](../../docs/identity-recovery.md). The source dispatcher adds verification only; availability/maturity are not promoted to assert a deployed recovery service.