docs(reuse): establish reviewed NetKingdom security capabilities
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684
This commit is contained in:
parent
1a36e857cc
commit
e99c3e9791
7 changed files with 658 additions and 87 deletions
110
registry/capabilities/capability.security.case-contracts.md
Normal file
110
registry/capabilities/capability.security.case-contracts.md
Normal file
|
|
@ -0,0 +1,110 @@
|
|||
---
|
||||
id: capability.security.case-contracts
|
||||
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: Versioned types, cases and schema
|
||||
validation. Availability describes the delivery form, not production acceptance.
|
||||
Type acknowledgment, case acceptance, structural materialization and native
|
||||
execution are distinct.'
|
||||
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: Security case types and instance validation
|
||||
summary: Versioned types, cases and schema validation.
|
||||
tags:
|
||||
- security
|
||||
- netkingdom
|
||||
- framework-reuse
|
||||
discovery:
|
||||
intent: Versioned types, cases and schema validation
|
||||
includes:
|
||||
- Versioned types, cases and schema validation
|
||||
excludes:
|
||||
- Type acknowledgment, case acceptance, structural materialization and native execution
|
||||
are distinct
|
||||
use_cases:
|
||||
- 'U01: Architect composes a security deployment from explicit owner contracts and
|
||||
case types'
|
||||
- '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: A2
|
||||
target_level: A2
|
||||
current_artifacts:
|
||||
- tools/security-case-types/README.md
|
||||
- canon/standards/security-case-types_v0.1.md
|
||||
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-case-types/README.md
|
||||
- canon/standards/security-case-types_v0.1.md
|
||||
consumer_guidance:
|
||||
recommended_for:
|
||||
- Architect composes a security deployment from explicit owner contracts and case
|
||||
types
|
||||
- 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:
|
||||
- Type acknowledgment, case acceptance, structural materialization and native execution
|
||||
are distinct
|
||||
known_limitations:
|
||||
- Type acknowledgment, case acceptance, structural materialization and native execution
|
||||
are distinct
|
||||
- 2026-10-14 architecture review estimates operational maturity separately; a registry
|
||||
entry does not authorize execution or establish deployment.
|
||||
---
|
||||
|
||||
# Security case types and instance validation
|
||||
|
||||
Versioned types, cases and schema validation.
|
||||
|
||||
## Reuse boundary
|
||||
|
||||
Type acknowledgment, case acceptance, structural materialization and native execution are distinct.
|
||||
|
||||
## Supported use cases
|
||||
|
||||
- U01: Architect composes a security deployment from explicit owner contracts and case types
|
||||
- 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
|
||||
|
||||
- [tools/security-case-types/README.md](../../tools/security-case-types/README.md)
|
||||
- [canon/standards/security-case-types_v0.1.md](../../canon/standards/security-case-types_v0.1.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.
|
||||
Loading…
Add table
Add a link
Reference in a new issue