Wallet Setup Open DAOrg

DAOrg needs JavaScript for wallet access.

The preview stays readable, but holder verification, ODEI App session handoff, holder signaling, and motion actions need JavaScript enabled.

Motion Studio

Open the next DAOrg question

Every field becomes part of the motion contract. Holders see exactly what they approve and what shipped.

Governance Lobby Agent Builds

Step 1

Wallet-verified governance

Connect the holder wallet first. Motion creation and weighted signaling inherit the same verified identity.

Current session

No wallet is verified in this browser yet.

Next unlock

Verify the holder wallet, then come straight back to Motion Studio.

Open ODEI App profile Wallet Setup

If this browser already has a live app.odei.ai session, DAOrg will import it automatically. Continue from ODEI App is the manual fallback.

Access Connect wallet or continue from ODEI App to edit.

No email confirmation is required in v.0.1 preview. Wallet Setup and ODEI App sessions are the active access paths.

Title Decision Question Summary Execution Path Initial Status Signal Window

Starter templates

Browse starter contracts now. Verified holder access unlocks editing and publishing.

Ratify Surface Confirm a governance or product baseline. Ship Product Change Approve a concrete build path and shipped artifact. Reward Operator Work Move contribution into a visible reward decision. Governance Policy Set a durable rule for how DAOrg should operate.

Template Route

Ship Product Change template route

Share this route when the org should open a concrete product change with a shipped artifact path already implied.

/daorg/studio?template=ship#daorg-create-proposal

Signaling readiness

Signaling opens after the contract is specific enough for holders to signal.

Strengthen the motion before opening weighted signaling. Holders should see a crisp question, reason, and execution path.

2/4 checks ready

Title is specific enough54 chars, minimum met
Question reads like a real holder decision77 chars, minimum met
Summary explains why the motion exists95/120 chars required
Execution path defines shipped proof151/180 chars required

Local draft

No local draft yet.

This browser will keep the motion contract while you shape it, then restore it after refresh on this device.

Motion Studio

Publish motions that can actually survive governance and ship.

Good motions are specific, executable, and honest about what the org is really deciding. This lane should read like a contract, not a brainstorm.

State one decision

The title and question should make it obvious what a holder is signaling for or against.

Define the execution path

Describe the deliverable, the receipt, and what artifact proves the work actually landed.

Choose the right opening state

Use draft for shaping, discussion for live debate, and signaling only when weighted holder signaling should start now.

Live Motion Preview

Execution Motion // Ship the next DAOrg product change

Use this when holders are deciding on a concrete shipped change, not just discussing direction.

Question: Should DAOrg approve this product change for execution on the published path?
Status: Signaling
Signal Window: 5 day signaling window
Execution: Describe the exact shipped change, responsible operator, destination route, and the artifact URL that will prove execution once the motion is complete.

Share View

Share the exact governance view.

Clean links for live motions, pipeline, sync status, rewards, receipts, and Motion Studio.

Overview Live Motions Pipeline Sync Status Receipts Rewards Motion Studio

Motion Studio link /daorg/studio?template=ship#daorg-create-proposal