user-engine/registry/capabilities/capability.identity.user-engine.md

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.identity.user-engine	User lifecycle and account journeys	Accounts, identity links, membership, MFA and recovery portal, advisory catalog.	user-engine	draft	communication	identity user-management multi-tenant security netkingdom framework-reuse	discovery availability current target confidence rationale D4 D5 high 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. current target confidence rationale A4 A4 medium 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.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C2 low scope_vs_intent_and_consumer_expectations registration/identity/factor model documented entitlement claims and access-profile model (hats/realms/services/assets) documented canon mapping and interface card present level confidence basis known_reliability_risks R0 low consumer_quality_signals breadth of documented scope not independently verified against implementation completeness in this sweep	intent includes excludes assumptions use_cases research_memos Accounts, identity links, membership, MFA and recovery portal, advisory catalog Accounts, identity links, membership, MFA and recovery portal, advisory catalog Application readback is advisory; applications must enforce their own authorization 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	current_level target_level current_artifacts target_artifacts consumption_modes A4 A4 SCOPE.md README.md HTTP API source	depends_on supports related_to capability.iam.key-cape capability.identity.tenant-facts capability.authorization.policy-evaluate capability.audit.event-retain	documentation tests consumer_feedback bug_reports incidents SCOPE.md README.md tests/	recommended_for not_recommended_for known_limitations 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 Application readback is advisory; applications must enforce their own authorization 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.	date dimension from to rationale author 2026-10-14 availability A1 A4 Interface-form reassessment from current owner sources; no completeness/reliability promotion. codex

User lifecycle and account journeys

Accounts, identity links, membership, MFA and recovery portal, advisory catalog.

Reuse boundary

Application readback is advisory; applications must enforce their own authorization.

Supported 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

Evidence and integration

• SCOPE.md
• README.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.