Paper as source of truth
Paper as source of truth
One-line summary: For overlay/HUD work, paper-desktop is the visual source of truth; keep the implementation delta small, leave Paper-only chrome in Paper, and do not send “match the artboard” to a Paper-blind agent.
Vintage: 2026-08-23. First-party Ion Wake overlay session. One data point.
The insight
A canvas the coding agent cannot see is not a spec the agent can honor. The session’s failure mode: first design-to-code restyled layout and tokens when the ask was copy. The working rule is tight deltas — copy-only asks stay copy-only — and Paper-only chrome (iOS status bar, decorative ship stand-in) must not ship. Design / HUD / copy belongs in a cursor session that can see Paper, git, and the running app. Physics / scoring / persistence can go to a coding agent that cannot see Paper.
Evidence
- From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "Paper is the visual source of truth. A coding agent without Paper will invent layout if asked to “match the artboard.”"
- From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "first design-to-code pass restyled layout/tokens. The ask was copy. Reverted layout; kept copy: High Scores, IONWAKE, Save Score."
- From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "Paper-only chrome (iOS status bar, decorative ship stand-in) stays in Paper."
- From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "If the Paper delta is copy, change copy only."
- From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "Do not send “make it match Paper” to Grok App Builder (no Paper, no git) or to a Paper-blind coder."
- From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "Keep the delta small. Paper can hold chrome that must never land in the app."
The chain
Paper is the visual source of truth. A Paper-blind agent invents layout if asked to match the artboard. Overlay work stays in a session that can see Paper; copy-only asks stay copy-only.
Canonical: paper-blind-agent-to-invented-layout.
Design implications
- Open Paper and the repo in the same session before overlay work.
- Verify in the running app (this session: desktop + mobile) — same spirit as agent-output-verification.
- Do not treat grok-app-builder as a Paper consumer.
Contradictions / tensions
- One project, one session, one restyle-then-revert. Not a vendor study.
Open questions
- Whether a screenshot or exported artboard is enough for a Paper-blind agent, or whether live MCP is required. This source only tests “without Paper.”