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 rapid review of the chapter’s existing Quick Read, principles, definitions, lessons, and review material.
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 criteriaObjective
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.
Prerequisites 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 implementation
- Assign every component a canonical identity, owner, immutable version, digest, source, license, permissions, dependencies, compatibility, and lifecycle state.
- Resolve the transitive graph into a lock and bind it into a simulated Factory Version.
- Run functional, operational, security, and policy evaluations.
- Produce a certification object limited to read-only analysis in the disposable repository.
- Execute one qualified Attempt and retain the resolved graph with its evidence.
- Revoke the tool, attempt a new resolution, and prove it fails closed.
- Show that the historical Attempt still resolves to its original manifests and revocation timeline.
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.
Evidence and pass criteria
Retain manifests, digests, dependency lock, evaluation results, certification, policy decision, successful historical Attempt, rejected new resolution, revocation record, and migration recommendation. The lab fails if “latest” is used, revoked components remain eligible, or history becomes unresolvable.
Cleanup
Delete disposable packages and runtime state. Preserve the evidence bundle and remove any temporary credentials.
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