Life

Architecture

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

Axioms Architecture Security Glossary

The three layers

Coexist

Consumer identity and relationship layer

Owns

Coexist 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

Coexist DAO

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

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

Coexist's own progression

1
Identity
One verified iD per human, with graded verification level.
2
Relationships
Private social graph, groups and verified brand connections.
3
Permissions
Purpose-scoped, time-bounded, revocable grants per data category.
4
Transactions
Purchases, memberships, tickets, rewards and signed agreements.
5
Experiences
Real-world access, venue credentials and brand interactions.

Data flow

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

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

Provider interfaces

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

Interface	Initial adapter	Scope
IdentityVerificationProvider	Persona	Government ID, licence, passport, selfie liveness, manual review, webhooks
PhoneVerificationProvider	Twilio Verify	OTP send / verify / resend, expiry, attempt limits, rate limiting, recovery
ContractProvider	SignNow	Templates, field population, signer invitations, embedded signing, audit trail
BiometricIdentityProvider	Iris ID (candidate)	Enrolment, encrypted template reference, verification, revocation
CollectiveIntelligenceProvider	Coexist DAO	Consent events, observations, outcomes, capability grants
ChainAnchorProvider	Coexist DAO → ADI	Hash submission, anchor state, transaction reference