Pattern matrix/White paper/G3

ADPS Agent Design Pattern White Paper

G3 · Progressive Commitment

Manage promotion, hold, demotion, and retirement by capability, scenario, resource, and version.

Progressive Commitment governs local, version-bound authority. It records an agent version's authority for a capability, scenario, resource, and environment instead of assigning one global trust score.

Coordinate and authority unit

Governance × Chain. Shadow, recommendation, bounded execution, and expanded scope have evidence prerequisites. Incidents, dependencies, and version changes can move the chain backward.

authority_key = (
    agent_version,
    capability,
    scenario,
    resource_scope,
    environment
)

Validation and submission by the same payroll agent should have separate grants.

Autonomy tiers

TierBehaviorEvidence
ShadowRead real input with no business effectBaseline, coverage, failure classes
RecommendProduce a recommendation or draftAdoption, edits, long-tail errors
Bounded ExecuteAutomate reversible or low-impact work inside hard limitsExternal acceptance, reversal, boundary events, incidents
Expanded ExecuteExpand objects, frequency, or scenarios while retaining hard limitsStable window, stratified samples, business outcome
Frozen / RetiredStop new effects and preserve audit or rollbackIncident, expired version, missing owner, ended pilot

Evidence

Task and outcome evidence shows goal completion and downstream use. Process evidence covers planning, tools, memory, and recovery. Foundation evidence covers model, tool, storage, and policy health. An average success rate cannot replace these levels or expose high-risk tails.

Running example

Payroll agent v7 validates in Shadow and then Recommend. Routine batches are stable while new-hire and cross-region cases remain weak, so only the routine slice receives Bounded Execute. Submission remains reviewed under G1. A payment-tool upgrade freezes the affected validation grant and returns it to Shadow while unrelated capabilities retain their state.

Disposition, failure, and verification

A review can promote, hold, narrow, demote, or retire. Missing eval coverage, a changed dependency, rising error rates, owner departure, or long inactivity can invalidate authority without an incident.

Reject global agent levels, one-way ladders, easy-sample selection, authority inheritance after material changes, agent-writable grants, and immediate full traffic after promotion. Verify grant granularity, evidence coverage, post-promotion rollback, demotion latency, version inheritance, retirement, and real reduction in human load.

Suggested citation:ADPS, G3 · Progressive Commitment, Agent Design Pattern White Paper v0.4, 19 August 2026.

Pattern catalog · Governance workshop · CC BY 4.0

Scope:Public review draft. Definitions and classifications are open for discussion and citation; running examples explain mechanisms, while attributed practice appears in the case library.