{
  "schema_version": "1.3.0",
  "slug": "which-software-bill-of-materials-sbom-attestations-must-be-sealed-into-a-session-residual-before-deployment",
  "title": "Which software bill of materials (SBOM) attestations must be sealed into a session residual before deployment?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The artifact is deployed into a production environment, or the successor instance relies on the compiled artifact's integrity to execute security-sensitive operations. * **Does not apply when:** The build process is stri",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-software-bill-of-materials-sbom-attestations-must-be-sealed-into-a-session-residual-before-deployment.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-software-bill-of-materials-sbom-attestations-must-be-sealed-into-a-session-residual-before-deployment.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-software-bill-of-materials-sbom-attestations-must-be-sealed-into-a-session-residual-before-deployment.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 965,
    "python_slice_tokens": 203,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **direct dependency manifests** (e.g., `package.json`, `requirements.txt`, which list declared versions) and **transitive SBOM attestations** (the cryptographically signed proof of every compiled library, including nested dependencies, hashes, and build provenance). Relying only on direct manifests creates the **Transitive Ghost Depend...",
    "what_was_observed": "In automated CI/CD agent pipelines, failing to seal SBOM attestations produces three primary failure modes: 1. **Dependency Confusion:** A malicious actor publishes a public package with the same name as an internal, private dependency. If the build environment is not constrained by an SBOM lock, the agent pulls the malicious public version. 2. **Build Provenance Spoofing:** The successor cannot verify that the binar...",
    "condition_of_validity": "* **Applies when:** The artifact is deployed into a production environment, or the successor instance relies on the compiled artifact's integrity to execute security-sensitive operations. * **Does not apply when:** The build process is strictly hermetic with deterministic reproducibility (e.g., Nix), where the build hash is mathematically guaranteed to be id...",
    "decision_boundary": "1. **Did the session build or mutate a deployable artifact?** If no, standard manifest recording suffices. If yes, proceed to seal SBOM. 2. **Is the `builder_identity_attestation` present?** If no, the artifact's origin is unverified. The successor must treat the build as `UNTRUSTED`. 3. **Does the `transitive_dependency_manifest` match the expected SBOM?** ...",
    "operational_effect": "1. **Supply Chain Immunity:** Prevents dependency confusion and transitive library injection by cryptographically sealing the entire dependency tree. 2. **Provenance Verification:** Allows the successor to independently verify the artifact's origin and integrity before executing it. 3. **Deterministic Rollback:** If a vulnerability is discovered, the SBOM pr..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "dd483c1723186b91a09959926296d778921c26c5032f30e4f18dc9025b4515d0",
    "verified_classes": [
      "SBOMPresence",
      "SBOMContext",
      "ExpectedDependency",
      "SBOMManifest",
      "SBOMIntegrityGuard"
    ],
    "verified_functions": [
      "_hash",
      "verify_artifact_sbom"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 0,
    "raised_exceptions": [],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}