Agent Factory4 min readchapterQuick Read
Tool, Skill, and Integration Contract Reference
Make every callable capability discoverable, authorizable, testable, observable, recoverable, and revocable.
Status: Review readyRisk: highLifecycle: define · execute · verify · learnContent reviewed 2026-08-30Maturity guide →
Claim boundaryThis chapter references implementation evidence. Inspect its evidence boundary before treating a claim as proven.
study mode
A rapid review of the chapter’s existing Quick Read, principles, definitions, lessons, and review material.
Quick Read
~2 minThe chapter in one pass.
- Purpose: Make every callable capability discoverable, authorizable, testable, observable, recoverable, and revocable.
- Core rule: A tool schema describes data shape; a complete capability contract also defines authority, side effects, failure, cost, evidence, and lifecycle.
- Selection rule: Prefer narrow, atomic primitives with explicit receipts.
- Evidence boundary: Existing tools are not assumed to conform until their exact versions pass the contract suite.
10. Review and lab
Complete the External Capability Intake and Recertification Lab. A passing review demonstrates negative authorization, duplicate invocation, timeout after a side effect, reconciliation, revocation, dependency change, recertification, and independent reconstruction of the resulting evidence.
Evidence boundary
Curriculum maturity is not implementation proof.
This chapter defines architecture or practice. It does not by itself prove a corresponding production implementation.
External review
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence