(Coming Soon)

Build schedule

Five days. Each day confirms something real before the next begins. The ceremony comes first because everything else depends on it working. The soul bundle, the trace, the guild: each only becomes meaningful once two people have actually held their cards together and felt something pass between them.

DAY 1 - 18 MAR End-to-end ceremony skeleton

◆ Milestone: A working hold → depth achieved → record shown loop in the UI (even if stubbed).

◆ Tech: Ensure `npm run dev` + routing is stable.

◆ Tech: Verify the depth meter + thresholds UI (Level 1 / Level 2 / Level 3).

◆ Tech: Store a mock bond record locally and render it clearly.

◆ Non-tech: Write a 45–60s demo narrative for what happens during a hold.

◆ Non-tech: Collect 3 screenshots (hero, depth meter, bond record).

✓ Confirm: Done: A judge can see the ceremony flow in-browser from start to finish.

DAY 2 - 19 MAR Make the trace feel real

◆ Milestone: The UI shows an example relational trace that persists and is readable.

◆ Tech: Define a clear bond record JSON shape consistent with the spec.

◆ Tech: Add a simple history view (list of bonds / traces).

◆ Non-tech: Write 3 example traces (quiet, precise, human).

◆ Non-tech: Tighten copy on `/concept`, `/ceremony`, `/protocol` for consistency.

✓ Confirm: Done: You can create 2+ bonds and see them accumulate as history.

DAY 3 - 20 MAR Spec alignment + public artifacts

◆ Milestone: The site, spec links, and terminology are consistent and submission-ready.

◆ Tech: Ensure `/synthesis` links work and all routes prerender/build clean.

◆ Tech: Remove remaining inconsistent naming in UI labels (Levels, Depth Sync, trace).

◆ Non-tech: Finalize `static/synthesis.md` as the submission companion.

◆ Non-tech: Draft submission text sections: problem, solution, what’s novel, what’s real.

✓ Confirm: Done: `npm run build` is clean and the site reads like a finished story.

DAY 4 - 21 MAR Demo hardening

◆ Milestone: Record a clean demo video and freeze content.

◆ Tech: Fix remaining papercuts (layout issues, broken links, obvious UI bugs).

◆ Tech: Add happy-path guardrails so the demo can’t easily break.

◆ Non-tech: Record and edit demo video.

◆ Non-tech: Create a 1-page judging walkthrough checklist (what to click, what to notice).

✓ Confirm: Done: Demo video exported; walkthrough works three times in a row.

DAY 5 - 22 MAR Submission day

◆ Milestone: Submit early; keep buffer for last-minute issues.

◆ Tech: Final build + deploy (or ensure static output is ready).

◆ Tech: Smoke test all pages and links.

◆ Non-tech: Complete the submission form.

◆ Non-tech: Final proofreading + screenshot selection.

✓ Confirm: Done: Submitted with working links and video; no last-minute scrambling.