| capability.security.case-contracts |
net-kingdom |
draft |
infotech |
| discovery |
availability |
| current |
target |
confidence |
rationale |
| D3 |
D5 |
medium |
Owner scope, neighboring responsibilities, concrete use cases and limitations are documented; no exhaustive or generalized maturity claim. |
|
| current |
target |
confidence |
rationale |
| A2 |
A2 |
medium |
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. |
|
|
| completeness |
reliability |
| level |
confidence |
basis |
| C1 |
low |
Source artifacts establish a bounded capability; no independent consumer-completeness assessment in this review. |
|
| level |
confidence |
basis |
| R0 |
low |
No longitudinal consumer reliability measurement established by this review. |
|
|
Security case types and instance validation |
Versioned types, cases and schema validation. |
| security |
| netkingdom |
| framework-reuse |
|
| intent |
includes |
excludes |
use_cases |
| Versioned types, cases and schema validation |
| Versioned types, cases and schema validation |
|
| Type acknowledgment, case acceptance, structural materialization and native execution are distinct |
|
| 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 |
|
|
| current_level |
target_level |
current_artifacts |
consumption_modes |
| A2 |
A2 |
| tools/security-case-types/README.md |
| canon/standards/security-case-types_v0.1.md |
|
|
|
| related_to |
specializes |
| capability.security.practice-canon |
| capability.security.doctrine-review |
| capability.iam.key-cape |
| capability.authorization.policy-evaluate |
| capability.registry.register |
|
| capability.security.iam-tooling-suite |
|
|
| documentation |
| tools/security-case-types/README.md |
| canon/standards/security-case-types_v0.1.md |
|
|
| recommended_for |
not_recommended_for |
known_limitations |
| 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 |
|
| Type acknowledgment, case acceptance, structural materialization and native execution are distinct |
|
| 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. |
|
|