MainQuest: The Unwritten World

MainQuest: The Unwritten World

MainQuest is a local-first personal operating system where confirmed real-life progress changes a personal world. It combines cognitive offload—one clear directive, upkeep, wealth/runway, and a calm Day Close—with transparent progression and an authored story that moves only when life actually moves.

What the demo proves

One directive, with reasons

The Living World opens before the task list. Its first viewport shows compact progression, wealth/runway, hard risk, one current directive, and a factual world vista. The user can ask why the directive was selected or replace it in Quests. Selection and reward rules are deterministic and local; AI does not secretly decide which task matters.

A durable World Answer

Completing a real action is a two-step confirmation. Only after the local record saves does MainQuest render an inline World Answer with the confirmation time, rule version, XP/GOLD, impact tier, named world change, rationale, and idempotency reference. Main-quest outcome confirmation makes the completion reward explicit and leaves the quest visible in Recently completed, while the progression rail keeps level, rank, total XP, banked GOLD, and VIT/REP/INT discoverable.

Story that follows meaningful progress

An authored Awakening scene can unlock only from durable, deterministic main-quest progress important enough to materially change the world record. At most one scene unlocks per unique local day. If the current scene remains unresolved—or the user does not return—it simply waits without penalty. Progress accumulated behind that waiting scene is not banked to skip forward, and resolving a scene alone can never unlock the next. Five authored scenes are bundled locally, including one persistent choice, without changing rewards or world facts.

A complete daily loop

The fictional public demo includes two scheduled habits. Day Close records the liquid snapshot, completed habits, and one line for tomorrow, then returns a persisted recap with the saved details, XP/GOLD earned in that close, and current/best streaks. Upkeep payment, main-quest outcome, and boss clear each require their own explicit confirmation rather than treating a checklist tap as proof.

What was built for Build Week

Living World-first React PWA with one directive, transparent risks, factual continuity, privacy masking, and a compact progression rail Deterministic Priority and Progression engines with idempotent XP, domain XP, GOLD, rank, streak, and trophy records Explicit, persistence-backed confirmation for actions, main-quest outcomes, boss clears, and upkeep payments Durable World Answer materializations linked to proof, impact assessment, reward, and world-change records Five locally authored Awakening scenes gated by new meaningful main-quest progress on unique local days IndexedDB persistence for quest, upkeep, wealth, receipt, check-in, progression, and story state Recently completed quest history and a structured persisted Day Close recap A resettable fictional public demo seed that never loads personal data Provider-independent core rules and adapter boundaries

Privacy and current scope

The current demo does not simulate a live community, opaque AI task scoring, or a cloud account. Raw wealth stays local and is masked in Privacy Mode. Supabase, LINE, Claude runtime copy, shared-world voting, commerce, and metaworld features remain deliberately closed behind later gates.

Built with Codex

Codex was the implementation and verification partner: translating product direction into provider-independent TypeScript rules, React interaction surfaces, regression tests, and submission documentation. The qualifying /feedback Session ID is supplied privately in the required submission field. GPT-5.6 Codex was used for architecture, implementation, testing, review, and submission preparation; delegated implementation and audit work used lower-cost GPT-5.6 agents while decisive product judgments stayed with the primary reasoning model. The app itself does not send user data to a runtime model.

Verification

On July 22, 2026, the workspace passed all 200 automated tests—127 core, 4 adapter, and 69 PWA tests—plus full TypeScript checking and the production build. The repository README contains a reproducible fictional-demo walkthrough.

Built With

• codex
• gpt-5.6
• indexeddb
• pnpm
• react
• typescript
• vite
• vitest