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

Governance Policy template route

Share this route when the motion is setting a durable governance rule rather than shipping a one-off change.

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

Signaling readiness

Draft can stay flexible before signaling.

These checks become blocking only when the motion moves into signaling. Draft and discussion can stay incomplete while the operator shapes the contract.

Gate inactive before signaling

Title is specific enough50 chars drafted
Question reads like a real holder decision81 chars drafted
Summary explains why the motion exists114 chars drafted
Execution path defines shipped proof130 chars drafted

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

Policy Motion // Set the next DAOrg operating rule

Use this when the org is deciding how DAOrg should behave, review work, or publish execution proofs going forward.

Question: Should DAOrg adopt this governance policy as a durable rule for future decisions?
Status: Discussion
Signal Window: Not live yet
Execution: Spell out the rule, how it changes operator behavior, and what receipt or architecture record will prove the policy is now active.

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=policy#daorg-create-proposal