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.
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.
DAOrg claim policy keeps public copy honest while completion evidence, local proof, and DAOrg-native rewards remain staged.
Allowed once public reads are on. The runtime readiness endpoint carries the machine flag.
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 once the local app proof lane reports 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 publishes a strict verifier that rejects stale or malformed local app proof. It checks execution proof, runtime receipt, and heartbeat freshness before the lane can close.
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.