2026-06-16 01:46:54 +02:00
---
id: capability.authorization.policy-evaluate
2026-10-14 06:37:38 +02:00
name: Policy evaluation and decision evidence
summary: Check, batch, list-allowed, explain, binding, lifetime and decision records.
owner: access-engine
2026-06-16 01:46:54 +02:00
status: draft
domain: helix_forge
2026-10-14 06:37:38 +02:00
tags:
- authorization
- policy
- flex-auth
- security
- netkingdom
- framework-reuse
2026-06-16 01:46:54 +02:00
maturity:
discovery:
current: D4
target: D6
confidence: medium
2026-10-14 06:37:38 +02:00
rationale: flex-auth INTENT defines policy-as-code boundary and enterprise growth
path.
2026-06-16 01:46:54 +02:00
availability:
2026-10-14 06:37:38 +02:00
current: A4
2026-06-16 01:46:54 +02:00
target: A5
confidence: low
2026-10-14 06:37:38 +02:00
rationale: 'Source interface assessed 2026-10-14: Check, batch, list-allowed,
explain, binding, lifetime and decision records. Availability describes the
delivery form, not production acceptance. One PDP owner with per-consumer deployments;
signed envelope production and consumer adoption are distinct.'
2026-06-16 01:46:54 +02:00
external_evidence:
completeness:
level: C2
name: Partial
confidence: low
basis: scope_vs_intent_and_consumer_expectations
satisfied_expectations:
2026-10-14 06:37:38 +02:00
- policy-as-code intent documented
2026-06-16 01:46:54 +02:00
broken_expectations:
2026-10-14 06:37:38 +02:00
- not yet indexed from flex-auth native registry
2026-06-16 01:46:54 +02:00
out_of_scope_expectations:
2026-10-14 06:37:38 +02:00
- identity proofing
2026-06-16 01:46:54 +02:00
reliability:
level: R1
confidence: low
basis: consumer_quality_signals
known_reliability_risks:
2026-10-14 06:37:38 +02:00
- early implementation phase
2026-06-16 01:46:54 +02:00
discovery:
2026-10-14 06:37:38 +02:00
intent: Check, batch, list-allowed, explain, binding, lifetime and decision records
2026-06-16 01:46:54 +02:00
includes:
2026-10-14 06:37:38 +02:00
- Check, batch, list-allowed, explain, binding, lifetime and decision records
2026-06-16 01:46:54 +02:00
excludes:
2026-10-14 06:37:38 +02:00
- One PDP owner with per-consumer deployments; signed envelope production and consumer
adoption are distinct
use_cases:
- 'U03: Application combines identity, tenant and resource facts and enforces a
bound decision'
- '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'
2026-06-16 01:46:54 +02:00
availability:
2026-10-14 06:37:38 +02:00
current_level: A4
2026-06-16 01:46:54 +02:00
target_level: A5
current_artifacts:
2026-10-14 06:37:38 +02:00
- SCOPE.md
- README.md
2026-06-16 01:46:54 +02:00
consumption_modes:
2026-10-14 06:37:38 +02:00
- HTTP API
- source
2026-06-16 01:46:54 +02:00
relations:
depends_on:
2026-10-14 06:37:38 +02:00
- capability.identity.subject-resolution
2026-06-16 01:46:54 +02:00
related_to:
2026-10-14 06:37:38 +02:00
- capability.feature-control.evaluate
- capability.security.approval-lifecycle
- capability.iam.key-cape
- capability.identity.tenant-facts
- capability.security.zone-reference
- capability.security.maturity-claims
2026-06-16 01:46:54 +02:00
consumer_guidance:
recommended_for:
2026-10-14 06:37:38 +02:00
- Application combines identity, tenant and resource facts and enforces a bound
decision
- 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
2026-06-16 01:46:54 +02:00
not_recommended_for:
2026-10-14 06:37:38 +02:00
- One PDP owner with per-consumer deployments; signed envelope production and consumer
adoption are distinct
2026-06-16 01:46:54 +02:00
known_limitations:
2026-10-14 06:37:38 +02:00
- One PDP owner with per-consumer deployments; signed envelope production and consumer
adoption are distinct
- 2026-10-14 architecture review estimates operational maturity separately; a registry
entry does not authorize execution or establish deployment.
promotion_history:
- date: '2026-10-14'
dimension: availability
from: A2
to: A4
rationale: Interface-form reassessment from current owner sources; no completeness/reliability
promotion.
author: codex
evidence:
documentation:
- SCOPE.md
- README.md
2026-06-16 01:46:54 +02:00
---
2026-10-14 06:37:38 +02:00
# Policy evaluation and decision evidence
Check, batch, list-allowed, explain, binding, lifetime and decision records.
## Reuse boundary
One PDP owner with per-consumer deployments; signed envelope production and consumer adoption are distinct.
## Supported use cases
- U03: Application combines identity, tenant and resource facts and enforces a bound decision
- 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 )
- [README.md ](../../README.md )
2026-06-16 01:46:54 +02:00
2026-10-14 06:37:38 +02:00
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.