Files
reuse-surface/registry/capabilities/capability.identity.vocabulary-canonicalize.md

4.1 KiB

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance
id name summary owner status domain tags maturity external_evidence discovery availability relations evidence consumer_guidance
capability.identity.vocabulary-canonicalize Identity Vocabulary Canonicalization Define and maintain an implementation-neutral vocabulary for identity-related concepts across overlapping domains. identity-canon draft helix_forge
identity
terminology
research
discovery availability
current target confidence rationale
D4 D6 medium identity-canon has researched overlapping terminology across IAM, directory, federation, and authorization domains, but use-case saturation is not yet demonstrated.
current target confidence rationale
A0 A2 medium The capability is available as research and canon documentation only. Future source modules or libraries could raise availability to A2.
completeness reliability
level name confidence basis satisfied_expectations broken_expectations out_of_scope_expectations
C2 Partial low scope_vs_intent_and_consumer_expectations
draft canonical glossary exists
terminology conflict map exists
conceptual model and scenario tests exist
individual source notes are not fully backfilled
many mappings remain candidate rather than finalized
operating identity providers
provisioning or authorization engines
level confidence basis known_reliability_risks
R0 low consumer_quality_signals
draft canon terms may change as source evidence is backfilled
intent includes excludes assumptions use_cases research_memos
Provide a reusable planning primitive for identity vocabulary so architects and agents can compare overlapping terms consistently without collapsing product-specific meanings into one ambiguous label.
canonical glossary maintenance
terminology conflict mapping
conceptual model and scenario tests
research corpus indexing
identity provider implementation
account lifecycle services
authorization policy enforcement
external product mappings remain separate from canonical definitions
UC-RS-004
UC-RS-006
identity-canon/ResearchProposal.md
identity-canon/canon/CanonicalGlossary.md
current_level target_level current_artifacts target_artifacts consumption_modes
A0 A2
identity-canon/canon/CanonicalGlossary.md
identity-canon/terminology/TerminologyConflictMap.md
identity-canon/model/ConceptualModel.md
identity-canon/packages/identity-vocabulary
informational
markdown research artifacts
depends_on supports related_to
capability.feature-control.evaluate
capability.registry.register
capability.identity.subject-resolution
documentation tests consumer_feedback bug_reports incidents
identity-canon/INTENT.md
identity-canon/canon/CanonicalGlossary.md
recommended_for not_recommended_for known_limitations
architecture and planning conversations involving overloaded identity terms
comparing IAM, directory, and authorization vocabulary without forcing one product model
runtime identity resolution
assuming draft canon entries are finalized standards
source-note backfill is incomplete
mappings may remain candidate until evidence review completes

Identity Vocabulary Canonicalization

Overview

This capability makes identity vocabulary reusable for planning across adjacent domains. It is intentionally research-heavy and informational, illustrating a D4/A0/C2/R0 vector that contrasts with implementation-ready entries.

Current reuse mode

Consumers read canon, terminology, and model artifacts in the identity-canon repository. The value is planning reuse through shared vocabulary, not runtime integration.

Relation to adjacent capabilities

Feature-control evaluation depends on consistent subject and tenant concepts. This capability supports that planning layer without providing runtime identity services itself.