Zones are operating environments, not integrations.

Each zone is provisioned from a factory contract — access, governance, liquidity, and identity are structural components, not middleware layers you add later.

ZBC/02·Zone Anatomy

FAC · SELECTED

ORIGINZone Factory Contract

SCOPEFull environment provisioning

OUTPUTDeployed zone with initialized state

Zone deployment begins with a factory call, not manual contract composition. The factory receives provisioning parameters and deploys the zone as a complete initialized environment.

ZBC/03·Zone Lifecycle

STAGES: 5

LCY-01

Provision

Factory called with provisioning parameters — zone environment deployed as a single initialized contract.

LCY-02

Configure

Role NFTs minted, HAMP surfaces attached, governance model wired. The zone surface is established.

LCY-03

Activate

Vault initialized. Governance hooks live. Zone is open to role-holding members.

LCY-04

Operate

Members interact. Hooks fire against real activity. Module logic executes. Governance proposals enter the queue.

LCY-05

Evolve

Governance execution updates zone parameters and attached logic over time as the environment responds to use.

ZBC/04 // DZONES

dZones is a live Zone deployment.

REFERENCE DEPLOYMENT

Access control, governance, vault, and identity operating as a single coherent system. dZones is the existence proof that the Zone architecture becomes a usable product surface.

→ Review the dZones deployment

ZBC/SIGNAL

Build on the Zone layer.

Bring the product problem. We'll show you where the Zone architecture fits it.

Start the Build Signal Review the Zone Docs

SIGNAL OPEN