How to use identity-atoms

Read the catalog over HTTPS

Every artifact is served under stable URLs with correct content-types:

curl https://identity-atoms.com/exports/catalog.json
curl https://identity-atoms.com/atoms/auth-method/oauth2.json
curl https://identity-atoms.com/identities/federated-persona.json
curl https://identity-atoms.com/schemas/atom-v1.json

Resolve an identity composition

An identity composition assembles auth methods, claim types, and trust frameworks into a complete identity profile. To instantiate, fetch each referenced atom and compose:

// pseudo-code
const composition = await fetch("/identities/federated-persona.json").then(r => r.json());
const authMethod = await fetch(uriToUrl(composition.references.auth_method.ref)).then(r => r.json());
const claimTypes = await Promise.all(
  composition.references.claim_types.map(r => fetch(uriToUrl(r.ref)).then(r => r.json()))
);
const trustFramework = await fetch(uriToUrl(composition.references.trust_framework.ref)).then(r => r.json());
const identity = buildIdentityProfile({ authMethod, claimTypes, trustFramework });

Compatibility rules

Rules in /exports/catalog.json (under the rules key) declare predicates over atoms. Example: a trust-chain rule may require that a given auth-method is paired with specific claim-validation policies. A composition that violates a require-effect rule is malformed.

Cross-vendor portability

v0.1 ships the catalog and its JSON Schema. Adapters to specific identity vendors (OIDC providers, SAML, WebAuthn) are v0.2 work — they translate auth-method atoms into vendor-native protocol flows and bind trust-framework atoms to the vendor's trust model.