---
id: capability.security.scenario-compose
owner: net-kingdom
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: A2
    target: A2
    confidence: medium
    rationale: 'Source interface assessed 2026-10-14: CLI selects pinned providers
      and orders trust transitions. Availability describes the delivery form, not
      production acceptance. Plan only; execution.permitted is always false.'
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: Deterministic security scenario composition
summary: CLI selects pinned providers and orders trust transitions.
tags:
- security
- netkingdom
- framework-reuse
discovery:
  intent: CLI selects pinned providers and orders trust transitions
  includes:
  - CLI selects pinned providers and orders trust transitions
  excludes:
  - Plan only; execution.permitted is always false
  use_cases:
  - 'U01: Architect composes a security deployment from explicit owner contracts and
    case types'
  - 'U14: Framework adopter validates and reuses selected contracts, tools and reference
    compositions'
availability:
  current_level: A2
  target_level: A2
  current_artifacts:
  - tools/security-scenario-composer/README.md
  - tools/security-scenario-composer/security_scenario_composer.py
  consumption_modes:
  - CLI
  - source
relations:
  related_to:
  - capability.security.practice-canon
  - capability.security.doctrine-review
  - capability.iam.key-cape
  - capability.authorization.policy-evaluate
  - capability.registry.register
  specializes:
  - capability.security.iam-tooling-suite
evidence:
  documentation:
  - tools/security-scenario-composer/README.md
  - tools/security-scenario-composer/security_scenario_composer.py
consumer_guidance:
  recommended_for:
  - Architect composes a security deployment from explicit owner contracts and case
    types
  - Framework adopter validates and reuses selected contracts, tools and reference
    compositions
  not_recommended_for:
  - Plan only; execution.permitted is always false
  known_limitations:
  - Plan only; execution.permitted is always false
  - 2026-10-14 architecture review estimates operational maturity separately; a registry
    entry does not authorize execution or establish deployment.
---

# Deterministic security scenario composition

CLI selects pinned providers and orders trust transitions.

## Reuse boundary

Plan only; execution.permitted is always false.

## Supported use cases

- U01: Architect composes a security deployment from explicit owner contracts and case types
- U14: Framework adopter validates and reuses selected contracts, tools and reference compositions

## Evidence and integration

- [tools/security-scenario-composer/README.md](../../tools/security-scenario-composer/README.md)
- [tools/security-scenario-composer/security_scenario_composer.py](../../tools/security-scenario-composer/security_scenario_composer.py)

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.