| capability.security.iam-tooling-suite |
NetKingdom security architecture and conformance tooling |
Versioned IAM, layer, tenancy and credential contracts plus validators. |
net-kingdom |
draft |
infotech |
| security |
| iam |
| kubernetes |
| conformance |
| netkingdom |
| framework-reuse |
|
| discovery |
availability |
| current |
target |
confidence |
rationale |
| D3 |
D5 |
medium |
SCOPE plus docs/secrets-engine-security-infrastructure-boundary.md describe an explicit integration boundary with OpenBao, flex-auth, user-engine, ops-warden, ops-bridge, info-tech-canon, and State Hub; canon/standards/ holds versioned IAM v0.3, playbook capability, scenario composition, tenancy, zone, and boundary standards that provider repos implement against. |
|
| current |
target |
confidence |
rationale |
| A2 |
A3 |
medium |
Source interface assessed 2026-10-14: Versioned IAM, layer, tenancy and credential contracts plus validators. Availability describes the delivery form, not production acceptance. Mixed accepted and proposed standards; framework integration remains incomplete. |
|
|
| completeness |
reliability |
| level |
confidence |
basis |
satisfied_expectations |
broken_expectations |
out_of_scope_expectations |
| C1 |
low |
scope_vs_intent_and_consumer_expectations |
| versioned canon standards already implemented by a sibling repo (key-cape) |
| documented, runnable conformance, posture, composition, and bootstrap tools under tools/ |
|
|
|
|
| level |
confidence |
basis |
known_reliability_risks |
| R1 |
low |
consumer_quality_signals |
| no top-level packaging; each tool under tools/ has its own runtime dependencies, no unified install path yet |
|
|
|
| intent |
includes |
excludes |
assumptions |
use_cases |
research_memos |
| Versioned IAM, layer, tenancy and credential contracts plus validators |
| Versioned IAM, layer, tenancy and credential contracts plus validators |
|
| Mixed accepted and proposed standards; framework integration remains incomplete |
|
|
| U01: Architect composes a security deployment from explicit owner contracts and case types |
| U02: Human signs in with MFA and manages account or factor recovery |
| U03: Application combines identity, tenant and resource facts and enforces a bound decision |
| U14: Framework adopter validates and reuses selected contracts, tools and reference compositions |
|
|
|
| current_level |
target_level |
current_artifacts |
target_artifacts |
consumption_modes |
| A2 |
A3 |
| SCOPE.md |
| SECURITY-COMPANION.md |
|
|
|
|
| depends_on |
supports |
related_to |
|
|
|
| capability.security.practice-canon |
| capability.security.doctrine-review |
| capability.iam.key-cape |
| capability.authorization.policy-evaluate |
| capability.registry.register |
|
|
| documentation |
tests |
consumer_feedback |
bug_reports |
incidents |
| SCOPE.md |
| SECURITY-COMPANION.md |
|
| tools/iam-profile-conformance (pytest fixtures) |
|
|
|
|
|
| recommended_for |
not_recommended_for |
known_limitations |
| Architect composes a security deployment from explicit owner contracts and case types |
| Human signs in with MFA and manages account or factor recovery |
| Application combines identity, tenant and resource facts and enforces a bound decision |
| Framework adopter validates and reuses selected contracts, tools and reference compositions |
|
| Mixed accepted and proposed standards; framework integration remains incomplete |
|
| Mixed accepted and proposed standards; framework integration remains incomplete |
| 2026-10-14 architecture review estimates operational maturity separately; a registry entry does not authorize execution or establish deployment. |
|
|
|