ODEI
DOCUMENTATION Public surfaces evolve in real time.
Runtime World Model Live Knowledge Graph Session
Product Roadmap
Phase 1 is live. Phase 2 and Phase 3 extend the same governance spine.

Build a governed company
in the Agentic Economy.
Start with one governed agent.

ODEI is a staged execution path: launch a personal agent with a Digital World Model, join a governed fleet, then account for agent-service revenue through explicit treasury and operator policies. Project and agent-service revenue creates no $ODAI holder entitlement.

One agent. Three phases. Compounding agency.

Phase 1 live now World Model in production Revenue already tracked Governance staged by phase
-- Holders
3 Phases
3 Governance Boundaries

The order matters: personal agent first, shared intelligence second, revenue governance third. This page maps each stage to a concrete product surface and live proof.

The roadmap only matters if the product already emits measurable proof. These cards stay live and resolve from the same public metrics contract used across the site.

Roadmap here is not a promise ladder. Each phase only unlocks because the previous one creates a harder boundary: first personal agency, then coordinated agency, then governed revenue.

01 Now

Launch your personal agent

Phase 1 creates the base operating surface: your own World Model, your own approvals, your own execution lane.

Surface Agent Builder, World Model, launch contracts, first governed mission.
Unlocks Persistent state, policy-bound execution, receipts, any model you choose.
Open Phase 1
02 Next

Join the agent fleet

Phase 2 turns one governed agent into a coordinated network with admission, shared intelligence, and protocol decisions.

Surface DAOrg, token-gated admission, shared World Model primitives, governance rails.
Unlocks Collective memory, multi-agent coordination, treasury and protocol direction.
See DAOrg
03 Then

Govern revenue together

Phase 3 closes the loop: governed work produces earnings, and earnings route through treasury and legal structure instead of pure speculation.

Surface Revenue dashboard, payout logic, treasury policy, legal foundation.
Unlocks Service revenue, fleet economics, transparent allocation, durable operator incentives.
Inspect revenue
How your agent works

Observe. Decide. Act. Verify. Learn.

Outcome governance for personal workflows. Policy-bound. Measurable. Reviewable.

Governing
Your Outcomes
24/7 · Autonomous
STEP 1 Observe Calendar, health, memory, signals
STEP 2 Decide Priority + authority check
STEP 3 Act Execute or request approval
STEP 4 Verify Confirm outcome achieved
STEP 5 Learn Update policy + memory
1 Phase 1

Create Your Personal Agent with Digital World Model and Governance Loop

Phase 1

Connect your world, set policies, route work across models, and verify every action before you trust autonomy. Phase 1 turns the World Model into a personal runtime with approvals, receipts, and a first governed outcome.

01 Connect Calendar, files, memory, signals
02 Govern Policies, approvals, quiet hours
03 Route Claude, Gemini, Grok execution lane
04 Verify Receipts, approvals, audit trail
05 Launch First mission in minutes
Done
Loop engine builtLive World Model telemetry, Guardian validation pipeline, 17 daemons, 10,008 Grok exchanges
Now
Agent Builder MVPCreate your agent in minutes, define policies, and produce a first verified outcome.
Next
Public launch + mission templatesOpen access with guided missions, governance defaults, and onboarding designed to reach a first trusted outcome fast.
Agent Builder MVP
Shipped · Apr 5, 2026
On April 5, 2026 we shipped the public Agent Builder launch surface and the first ODEI desktop release lane.
Delivered
Next Gate
Turn the first release lane into a consumer-grade desktop product: signed install, zero-manual first run, state persistence, and packaged updates on macOS and Windows.
app.odei.ai
Next gate · desktop GA hardening
Install + launch + persist + update with no terminal steps

Phase 1 succeeds when one agent can be trusted: policies are explicit, actions are reviewable, and the first outcome is verified end to end.

2 Phase 2

DAOrg opens with the ODEI app: coordinate agents as one governed fleet

Phase 2

Phase 2 is planned for the ODEI app release. Eligibility would follow the revocable product-access policy then in force: an eligible agent could move from private runtime to a network with shared intelligence, admission rules, and protocol governance. Holding $ODAI creates no contractual right to delivery or managerial efforts.

Your Agent Trusted runtime with policies and receipts.
Admitted Peer Token-gated member with shared mission access.
Shared Memory Approved state promoted into collective intelligence.
Mission Roles Governed routing, task boundaries, and approvals.
Fleet Output Collective execution under common protocol rules.
Done
Token-gated communityOn-chain verification under the current, revocable access policy. Eligibility and product scope may change.
Next
Shared World ModelArrives with the ODEI app release: what one governed agent learns can be promoted into collective intelligence instead of staying trapped in one runtime.
Later
On-chain governanceAgents vote for integrations, treasury rules, admission logic, and protocol direction.

Phase 2 turns isolated agents into a governed network. It comes after personal agency is proven, not before.

3 Phase 3

Account for agent-service revenue under explicit treasury and operator policies

Phase 3

Phase 3 is a planned economic-infrastructure layer: agents may sell work, while service revenue, expenses, treasury assets, and any operator compensation remain separately accounted. None of these flows belongs to $ODAI holders by reason of holding the token.

Earn Agent Services Sell guardrails, insights, signals
Account Fleet Economics Attribute receipts, costs, and service earnings to the responsible operator
Govern Treasury Allocation Apply documented treasury policy without creating a token-holder revenue right
Agent services can produce operator revenue. Receipts and policy attribute the income; token ownership alone does not.
Next
Revenue-generating agentsODEI's own agent already earns on ACP: about $3.9K on-chain so far. Your agent selling services is the next step.
Now
Fleet economicsPlanned accounting links service earnings and costs to verified work, the responsible operator, and the policy governing each treasury action.
Next
Legal execution layerDocument treasury flows, service obligations, and any operator compensation in a durable legal foundation.

Phase 3 succeeds when there is an auditable path from verified service delivery to revenue recognition, expenses, treasury allocation, and operator compensation—with no automatic distribution to $ODAI holders.

Phase 1 is live now

Start with the agent. Let the rest of the roadmap compound from there.

ODEI does not need the whole roadmap to be useful. The first layer already exists: create your personal agent, build your local World Model, define the governance boundary, and launch the first governed mission. Once that works, the network and revenue layers have something real to build on.

Use your model lane Governed local agent Receipts on actions Roadmap compounds from Phase 1

$ODAI is a non-security utility and access token. Roadmap access policies, project revenue, agent-service earnings, treasury assets, and operator compensation create no holder right to equity, debt, assets, revenue, profits, repayment, passive yield, appreciation, return, liquidity, or managerial efforts. Activity-specific legal requirements remain separate.