nx_install_plan.nx

nx_install_plan.nx -- selection-pipeline output record. SA-6/SA-7 bridge of NISHI_SELF_ASSEMBLY_ROADMAP.md. Captures (probe-snapshot, calibration-snapshot, policy-snapshot, selected-variant-ids, total-cost, verdict) into one canary-bracketed record. The artifact: - SA-6 feeds this to nx_compile (which compiles only the selected variants), then nx_verify (which smoke-runs each on the target) - SA-7 cryptographically attests this record (install_hash = H(probe_snapshot + calibration_snapshot + policy_snapshot + selection)) so future audits can REPLAY the selector against the recorded inputs and reach bit-identical output The plan is content-addressable by construction: same inputs (same probe + same calibration + same policy + same candidate set) MUST yield the same plan. This is the racing-line claim per [[feedback-end-to-end-bit-traceability-architecture]]: every byte from source -> selection -> install has a ProvenanceLink. V1 scope: - Flat snapshot of probe + calibration + policy key fields - selected_variant_ids stored as *i64 array (caller-owned) - canary bracket for tamper-detect - schema versioning for future field additions Deferred per roadmap: - cryptographic install_hash computation (SA-7; will compose with nx_sha256 + nx_blake2b) - in-toto link metadata serialization (SA-7) - Rekor-class append-only audit log (SA-7) - Multi-substrate co-residence (multiple plans on one host) (SA-7) - Replay-from-plan verifier (SA-7) genealogy_id: in_toto_2018 + slsa_2021 + sigstore_2021 + reproducible_builds_2013 + cardinal_2026-05-19_self_assembly lineage_id: substrate_install_plan_v1 nx_capability_manifest: variant_class: install_plan_record variant_id: install_plan_v1