Concepts/Concept

Start with a generated pipeline

A coding agent has produced a new publishing pipeline. That output should not begin receiving production tasks immediately. The team must run a complete example, inspect the delivered result, and explicitly grant an operating boundary.

Definition

A capability certification lifecycle defines how a generated or modified capability gains, retains, and loses the right to run automatically.

draft -> candidate -> active

A complete evidence run moves the capability to candidate. Human certification moves it to active. A change in code, templates, or critical rules invalidates the old evidence and returns the capability to a review state.

Boundary

Lifecycle states must control real routing permissions, not serve as display labels. Certification is tied to a specific version, test set, evidence record, and declared scope. High-risk capabilities also require authorization, blast-radius limits, and rollback.

Provenance

• Initial case: Xuanxu Technology GIS publishing agent, contributed by Yuke Xiong.
• Lineage: artifact registries, staging-to-production promotion, model registries, and progressive delivery.
• ADPS contribution: applies promotion and invalidation to pipelines, skills, tool wrappers, and agent subflows, with explicit automatic execution rights.
• Definition status: candidate concept.

Edit source · Published source · Review process