Continuity Notes (New Chat Handoff)
We are building PrimeCore (100% digital, 100% automated; Founder approvals only) with an iPad-first PWA “War Room” that later reaches Windows parity.
CURRENT STATE (DO NOT RESET OR RE-ARCHITECT):
- Live Cloudflare Pages project exists and is working.
- Repo being deployed: Storm7070/primecore-war-room (Cloudflare Pages Git deploy).
- The app is a static PWA (no build step), deployed from repo root.
- Core UI: Approvals, Voice Intent, WHY (Policy Router explain panel), KPIs, Truth+Evidence.
- Sprint 31 is active: Policy Router + Model Gateway + Receipts wired into the UI.
IMPORTANT FILE STRUCTURE (paths matter):
Repo root:
- /index.html (main UI)
- /app.js (ES module; imports policy/gateway/receipts)
- /styles.css
- /manifest.webmanifest
- /sw.js
- /docs/index.html
Policy modules:
- /policy/policies.json
- /policy/policy-packs.json
- /policy/router.js
- /policy/policy/policy-router.js
- /policy/gateway/model-gateway.js
- /policy/receipts/receipts-store.js
CRITICAL RULES:
- Always route actions through Policy Router before any “execution”.
- Record every decision/outcome as a receipt.
- No silent writes. High-risk actions require Founder approval.
- Keep iPad-first UX as the control plane; don’t move logic into the UI.
WHAT WE NEED NEXT:
- Continue Sprint sequence beyond 31: expand Policy Router rules + pack versioning, add safe connectors in Shadow mode, canary writes, rollback classes, and observability tiles.
- Keep Cloudflare Pages deployment stable and ensure service worker caching doesn’t mask updates.
- Prepare PC migration without interrupting iPad work: clone repo, reproduce env, continue commits, keep Cloudflare auto-deploy.
Tip: If the site ever loads blank, hard refresh and confirm Cloudflare Pages is deploying from repo root and that /index.html exists.