Software Supply Chain Security, Provenance, and Attestation
Passing tests does not establish what was built, from which source, by which identity, with which dependencies, or whether the artifact later changed. An autonomous factory expands the supply chain: models, prompts, tools, MCP servers, runn
A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Reconstruct and defend this chapter’s architecture.
Reconstruct the architecture, name each boundary, and defend the tradeoffs.
Open the source exercise
Draw the chain from approved Plan to deployed digest. Mark every identity, trust boundary, signing event, verification event, mutable reference, and revocation check. Then show how a compromised dependency registry and a compromised CI worker are detected by different controls.
4. Tradeoffs
Hermetic builds and high SLSA levels cost engineering time and may not fit every ecosystem. Transparency can conflict with confidentiality. Keyless identity reduces key management but creates dependence on identity providers and trust roots. SBOMs can expose sensitive component data. Apply stronger controls to consequential artifacts while keeping hard identity and digest binding universal.
5. Current Mission Control Implementation
Mission Control models repository/base/head SHA lineage, run artifacts, verification receipts, GitHub CI ingestion, and release/deployment records. The current staged working tree contains additional Attempt, execution-manifest, isolated-worktree, path-scope, and GitHub App publication work. Because convex/factory/attempts.ts and apps/orchestration-server/src/githubAppRuntime.ts are staged but absent from local HEAD, this chapter treats them as implementation candidates rather than current capability.
It does not yet demonstrate a canonical SLSA provenance pipeline, SBOM generation and policy, Sigstore/in-toto verification, signed Quality Proof Packages, or a transparency-backed evidence ledger. These are future controls, not current product claims.
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence