Seeded research project with INTENT.md, ResearchProposal.md and initial work.

This commit is contained in:
2026-06-04 12:12:07 +02:00
parent c190c62cd5
commit 8a1482098b
28 changed files with 2621 additions and 0 deletions

View File

@@ -0,0 +1,50 @@
# Nist 800 63 4
## Source Type
TODO: Identify whether this is a standard, specification, product documentation, academic concept, architecture pattern, or implementation reference.
## Domain
TODO: Classify the source domain.
## Why This Source Matters
NIST Digital Identity Guidelines: identity proofing, authenticator assurance, federation assurance.
## Key Concepts
TODO:
- concept 1
- concept 2
- concept 3
## Relevant Terminology
TODO: Extract terms used by the source and note their source-specific meaning.
## Modeling Assumptions
TODO: Capture assumptions made by the source about users, accounts, organizations, tenants, groups, roles, identities, relationships, or credentials.
## Identity-Canon Implications
TODO: Explain what this source suggests for the canonical identity model.
## Terminology Conflicts
TODO: Record where this source uses terms differently from other sources.
## Candidate Canonical Mappings
TODO: Map source-specific concepts to identity-canon candidate concepts.
## Open Questions
TODO:
- Question 1
- Question 2
## References
TODO: Add canonical URLs, RFC/spec identifiers, documentation links, and citation notes.

View File

@@ -0,0 +1,50 @@
# Oidc Core Subject Identifiers
## Source Type
TODO: Identify whether this is a standard, specification, product documentation, academic concept, architecture pattern, or implementation reference.
## Domain
TODO: Classify the source domain.
## Why This Source Matters
OpenID Connect subject identifiers, claims, pairwise/public subjects, relying parties, and issuers.
## Key Concepts
TODO:
- concept 1
- concept 2
- concept 3
## Relevant Terminology
TODO: Extract terms used by the source and note their source-specific meaning.
## Modeling Assumptions
TODO: Capture assumptions made by the source about users, accounts, organizations, tenants, groups, roles, identities, relationships, or credentials.
## Identity-Canon Implications
TODO: Explain what this source suggests for the canonical identity model.
## Terminology Conflicts
TODO: Record where this source uses terms differently from other sources.
## Candidate Canonical Mappings
TODO: Map source-specific concepts to identity-canon candidate concepts.
## Open Questions
TODO:
- Question 1
- Question 2
## References
TODO: Add canonical URLs, RFC/spec identifiers, documentation links, and citation notes.

View File

@@ -0,0 +1,50 @@
# Saml Nameid Federation
## Source Type
TODO: Identify whether this is a standard, specification, product documentation, academic concept, architecture pattern, or implementation reference.
## Domain
TODO: Classify the source domain.
## Why This Source Matters
SAML assertions, NameID formats, identity provider/service provider federation terminology.
## Key Concepts
TODO:
- concept 1
- concept 2
- concept 3
## Relevant Terminology
TODO: Extract terms used by the source and note their source-specific meaning.
## Modeling Assumptions
TODO: Capture assumptions made by the source about users, accounts, organizations, tenants, groups, roles, identities, relationships, or credentials.
## Identity-Canon Implications
TODO: Explain what this source suggests for the canonical identity model.
## Terminology Conflicts
TODO: Record where this source uses terms differently from other sources.
## Candidate Canonical Mappings
TODO: Map source-specific concepts to identity-canon candidate concepts.
## Open Questions
TODO:
- Question 1
- Question 2
## References
TODO: Add canonical URLs, RFC/spec identifiers, documentation links, and citation notes.

View File

@@ -0,0 +1,50 @@
# Shared Signals Caep Risc
## Source Type
TODO: Identify whether this is a standard, specification, product documentation, academic concept, architecture pattern, or implementation reference.
## Domain
TODO: Classify the source domain.
## Why This Source Matters
OpenID Shared Signals, CAEP, and RISC for security event exchange and lifecycle/risk signaling.
## Key Concepts
TODO:
- concept 1
- concept 2
- concept 3
## Relevant Terminology
TODO: Extract terms used by the source and note their source-specific meaning.
## Modeling Assumptions
TODO: Capture assumptions made by the source about users, accounts, organizations, tenants, groups, roles, identities, relationships, or credentials.
## Identity-Canon Implications
TODO: Explain what this source suggests for the canonical identity model.
## Terminology Conflicts
TODO: Record where this source uses terms differently from other sources.
## Candidate Canonical Mappings
TODO: Map source-specific concepts to identity-canon candidate concepts.
## Open Questions
TODO:
- Question 1
- Question 2
## References
TODO: Add canonical URLs, RFC/spec identifiers, documentation links, and citation notes.