---
id: capability.identity.vocabulary-canonicalize
name: Identity Vocabulary Canonicalization
summary: Define and maintain an implementation-neutral vocabulary for identity-related concepts across overlapping domains.
owner: identity-canon
status: draft
domain: helix_forge
tags:
  - identity
  - terminology
  - research

maturity:
  discovery:
    current: D4
    target: D6
    confidence: medium
    rationale: >
      identity-canon has researched overlapping terminology across IAM,
      directory, federation, and authorization domains, but use-case saturation
      is not yet demonstrated.
  availability:
    current: A0
    target: A2
    confidence: medium
    rationale: >
      The capability is available as research and canon documentation only.
      Future source modules or libraries could raise availability to A2.

external_evidence:
  completeness:
    level: C2
    name: Partial
    confidence: low
    basis: scope_vs_intent_and_consumer_expectations
    satisfied_expectations:
      - draft canonical glossary exists
      - terminology conflict map exists
      - conceptual model and scenario tests exist
    broken_expectations:
      - individual source notes are not fully backfilled
      - many mappings remain candidate rather than finalized
    out_of_scope_expectations:
      - operating identity providers
      - provisioning or authorization engines
  reliability:
    level: R0
    confidence: low
    basis: consumer_quality_signals
    known_reliability_risks:
      - draft canon terms may change as source evidence is backfilled

discovery:
  intent: >
    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.
  includes:
    - canonical glossary maintenance
    - terminology conflict mapping
    - conceptual model and scenario tests
    - research corpus indexing
  excludes:
    - identity provider implementation
    - account lifecycle services
    - authorization policy enforcement
  assumptions:
    - external product mappings remain separate from canonical definitions
  use_cases:
    - UC-RS-004
    - UC-RS-006
  research_memos:
    - identity-canon/ResearchProposal.md
    - identity-canon/canon/CanonicalGlossary.md

availability:
  current_level: A0
  target_level: A2
  current_artifacts:
    - identity-canon/canon/CanonicalGlossary.md
    - identity-canon/terminology/TerminologyConflictMap.md
    - identity-canon/model/ConceptualModel.md
  target_artifacts:
    - identity-canon/packages/identity-vocabulary
  consumption_modes:
    - informational
    - markdown research artifacts

relations:
  depends_on: []
  supports:
    - capability.feature-control.evaluate
    - capability.registry.register
  related_to:
    - capability.identity.subject-resolution

evidence:
  documentation:
    - identity-canon/INTENT.md
    - identity-canon/canon/CanonicalGlossary.md
  tests: []
  consumer_feedback: []
  bug_reports: []
  incidents: []

consumer_guidance:
  recommended_for:
    - architecture and planning conversations involving overloaded identity terms
    - comparing IAM, directory, and authorization vocabulary without forcing one product model
  not_recommended_for:
    - runtime identity resolution
    - assuming draft canon entries are finalized standards
  known_limitations:
    - 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.