Document owner-fleet identity and offline qualification next steps #94

Merged
ams-tech merged 2 commits from codex/spiffe-roadmap into main 2026-10-01 05:45:29 -04:00
ams-tech commented 2026-09-29 00:28:31 -04:00 (Migrated from github.com)

Record the accepted owner-fleet identity and autonomous-boot follow-on in the delivery scope and README, with a pointer from the archived production-security proposal. The plan reuses kaiba-fleet and shared contracts, and evaluates native Pi monotonic state before a TPM add-on if required.

Keep the selected pilot policy distinct from the stronger rollback-qualified profile. SPIRE software tests do not satisfy physical provisioning, trusted-time, authority-state continuity, or production admission gates.

Documentation-only validation: local links and whitespace checks pass. No signing, OTP, TPM, storage, or physical provisioning operations performed.

Record the accepted owner-fleet identity and autonomous-boot follow-on in the delivery scope and README, with a pointer from the archived production-security proposal. The plan reuses kaiba-fleet and shared contracts, and evaluates native Pi monotonic state before a TPM add-on if required. Keep the selected pilot policy distinct from the stronger rollback-qualified profile. SPIRE software tests do not satisfy physical provisioning, trusted-time, authority-state continuity, or production admission gates. Documentation-only validation: local links and whitespace checks pass. No signing, OTP, TPM, storage, or physical provisioning operations performed.
Sign in to join this conversation.
No description provided.