Component Registry agent-readable instructions
The Registry records artifact identity, PCD hashes, checked state, and boundary notes so teams can inspect declared circuits before reuse.
- PCD-closed: The declared PCD reached closed-circuit state under its stated domains. This does not certify external runtime behavior.
- Review-checked: The artifact has bounded checks, hash references, and visible annotations. Reviewers must inspect remaining boundary notes.
- Blocked: A constraint, evidence, or boundary mismatch was detected. The artifact should not be reused until repaired.
Component Registry
Bounded blueprints with visible review state.
The Registry records artifact identity, PCD hashes, checked state, and boundary notes so teams can inspect declared circuits before reuse.
Registry Protocol
Integrity is measured, not assumed.
Every artifact should show what was checked, what state it reached, and where the claim boundary stops.
Verification States
Registry badges expose the review state of the declared circuit. They do not certify the consuming system.
PCD-closed
ClosedThe declared PCD reached closed-circuit state under its stated domains. This does not certify external runtime behavior.
Review-checked
BoundedThe artifact has bounded checks, hash references, and visible annotations. Reviewers must inspect remaining boundary notes.
Blocked
RepairA constraint, evidence, or boundary mismatch was detected. The artifact should not be reused until repaired.
PCD Lifecycle
The registry stores evidence state after the artifact passes through explicit checks.
02. Record state
Attach PCD hash, check result, boundary note, and evidence packet reference.
Publish artifacts with their review state visible.
Start with a bounded workflow, then publish the artifact with its evidence posture attached.