From 2f20c02cad1fcdc6d9070a08ba4d5b688f79b80c Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 14 Oct 2026 06:46:43 +0200 Subject: [PATCH] docs(reuse): establish reviewed NetKingdom security capabilities Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684 --- .../capability.identity.user-engine.md | 125 ++++++++++-------- registry/indexes/capabilities.yaml | 18 ++- 2 files changed, 79 insertions(+), 64 deletions(-) diff --git a/registry/capabilities/capability.identity.user-engine.md b/registry/capabilities/capability.identity.user-engine.md index 4cc90c9..0306dab 100644 --- a/registry/capabilities/capability.identity.user-engine.md +++ b/registry/capabilities/capability.identity.user-engine.md @@ -1,8 +1,7 @@ --- id: capability.identity.user-engine -name: Headless Multi-Tenant User Engine -summary: Headless, multi-application, multi-tenant user management engine covering registration, identity/factor - models, entitlement claims, hats/realms/services/assets access profiles, and onboarding journeys. +name: User lifecycle and account journeys +summary: Accounts, identity links, membership, MFA and recovery portal, advisory catalog. owner: user-engine status: draft domain: communication @@ -10,21 +9,27 @@ tags: - identity - user-management - multi-tenant +- security +- netkingdom +- framework-reuse maturity: discovery: current: D4 target: D5 confidence: high - rationale: 'Unusually large documentation set for its size: docs/development.md, configuration.md, - contracts.md, canon-mapping.md, canon-interface-card.yaml, family-dataspace-onboarding.md, registration-identity-and-factor-model.md, - prepared-accounts-and-entitlement-claims.md, hats-realms-services-assets-access-profiles.md, onboarding-journeys-and-welcome-protocols.md, + rationale: 'Unusually large documentation set for its size: docs/development.md, + configuration.md, contracts.md, canon-mapping.md, canon-interface-card.yaml, + family-dataspace-onboarding.md, registration-identity-and-factor-model.md, prepared-accounts-and-entitlement-claims.md, + hats-realms-services-assets-access-profiles.md, onboarding-journeys-and-welcome-protocols.md, and more — scope and contracts are thoroughly documented.' availability: - current: A1 - target: A3 + current: A4 + target: A4 confidence: medium - rationale: Python package with `make test`; no packaged distribution or hosted service confirmed in - this sweep. + rationale: 'Source interface assessed 2026-10-14: Accounts, identity links, membership, + MFA and recovery portal, advisory catalog. Availability describes the delivery + form, not production acceptance. Application readback is advisory; applications + must enforce their own authorization.' external_evidence: completeness: level: C2 @@ -41,37 +46,45 @@ external_evidence: confidence: low basis: consumer_quality_signals known_reliability_risks: - - breadth of documented scope not independently verified against implementation completeness in this - sweep + - breadth of documented scope not independently verified against implementation + completeness in this sweep discovery: - intent: Provide a headless, multi-application, multi-tenant user-management engine covering the full - registration-to-entitlement lifecycle, reusable across NetKingdom-family applications. + intent: Accounts, identity links, membership, MFA and recovery portal, advisory + catalog includes: - - multi-tenant registration and identity/factor model - - entitlement claims and hats/realms/services/assets access profiles - - onboarding journeys and welcome protocols + - Accounts, identity links, membership, MFA and recovery portal, advisory catalog excludes: - - IAM/OIDC protocol implementation itself (see key-cape, net-kingdom) + - Application readback is advisory; applications must enforce their own authorization assumptions: [] - use_cases: [] + use_cases: + - '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' + - 'U10: Operator recovers identity, custody or data with independently held recovery + material' research_memos: [] availability: - current_level: A1 - target_level: A3 + current_level: A4 + target_level: A4 current_artifacts: - - Python package (`user-engine`) + - SCOPE.md + - README.md target_artifacts: [] consumption_modes: - - library import + - HTTP API + - source relations: depends_on: [] supports: [] - related_to: [] + related_to: + - capability.iam.key-cape + - capability.identity.tenant-facts + - capability.authorization.policy-evaluate + - capability.audit.event-retain evidence: documentation: - - docs/contracts.md - - docs/registration-identity-and-factor-model.md - - docs/canon-mapping.md + - SCOPE.md + - README.md tests: - tests/ consumer_feedback: [] @@ -79,45 +92,43 @@ evidence: incidents: [] consumer_guidance: recommended_for: - - multi-tenant applications needing a headless user/identity/entitlement engine + - Human signs in with MFA and manages account or factor recovery + - Application combines identity, tenant and resource facts and enforces a bound + decision + - Operator recovers identity, custody or data with independently held recovery material not_recommended_for: - - needs for the IAM/OIDC protocol layer itself (see key-cape/net-kingdom) + - Application readback is advisory; applications must enforce their own authorization known_limitations: - - large documented scope; implementation completeness not independently verified in this sweep -promotion_history: [] + - Application readback is advisory; applications must enforce their own authorization + - 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: A1 + to: A4 + rationale: Interface-form reassessment from current owner sources; no completeness/reliability + promotion. + author: codex --- -# Headless Multi-Tenant User Engine +# User lifecycle and account journeys -## Overview +Accounts, identity links, membership, MFA and recovery portal, advisory catalog. -`user-engine` is a headless, multi-application, multi-tenant user-management engine: registration, identity/factor models, prepared accounts and entitlement claims, hats/realms/services/assets access profiles, and onboarding journeys, documented in unusual depth for its size. +## Reuse boundary -## Assessment notes +Application readback is advisory; applications must enforce their own authorization. -### Discovery +## Supported use cases -Unusually large documentation set for its size: docs/development.md, configuration.md, contracts.md, canon-mapping.md, canon-interface-card.yaml, family-dataspace-onboarding.md, registration-identity-and-factor-model.md, prepared-accounts-and-entitlement-claims.md, hats-realms-services-assets-access-profiles.md, onboarding-journeys-and-welcome-protocols.md, and more — scope and contracts are thoroughly documented. +- 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 +- U10: Operator recovers identity, custody or data with independently held recovery material -### Availability +## Evidence and integration -Python package with `make test`; no packaged distribution or hosted service confirmed in this sweep. +- [SCOPE.md](../../SCOPE.md) +- [README.md](../../README.md) -### Completeness - -First-pass honest assessment from the REUSE-WP-0017 coverage campaign -(reuse-surface). No external consumer feedback exists yet; levels reflect -scope-vs-intent documentation quality, not internal code quality. - -### Reliability - -No production consumer telemetry exists yet; reliability level is -intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence. - -## Promotion checklist - -- [x] ID follows `capability..` pattern -- [x] Maturity enums match `specs/CapabilityMaturityStandard.md` -- [x] `external_evidence` is populated separately from `maturity` -- [ ] Relations reference valid capability IDs (none yet) -- [x] Index entry added in `registry/indexes/capabilities.yaml` +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. diff --git a/registry/indexes/capabilities.yaml b/registry/indexes/capabilities.yaml index e0cb8e2..6e000fd 100644 --- a/registry/indexes/capabilities.yaml +++ b/registry/indexes/capabilities.yaml @@ -1,19 +1,23 @@ version: 1 -updated: '2026-07-06' +updated: '2026-10-14' domain: helix_forge capabilities: - id: capability.identity.user-engine - name: Headless Multi-Tenant User Engine - summary: Headless, multi-application, multi-tenant user management engine covering registration, identity/factor - models, entitlement claims, hats/realms/services/assets access profiles, and onboarding journeys. - vector: D4 / A1 / C2 / R0 + name: User lifecycle and account journeys + summary: Accounts, identity links, membership, MFA and recovery portal, advisory + catalog. domain: communication status: draft owner: user-engine - path: registry/capabilities/capability.identity.user-engine.md tags: - identity - user-management - multi-tenant + - security + - netkingdom + - framework-reuse + vector: D4 / A4 / C2 / R0 + path: registry/capabilities/capability.identity.user-engine.md consumption_modes: - - library import + - HTTP API + - source