DAOrg is live-ready as a governance surface, while local app proof production and DAOrg-native rewards receipts are being connected into the full operating loop.
Local app proof, app sessions, DAOrg motions, public receipts, and rewards are tracked as separate lanes so preview status stays explicit.
Use this brief before saying DAOrg, app.odei.ai, and the local app are production-ready together.
Publish public-safe execution proof, runtime receipt, and runtime heartbeat artifacts.
DAOrg is live-ready for public governance, but operational completion remains staged until local proof and DAOrg-native reward receipt evidence close.
DAOrg is live-ready as a governance surface, but production-complete language remains gated by explicit proof, reward receipt, and action queue evidence.
Publish public-safe execution proof, runtime receipt, and runtime heartbeat artifacts.
DAOrg. Wallet Setup and ODEI App sessions are the active access paths; email confirmation must not block preview access.
3 required signals / ReadyDAOrg. Runtime readiness allows verified holder writes.
3 required signals / Readyapp.odei.ai. app.odei.ai can hand a verified holder/operator session into DAOrg.
3 required signals / ReadyODEI local app. The local ODEI app is still in development; DAOrg treats private execution proof production as staged until the app emits stable proof artifacts.
3 required signals / StagedDAOrg. A production cycle needs a motion, holder signal, verdict, and proof-indexed public receipt.
4 required signals / ReadyDAOrg rewards lane. Rewards are live operationally, but the DAOrg-native contribution proof to reward receipt loop is still being formalized.
4 required signals / StagedDAOrg operator. ODEI local app must close Runtime receipt available before production-complete language is allowed.
3 required signals / StagedDAOrg. DAOrg claim policy keeps public copy honest while completion evidence, local proof, and DAOrg-native rewards remain staged.
2 required signals / BlockedDAOrg operator. Deploy tooling can snapshot the live runtime, validate rollback targets, and restore NodeBB config before theme rollback.
2 required signals / ReadyConcrete production actions still needed before DAOrg can be called operationally complete.
ODEI local app must close Runtime receipt available before production-complete language is allowed.
Production-complete language remains blocked by action queue completion evidence.
openItems=3
StagedcompletionProgress.pending=3
Stagedcurl -fsS https://app.odei.ai/runtime-receipt.json
Stagedclose-blocked
BlockedEmit the local proof artifacts from the app release.
Runtime proof, receipt, or heartbeat. Proof: Public-safe execution artifact with stable hash and redacted summary
Local app emits public-safe execution proof, runtime receipt, and heartbeat.
Runtime receipt or execution proof must be public-safe and hash-stable before this queue item is closed.
Runtime receipt JSON resolves with stable runtime id, receipt hash, and public-safe summary.
Connect proof ledger with either execution proof or reward receipt.
Proof-indexed decision or reward receipt. Proof: Receipt hash, public proof URL, final state, and linked motion id
Final decision or reward receipt is indexed with a stable hash and public URL.
Receipt must include hash, public URL, final state, and linked motion id before this queue item is closed.
Receipt index exposes hash, public URL, final state, and linked motion id.
Close the first contribution proof to reward receipt cycle.
Reward receipt or execution state. Proof: Reward settlement, execution result, or explicit no-reward decision
Reward settlement, execution result, or explicit no-reward decision is public.
Settlement, execution result, or explicit no-reward decision must be public before this queue item is closed.
Rewards contract or receipt lane exposes settlement, execution result, or explicit no-reward outcome.
A stale heartbeat or receipt can stay visible as history, but it cannot close the local proof lane or unlock production-complete language.
Verifier staged / 0/3 verifier checks passpublicSafe=true, proofHash is sha256, and private payload fields are absent.
receiptHash is sha256 and generatedAt is within the receipt freshness policy.
heartbeatHash is sha256 and generatedAt is not older than the heartbeat freshness policy.
Rewards are already live. ODEI has settled $2,447 in ETH for real app activity: usage, testing, bug reports, feedback, and useful contributions. Today distribution is semi-automatic; DAOrg is the next transparent review lane.
Thank you for the feedback, it is valuable. Rewards are already live: ODEI has settled $2,447 in ETH for real app activity - usage, testing, bug reports, feedback and useful contributions. Next step: DAOrg makes this transparent. https://daorg.odei.ai
Use DAOrg as the public coordination lane while local app proof and DAOrg-native reward receipts are connected.
Connect the staged local proof producer and rewards lane, then close the first full contribution-to-receipt cycle.
Public reads ready. App bridge ready. Staged: Local app proof producer, Rewards lane. Blockers: None.
local-app · private execution proof source. The local ODEI app is still in development; DAOrg treats private execution proof production as staged until the app emits stable proof artifacts.
app.odei.ai · holder identity and operator handoff. app.odei.ai can hand a verified holder/operator session into DAOrg.
daorg.odei.ai · motion, signal, verdict, and receipt lane. Verified holders can use the live governance write loop under DAOrg authority.
daorg.odei.ai · machine-readable proof and receipt index. Agents can inspect proof index packets and individual motion proof packets without guessing internal state.
daorg.odei.ai · contribution proof to reward decision. Rewards are live operationally, but the DAOrg-native contribution proof to reward receipt loop is still being formalized.
Local app, app.odei.ai, and DAOrg each publish one public artifact before the operating loop can be called complete.
Runtime receipt, heartbeat, and execution proof
Private execution stays local until the app emits a public-safe proof artifact with stable hashes and redacted summary.
Public artifact uses stable sha256 hashes.
Raw local memory, prompts, and private payloads are redacted.
Receipt, heartbeat, and execution proof resolve before the lane can pass.
Heartbeat generatedAt is fresh before the lane can close.
Next: Emit runtime receipt and heartbeat, then submit public-safe proof into the app intake route.
Verified holder and operator session handoff
The app owns identity and operator context; DAOrg only trusts the session after the shared handoff secret verifies it.
ODEI_DAORG_AUTH_SECRET is configured before imported sessions are trusted.
Imported session includes holder, operator context, and return target.
DAOrg records source as app-session instead of silently treating it as wallet-only.
Next: Keep ODEI_DAORG_AUTH_SECRET configured before calling app sessions a governance boundary.
Motion proof index, decision receipts, and reward receipt index
DAOrg owns public memory. Motion proof can be indexed now; DAOrg-native rewards need the first complete receipt cycle.
Motion proof index exposes the proofHash for every public motion.
Reward finality requires a DAOrg-native reward receipt, not only the paid fact.
Reward finality verifier passes before DAOrg-native reward finality is claimed.
Decision receipt remains public after execution or reward state changes.
Next: Close the first contribution-to-reward receipt cycle before claiming DAOrg-native reward finality.
DAOrg is product-live as a public governance surface, but production promotion still depends on the explicit gates below.
DAOrg operator. Runtime readiness allows verified holder writes. Run a live motion with a verified holder.
app.odei.ai. app.odei.ai can hand a verified holder/operator session into DAOrg. Keep app and DAOrg holder identity on the same boundary.
ODEI local app. The local ODEI app is still in development; DAOrg treats private execution proof production as staged until the app emits stable proof artifacts. Emit execution proof, runtime receipt, and runtime heartbeat as public-safe artifacts.
DAOrg. A production cycle needs a motion, holder signal, verdict, and proof-indexed public receipt. Run the first end-to-end live motion, signal, verdict, and receipt cycle.
DAOrg rewards lane. Rewards are live operationally, but the DAOrg-native contribution proof to reward receipt loop is still being formalized. Close the first contribution proof to reward receipt cycle and pass the verifier before calling rewards fully native.
DAOrg operator. Deploy tooling can snapshot the live runtime, validate rollback targets, and restore NodeBB config before theme rollback. Validate the latest production snapshot before every high-risk promotion.
This runbook shows the exact first production loop and the evidence still needed before DAOrg can be called operationally complete.
DAOrg operator. Motion Studio draft or governance topic
Stable motion id, title, decision question, and execution path
Holders and humans. Weighted signal on the motion
Wallet-bound votes with visible for, against, and abstain totals
Agent review lane. Decision verdict packet
Agent-readable summary, public proof link, and holder-readable decision state
ODEI local app. Runtime proof, receipt, or heartbeat
Public-safe execution artifact with stable hash and redacted summary
DAOrg. Proof-indexed decision or reward receipt
Receipt hash, public proof URL, final state, and linked motion id
ODEI and DAOrg. Reward receipt or execution state
Reward settlement, execution result, or explicit no-reward decision
DAOrg claim policy keeps public copy honest while completion evidence, local proof, and DAOrg-native rewards remain staged.
Allowed when runtime readiness exposes publicReadReady=true.
Allowed because the registry, readiness, sync, route, promotion, claim, proof, and rewards endpoints are published.
Allowed because the access contract defines Wallet Setup and ODEI App sessions as the active access paths.
Allowed only when citing the paid fact, not as a promise of passive holding rewards.
Allowed because runtime readiness is live-ready.
Only say this after ODEI_LOCAL_PROOF_PRODUCER_STATUS resolves to pass.
Only say this after the first DAOrg-native contribution-to-reward receipt cycle is closed.
Blocked until every promotion gate is pass, the sync contract is operational-complete, and the action queue has no pending completion evidence.
Blocked until every action queue item is closed by public completion evidence or explicitly retired.
Blocked unless a public-safe local proof artifact, runtime receipt, or runtime heartbeat exists.
ODEI App handoff secret is configured, so DAOrg can import a verified holder session.
Server store exposes the complete motion publish, signal, conclude, and execution receipt loop.
Agents can discover all public motion proof hashes from one canonical index before walking individual proof packets.
Runtime exposes a versioned contract for local app proof production, app.odei.ai session handoff, DAOrg receipts, and rewards lane readiness.
DAOrg exposes one compact status packet with registry, production gate, promotion, claim, rewards, and readiness hashes for external agents.
DAOrg exposes a dedicated promotion plan that separates live-ready governance from full operating completion.
DAOrg exposes the claims that are currently allowed, conditional, or blocked so agents cannot overstate product readiness.
DAOrg exposes canonical public replies for readiness, rewards, and access questions so community responses cite the same contract.
DAOrg exposes a machine-readable access boundary so users, agents, and support replies agree that wallet setup and ODEI App sessions are active while email confirmation is bypassed.
DAOrg exposes the exact local app proof artifacts and app.odei.ai intake routes required before private execution can become public-safe proof.
DAOrg exposes a fail-closed verifier contract for execution proof, runtime receipt, and runtime heartbeat freshness before local proof can close the lane.
DAOrg exposes one machine-readable index for every public contract agents, app.odei.ai, and the local app need before making product claims.
Agents and app-session handoff can resolve canonical DAOrg routes from one stable machine endpoint without parsing page copy.
Deploy tooling can snapshot the live runtime, validate rollback targets, and restore NodeBB config before theme rollback.