Capability Certification and Revocation Lab
Prove that an agent capability can be packaged, evaluated, certified for a bounded scope, resolved into an execution contract, and revoked without losing historical explainability.
A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Prove that an agent capability can be packaged, evaluated, certified for a bounded scope, resolved into an execution contract, and revoked without losing historical explainability.
Execute the existing Markdown instructions and retain the required output and evidence.
Jump to validation criteriaPrerequisites and starting state
- A disposable local repository.
- One read-only repository-analysis agent, one skill, one typed tool, one model profile, and one evaluator represented by manifests.
- No production credentials or production registry.
- Read the three Agent Factory chapters.
Required failure
Publish a second skill version that requests a permission outside the certified scope. The resolver must reject it or require a new certification; a familiar name cannot preserve eligibility.
Curriculum maturity is not implementation proof.
This chapter defines architecture or practice. It does not by itself prove a corresponding production implementation.
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence