Add Prophet Trust Chain supply-chain validation artifacts#264
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements the first AgentPlane slice for Prophet Trust Chain supply-chain validation evidence.
This PR adds
SupplyChainValidationArtifactas a contract surface binding runtime supply-chain evidence to AgentPlane validation, replay, and receipt evidence.Closes #261.
Changes
schemas/trust-chain/supply-chain-validation-artifact.v0.1.schema.jsontests/fixtures/trust-chain/supply-chain-validation.valid.jsontests/fixtures/trust-chain/supply-chain-validation.blocked.jsontools/validate_trust_chain_supply_chain_validation.pytools/tests/test_trust_chain_supply_chain_validation.pyAcceptance coverage
The valid fixture requires SBOM, VEX, lockfile, signature, scan, promotion, rollback, policy, guardrail, validation, replay, and runtime receipt references before production-scope execution and promotion are allowed.
The blocked fixture denies execution and promotion, requires repair and human review, and preserves remediation authority.
The validator enforces:
Boundary
This does not perform live package scanning, certify runtime production readiness by itself, replace Lattice Forge runtime evidence, replace Policy Fabric policy profiles, or replace Guardrail Fabric action admission.
Validation
Expected: