generated from coulomb/repo-seed
tegwick
3ccf841095
Record B2B SaaS subscriber tenancy and Stripe billing source notes. Resolve the Customer Account open question: reject it as canonical, add Commercial Record and Commercial Relationship to the Record and relationship layers, and document Subscriber as a convenience term only.
89 lines
2.2 KiB
Markdown
89 lines
2.2 KiB
Markdown
# CorpusIndex.md
|
|
|
|
# identity-canon Research Corpus Index
|
|
|
|
This index tracks the research corpus for `identity-canon`.
|
|
|
|
The repository is focused on research and terminology. The corpus should collect source notes, terminology extracts, conflict observations, and modeling implications from standards, product documentation, semantic vocabularies, authorization systems, decentralized identity work, and entity-resolution/privacy research.
|
|
|
|
## Source Stack
|
|
|
|
### identity-provisioning
|
|
|
|
- `scim-rfc7643-rfc7644.md`
|
|
- `ldap-rfc4519-inetorgperson-rfc2798.md`
|
|
- `keycloak-organizations.md`
|
|
- `zitadel-organizations-projects.md`
|
|
- `ory-kratos-keto.md`
|
|
|
|
### authentication-federation
|
|
|
|
- `oidc-core-subject-identifiers.md`
|
|
- `saml-nameid-federation.md`
|
|
- `nist-800-63-4.md`
|
|
- `shared-signals-caep-risc.md`
|
|
|
|
### social-community-graphs
|
|
|
|
- `activitypub-actors-followers.md`
|
|
- `foaf-agent-person-group-onlineaccount.md`
|
|
- `webid-solid-profile.md`
|
|
- `schema-org-person-organization-membership.md`
|
|
|
|
### authorization-relationships
|
|
|
|
- `zanzibar-rebac.md`
|
|
- `openfga-modeling.md`
|
|
- `cedar-principal-action-resource-context.md`
|
|
- `cerbos-abac-derived-roles.md`
|
|
|
|
### verifiable-claims
|
|
|
|
- `did-core.md`
|
|
- `vc-data-model-2.md`
|
|
- `openid4vc.md`
|
|
|
|
### entity-resolution-privacy
|
|
|
|
- `deterministic-vs-probabilistic-matching.md`
|
|
- `synonymity-assertions.md`
|
|
- `gdpr-pseudonymization.md`
|
|
|
|
### commercial-subscription
|
|
|
|
- `b2b-saas-subscriber-tenancy.md`
|
|
- `stripe-customer-billing.md`
|
|
|
|
## Source Note Template
|
|
|
|
Each source note should capture:
|
|
|
|
- source name;
|
|
- source type;
|
|
- domain;
|
|
- key concepts;
|
|
- relevant terminology;
|
|
- assumptions;
|
|
- modeling implications;
|
|
- conflicts with other sources;
|
|
- usefulness for identity-canon;
|
|
- candidate canonical mappings;
|
|
- open questions.
|
|
|
|
## Derived Canon Artifacts
|
|
|
|
The first proposal follow-up pass created these draft artifacts from the
|
|
proposal and seeded corpus topics:
|
|
|
|
- `terminology/TerminologyInventory.md`
|
|
- `terminology/TerminologyConflictMap.md`
|
|
- `canon/DesignPrinciples.md`
|
|
- `canon/CanonicalGlossary.md`
|
|
- `model/ConceptualModel.md`
|
|
- `scenarios/ScenarioTests.md`
|
|
- `OpenQuestions.md`
|
|
- `DownstreamRecommendations.md`
|
|
|
|
These files are candidate canon surfaces. Treat them as hypotheses to test
|
|
while backfilling the individual source notes.
|