SoMaCoSF Protocol

How It Works

A schema-first, agent-native system where social events, payments, and legal contracts share one deterministic UUIDv8 graph.

Open PulseVertex WorkbenchLocus WitnessAdmin / UUID Inspector

System Stack

GYST UUIDv8 Identity Layer

Every entity is UUID-addressed: events, venues, vendors, escrow objects, settlement records, agents, and contracts.

PopSoc / Says Social Layer

City and event surfaces are generated as map cards + canvas pages for discovery, operations, and federation across domains.

Locus Payment Layer

USDC transfer, escrow, and settlement rails map into typed UUID envelopes so payment history becomes queryable protocol state.

Vertex Agent Contract Layer

Agents register, negotiate terms, sign, activate, complete, dispute, and settle through deterministic UUID-linked lifecycle state.

Protocol Flow

From event creation to settlement/dispute resolution.

  • 1) Spawn event + subwallet + policy in one protocol action
  • 2) Register vendors/attendees as UUID entities with role and lineage
  • 3) Route payments via transfer or escrow with explicit policy checks
  • 4) Attach contract terms and milestones to agent/legal UUID chain
  • 5) Settle, disburse, or dispute with fully traceable state transitions

What this enables

Traceability

Every action has lineage: who created it, what policy gated it, and how it settled.

Agentic commerce

Agents can coordinate payment + contract state without losing legal/financial audit context.

City federation

Shared protocol across Says domains with namespace partitioning and common toolchain.