First make the runtime real.
Then coordinate it as a network.
DAOrg is not the first step. The live ODEI path today is verified holder access on Base, Launch Builder, ODEI.app desktop activation, and reviewed provisioning for one bounded runtime and first mission. DAOrg is the next coordination layer that follows once those operator runtimes are real.
$ODAI on Base
Holder verification is the live access boundary. The current path is simple: verify the wallet on Base, reopen the operator surface, and carry the same holder identity into Builder and ODEI.app.
Your Runtime
Builder is the live shaping surface. Choose the runtime boundary, governance posture, execution surfaces, and first mission before activation. ODEI.app then materializes that runtime locally.
First Mission
ODEI does not jump from token to fleet fantasy. Reviewed provisioning locks identity, commercial boundary, governance, and the first mission before the runtime is treated as live.
Coordination Layer
DAOrg remains the future network layer above verified operator runtimes. Governance becomes real only after ODEI proves durable runtime boundaries, continuity, and first outcomes across the agent base.
Verified Holder Access
Wallet verification on Base unlocks the operator surface, profile, and Builder entry path. ODEI treats that verified holder session as the only valid start of the runtime lane.
Launch Builder + ODEI.app
The live product is Builder plus the desktop runtime. Builder shapes the contract; ODEI.app runs the local World Model, agent workspace, and continuity layer on the machine you control.
Local World Model Runtime
Your runtime uses ODEI's graph stack, but the operator truth stays local: Neo4j Community Edition, SQLite continuity, MCP services, and provider lanes for Claude, Codex, or Gemini.
Governance Boundary
Governance is already visible as a boundary, not as fake token theater. The operator dashboard tracks clearance, entitlement state, and the reviewed activation lane before any larger network coordination opens.
Reviewed Provisioning
The live gating step is reviewed provisioning. Identity, commercial boundary, governance mode, and the first mission are locked before the runtime is treated as active.
Future Coordination Rights
DAOrg is still the strategic destination, but it comes after ODEI proves real operator runtimes, first missions, and cross-runtime coordination. This page now reflects that sequencing honestly.
"The real product path is Builder-first. Verify the holder wallet on Base. Open Launch Builder. Shape the runtime boundary, governance mode, execution surfaces, and first mission. Install ODEI.app with Neo4j Community Edition. Reviewed provisioning then links identity, commercial boundary, and launch gate before the runtime is considered live. DAOrg is the future coordination layer above that foundation, not a substitute for it."
Base verification + operator session
The live token gate is wallet verification on Base. That verified holder session reopens Profile, Builder, and the local activation lane.
LiveLaunch Builder
The public Builder surface is live now. Operators shape runtime boundary, governance mode, execution surfaces, and the first mission before activation.
LiveODEI.app
The runtime truth lives in the installed desktop app, not in a browser simulation. World Model, agent workspace, and continuity all run on the operator's machine.
LiveNeo4j Community Edition
Neo4j Community Edition is the explicit local graph dependency for World Model state, memory structure, and the persistent context topology used by ODEI.app.
LiveSQLite + MCP services
Conversation continuity, graph context, and runtime coordination stay local through SQLite plus the bundled MCP services inside the installed environment.
LiveClaude, Codex, Gemini
ODEI sits above the model lane. The operator keeps the provider they already trust while ODEI preserves memory, governance, continuity, and receipts above it.
LiveReviewed provisioning
The live gating rule is reviewed provisioning. Identity, commercial boundary, governance mode, and first mission are checked before the runtime is promoted as active.
BuildingClearance + entitlement state
What exists today is a visible governance boundary in the operator dashboard: clearance, activation entitlement state, and the exact next upgrade path. Larger network governance follows later.
BuildingFirst the runtime.
Then the network.
Then DAOrg.
The current truth is Builder, ODEI.app, local runtime components, and reviewed provisioning. Hold $ODAI to enter the live operator path now, not a fictional governance layer that has not shipped yet.