0% read on this device
Browse the curriculum

Start Here

Vision

First Principles

Operating Model

Domain Model

Agent Factory

Runtime Architecture

AI Engineering

Autonomous Workflows

Verification & Delivery

Factory Platform

Quality Engineering

Security & Governance

Case Studies

Labs

Interview Practice

Research Journal

Reference

Curriculum/Labs/Complete source chapter
Labs2 min readlabexecutable lab

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.

Status: Review readyRisk: highLifecycle: define · verify · learnContent reviewed 2026-08-30Maturity guide →
Claim boundaryThis chapter references implementation evidence. Inspect its evidence boundary before treating a claim as proven.
Hands-on 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.

Execute the existing Markdown instructions and retain the required output and evidence.

practice2 min chapter
Jump to validation criteria

Objective

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

  1. Assign every component a canonical identity, owner, immutable version, digest, source, license, permissions, dependencies, compatibility, and lifecycle state.
  2. Resolve the transitive graph into a lock and bind it into a simulated Factory Version.
  3. Run functional, operational, security, and policy evaluations.
  4. Produce a certification object limited to read-only analysis in the disposable repository.
  5. Execute one qualified Attempt and retain the resolved graph with its evidence.
  6. Revoke the tool, attempt a new resolution, and prove it fails closed.
  7. 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.

Evidence boundary

Curriculum maturity is not implementation proof.

This chapter defines architecture or practice. It does not by itself prove a corresponding production implementation.

CurriculumReview readyImplementation evidenceNot asserted hereInspect evidence map →
External review

Review this chapter.

Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.

  • Claim
  • Boundary
  • Failure
  • Evidence