Files
identity-canon/research/CorpusIndex.md
tegwick bd272151af Model reputation as counterparty assurance gradient across four tiers
Add research on the journey from gamable opinion signals (reviews, ratings)
through observed metrics (PAYDEX, SLA stats), financial commitments (bonds,
escrow), and adjudicated outcomes (arbitration, courts). Resolve OpenQuestions:
no Reputation entity; use Reputation Signal, Performance Evidence, Commercial
Commitment, and Adjudication Outcome with Counterparty Assurance Gradient pattern.
2026-06-21 22:57:28 +02:00

2.7 KiB

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

commercial-identity

  • commercial-identity-synthesis.md
  • commercial-trust-binding-theory.md
  • legal-person-agency-contract.md
  • lei-gleif-legal-entity-identifier.md
  • duns-commercial-credit-identity.md
  • kyc-aml-commercial-identity-binding.md
  • eidas-eudi-legal-person-wallet.md
  • salesforce-crm-commercial-record.md
  • beneficial-ownership-kyc-boi.md
  • registry-identifier-subtypes.md
  • reputation-assurance-gradient.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.