Capability without custody.

Status: audit writer foundation. Storage-neutral durable writer and recovery contracts exist with a volatile conformance store; no durable profile has been accepted and no mutation lifecycle is integrated.

The problem

Agents need to inspect and change real systems, but direct credential access collapses intent, policy, execution and audit into one opaque step.

Responsibility

Expose typed capabilities through an explicit intent-to-evidence lifecycle: describe the proposed action, evaluate policy, execute within a bounded grant and return durable proof of the outcome.

Authority boundary

MCP may validate and execute an authorized capability. It does not decide portfolio priority, own project state or infer coordination authority from messages.

Public contracts

• Intent: a typed declaration of the requested outcome and target.
• Policy decision: an explicit allow, deny or approval requirement with reasons.
• Capability grant: the minimum authority, scope and lifetime needed for execution.
• Evidence: immutable references that show what happened and under which decision.

How it interacts

Coordination carries claims and signals to the right participants. Projects provides durable delivery context. MCP alone crosses the execution boundary and returns evidence for both.

Next direction

Review and explicitly accept a durable profile before implementation, then qualify checkpoint authority, approval identity, gateway integration, provider execution, verification and reconciliation as one bounded mutation lifecycle.