Track 3 · Phase 2 draft
Federation without centralization.
Seven parties keep their own systems, identity and raw data. A regional exchange holds only contracts, policy and what is derived from them.
Four rules the diagram keeps.
Data stays local
Raw records never leave a party's account. Only contract-shaped, classified records cross the line, and a party can revoke them.
Contracts, not copies
The region owns the shapes, the policy and the audit trail. It does not own a regional copy of anyone's operations.
Any maturity
A party can be segregated, coordinated or federated-ready inside. The adapter is the only thing the region requires.
Joining is a checklist
An eighth party deploys an adapter, federates its identity and signs an agreement. The seven already connected are untouched.
Seven parties
Who is in the region, what stays inside each boundary.
The exchange
Contracts, semantics, APIs, policy, identity and audit.
Classification
Critical, important or informational; public, internal or restricted.
Field tables
The four sample datasets, column by column.
Onboarding
Adding an eighth party without touching the seven.
The -ilities
Security, governance, scalability and the rest, answered.
Team
Who is building Track 3.