Resources

Architecture

Prism is one layer of three. Each layer owns a distinct responsibility, and the boundaries are structural rather than conventional — Prism never reimplements what sits beneath it.

The three layers

01

Prism

Consumer identity and relationship layer

Owns

  • Prism iD, profile and verification level
  • Credential wallet and selective disclosure
  • Friends, groups and brand connections
  • Purchases, memberships, tickets and rewards
  • Agreements and e-signature workflows
  • Real-world iD mode and rotating venue credentials

Never

  • Governance, voting or constitutional logic
  • Collective intelligence or AI reasoning
  • Chain keys or direct on-chain writes
02

Organic DÃO

Consent, event truth, intelligence and governance

Owns

  • Consent-as-a-Service and capability grants
  • The Event Spine and institutional memory
  • Collective intelligence and cognitive routing
  • Governance, proposals and voting
  • Hashing, Merkle roots and anchor orchestration

Never

  • Consumer identity presentation
  • Retail-facing wallet or social surfaces
03

ADI Chain

Cryptographic settlement and anchoring

Owns

  • Immutable anchoring of hashes and proofs
  • Verification of credential issuance and revocation
  • Settlement infrastructure

Never

  • Any raw personal data: names, addresses, document numbers, DOB, biometrics, purchase contents

Prism's own progression

  1. 1

    Identity

    One verified iD per human, with graded verification level.

  2. 2

    Relationships

    Private social graph, groups and verified brand connections.

  3. 3

    Permissions

    Purpose-scoped, time-bounded, revocable grants per data category.

  4. 4

    Transactions

    Purchases, memberships, tickets, rewards and signed agreements.

  5. 5

    Experiences

    Real-world access, venue credentials and brand interactions.

Data flow

Every consented Prism event travels the same path. Nothing reaches the chain that has not first been filtered, hashed and consented.

PRISM USER ACTION
   |
   v
PRISM EVENT
   |
   v
PRIVACY + CONSENT FILTER        (strip / hash PII, drop unconsented fields)
   |
   v
ORGANIC DAO INGESTION API       (signed, versioned, idempotent)
   |
   v
ORGANIC EVENT SPINE
   |
   +--> COLLECTIVE INTELLIGENCE / MEMORY / GOVERNANCE
   |
   v
HASH / MERKLE ANCHOR
   |
   v
ADI CHAIN
   |
   v
ANCHOR REFERENCE  ------------->  back to PRISM (state, tx hash, network)

Provider interfaces

Every supplier sits behind a Prism-owned interface, so any of them can be replaced without touching the identity model. Each ships with a labelled mock adapter for development.

InterfaceInitial adapterScope
IdentityVerificationProviderPersonaGovernment ID, licence, passport, selfie liveness, manual review, webhooks
PhoneVerificationProviderTwilio VerifyOTP send / verify / resend, expiry, attempt limits, rate limiting, recovery
ContractProviderSignNowTemplates, field population, signer invitations, embedded signing, audit trail
BiometricIdentityProviderIris ID (candidate)Enrolment, encrypted template reference, verification, revocation
CollectiveIntelligenceProviderOrganic DÃOConsent events, observations, outcomes, capability grants
ChainAnchorProviderOrganic DÃO → ADIHash submission, anchor state, transaction reference