Files
identity-canon/registry/capabilities/capability.identity.subject-resolution.md
tegwick c66bebc9c3 Add capability registry scaffold and seed entries from reuse-surface
Bootstrap registry/indexes/capabilities.yaml and migrate helix_forge
capability entries owned by this repository for federation publishing.
2026-06-16 01:34:23 +02:00

3.3 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.subject-resolution Identity Subject Resolution Resolve who or what is acting in a context by mapping principals, accounts, actors, and identifiers to a stable subject model. identity-canon draft helix_forge
identity
subject
architecture
discovery availability
current target confidence rationale
D3 D5 medium Subject/principal terminology is explored in identity-canon conflict maps and conceptual model, but dedicated use-case grounding is incomplete.
current target confidence rationale
A0 A4 low Canon and research artifacts exist; no standalone resolver service or SDK is registered yet.
completeness reliability
level name confidence basis satisfied_expectations broken_expectations out_of_scope_expectations
C1 Fragmentary low scope_vs_intent_and_consumer_expectations
overloaded subject and principal terms are mapped as candidates
no runtime resolver artifact
canonical subject model not finalized across all actor types
authentication protocol implementation
credential storage
level confidence basis known_reliability_risks
R0 low consumer_quality_signals
draft terminology may change during source-note backfill
intent includes excludes assumptions use_cases research_memos
Give planners and implementers a consistent subject concept for authorization, feature control, tenancy, and agent workflows without collapsing product-specific identity models.
subject vs principal vs account distinctions
actor type modeling
identifier resolution concepts
authentication execution
credential issuance
directory provisioning
vocabulary canonicalization supports but does not replace subject resolution
UC-RS-004
identity-canon/terminology/TerminologyConflictMap.md
identity-canon/model/ConceptualModel.md
current_level target_level current_artifacts target_artifacts consumption_modes
A0 A4
identity-canon/model/ConceptualModel.md
identity-canon/canon/CanonicalGlossary.md
identity-canon/packages/subject-resolution-sdk
informational
depends_on supports related_to
capability.identity.vocabulary-canonicalize
capability.feature-control.evaluate
capability.statehub.workstream-coordinate
documentation tests consumer_feedback bug_reports incidents
identity-canon/canon/CanonicalGlossary.md
identity-canon/scenarios/ScenarioTests.md
recommended_for not_recommended_for known_limitations
architecture planning where subject/principal/account terms overlap
runtime authentication or token validation
treating draft canon as finalized resolver behavior
resolver artifacts are not yet available

Identity Subject Resolution

Overview

Subject resolution defines how actors and identifiers map to a stable subject concept for downstream capabilities such as feature evaluation and coordination. Today this capability is planning-heavy (D3/A0).