---
id: capability.security.approval-lifecycle
owner: approval-engine
status: draft
domain: infotech
maturity:
  discovery:
    current: D3
    target: D5
    confidence: medium
    rationale: Owner scope, neighboring responsibilities, concrete use cases and limitations
      are documented; no exhaustive or generalized maturity claim.
  availability:
    current: A4
    target: A4
    confidence: medium
    rationale: 'Source interface assessed 2026-10-14: Authenticated issue, claim,
      revoke, supersede and atomic consume API with outbox. Availability describes
      the delivery form, not production acceptance. Deployed schema v5 and source
      v6 differ; named PEP and issuer acceptance remain open.'
external_evidence:
  completeness:
    level: C1
    confidence: low
    basis: Source artifacts establish a bounded capability; no independent consumer-completeness
      assessment in this review.
  reliability:
    level: R0
    confidence: low
    basis: No longitudinal consumer reliability measurement established by this review.
name: Bound approval lifecycle
summary: Authenticated issue, claim, revoke, supersede and atomic consume API with
  outbox.
tags:
- security
- netkingdom
- framework-reuse
discovery:
  intent: Authenticated issue, claim, revoke, supersede and atomic consume API with
    outbox
  includes:
  - Authenticated issue, claim, revoke, supersede and atomic consume API with outbox
  excludes:
  - Deployed schema v5 and source v6 differ; named PEP and issuer acceptance remain
    open
  use_cases:
  - 'U04: Protected operation obtains and consumes exact human approval before its
    side effect'
  - 'U05: Operator provisions and delivers a scoped workload credential through the
    approved owner lane'
  - 'U06: Operator or automation obtains a bounded SSH certificate and maintains private
    connectivity'
availability:
  current_level: A4
  target_level: A4
  current_artifacts:
  - SCOPE.md
  - approval_engine/api.py
  - docs/production-dependencies.md
  consumption_modes:
  - HTTP API
  - source
relations:
  related_to:
  - capability.authorization.policy-evaluate
  - capability.iam.key-cape
  - capability.security.credential-lifecycle
  - capability.audit.event-retain
evidence:
  documentation:
  - SCOPE.md
  - approval_engine/api.py
  - docs/production-dependencies.md
consumer_guidance:
  recommended_for:
  - Protected operation obtains and consumes exact human approval before its side
    effect
  - Operator provisions and delivers a scoped workload credential through the approved
    owner lane
  - Operator or automation obtains a bounded SSH certificate and maintains private
    connectivity
  not_recommended_for:
  - Deployed schema v5 and source v6 differ; named PEP and issuer acceptance remain
    open
  known_limitations:
  - Deployed schema v5 and source v6 differ; named PEP and issuer acceptance remain
    open
  - 2026-10-14 architecture review estimates operational maturity separately; a registry
    entry does not authorize execution or establish deployment.
---

# Bound approval lifecycle

Authenticated issue, claim, revoke, supersede and atomic consume API with outbox.

## Reuse boundary

Deployed schema v5 and source v6 differ; named PEP and issuer acceptance remain open.

## Supported use cases

- U04: Protected operation obtains and consumes exact human approval before its side effect
- U05: Operator provisions and delivers a scoped workload credential through the approved owner lane
- U06: Operator or automation obtains a bounded SSH certificate and maintains private connectivity

## Evidence and integration

- [SCOPE.md](../../SCOPE.md)
- [approval_engine/api.py](../../approval_engine/api.py)
- [docs/production-dependencies.md](../../docs/production-dependencies.md)

Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists.