Tool, Skill, and Integration Contract Reference
Make every callable capability discoverable, authorizable, testable, observable, recoverable, and revocable.
A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
2. Complete contract
capability:
id: tool:pull-request-publish
version: 6.1.0
kind: tool
owner: team:developer-platform
lifecycle: certified
purpose: "Publish a review request for an existing branch"
non_purpose: [merge, deploy, change-branch-content]
input_schema: schema:publish-pr-input@3
output_schema: schema:publish-pr-result@2
error_schema: schema:capability-error@4
authn: workload-identity
authz: policy:repository-publication@5
resource_scope: [repository, branch]
tenant_scope: caller-tenant
data_classes: [internal, confidential]
destinations: [approved-source-provider]
side_effect: publication
reversible_by: tool:pull-request-close@2
idempotency: caller-key-required
timeout: PT20S
retry: reconcile-before-retry
rate_limit: 30/minute/installation
concurrency_key: repository
audit: full-request-metadata-redacted-body
evidence: external-object-receipt
availability_slo: 99.9%
cost_profile: external-api
certification_suite: suite:publish-pr@8
deprecation_notice: P90D
revocation_handle: capability-version
Skills additionally declare instructions, prerequisites, allowed tool dependencies, context needs, model profile compatibility, expected outputs, evaluation cases, and prohibited delegation. Integrations additionally declare provider ownership, tenancy mapping, credential exchange, data-use terms, residency, incident notification, rate behavior, reconciliation API, and exit procedure.
4. Invocation contract
The caller proposes a call with capability/version, subject, input digest, resource, tenant, purpose, expected side effect, idempotency key, deadline, and grant. The gateway validates discovery status, certification, schema, authorization, data class, destination, budget, concurrency, and revocation. The result includes status, exact output, effect receipt, dependency version, duration, usage/cost, retry classification, redactions, and audit reference.
A timeout means the result is unknown unless the contract guarantees no effect after timeout. Reconcile through the provider using the idempotency key or external receipt before retrying.
9. Tradeoffs and nonclaims
A broad integration reduces call count but hides policy and partial effects. Atomic tools improve composition and evidence but add orchestration overhead. Use atomic effects for consequential work and curated skills for reusable decision procedures. This review-ready reference does not certify any particular tool, protocol server, supplier, or registry.
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