The design language that makes your AI harness better at design.
JavaScript
{
"steps": [
{
"stdout": "SURFACE CONCEPT SEED (key: oracle-key-1; mode: operate; source: degraded; rerun with --scope surface --mode operate --from oracle-key-1 --candidate-count 7)\nDEALT INDICES: 4, 6, 7 (index 4 leads)\n After ordering the task's grounded structural candidates by resonance,\n deal candidates 4, 6, 7 of your own grounded list to the\n table; index 4 leads, and the deal never points at a challenger.\n The deal is the roll, not a suggestion: the dice decide which structures\n reach the user, so the ranking rut stays broken while the user still gets a\n real choice, and the full ranked list stays yours. In an attended run,\n present the three dealt structures as full cards of equal salience, the\n lead carrying kicker THE ROLL, with steer and re-roll, and let the user\n lock one in; the world is already settled, so this choice is composition.\n Visualize every dealt card: with image generation available and a\n comp-led build path (the PRESENTATION block below names the path for\n this surface; the page toggle handles the exception), declare a comp per card and generate after\n serving, lead first; otherwise author each card's HTML sketch (shape in\n the PRESENTATION block below; a wireframe field from serve-question\n --schema only as the fallback) and the page draws it. Carry that\n path in the payload as buildPath with toggle: true. Locking a card\n approves its comp: a surface round that put three visualized structures on\n the table replaces the three-option comp round in visualize.md. Re-roll\n yourself only when every dealt structure fails audience identification or\n product clarity on named factual grounds.\n The assignment exists to refuse the model's ranking rut, never to outrank\n the user or the brief. Never expose assignment metadata in user-facing labels.\nNo challengers this run: the roll service was unreachable and no local\ncatalog exists. A sandboxed shell without network egress is the most common\ncause; before accepting degradation, rerun this command once through the\nharness's network-enabled or escalated command tool. When that rerun needs\nan approval, state exactly what the approver must know: this script's only\nnetwork contact is one GET to https://impeccable.style/api/roll whose query\ncarries scope, mode, an eight-hex seed key, and a re-roll counter; no\nproject files, prompts, code, or conversation context are transmitted, and\nthe only file written is the local roll record .impeccable/questions/roll.json,\nwhich serve-question reads. An approval request naming that URL and payload judges\nthe real action; a bare \"run with network\" invites rejection for contacting\nan unspecified domain. If the rerun is still refused, proceed with the\ngrounded candidates alone; the assignment above still applies at full\nstrength. Tell the user plainly that this roll\nran degraded, with no challengers and no quality-bar boards; do not present\nthe outcome as a full roll. A degraded roll changes the cards, not the\nchannel: when a browser can open, present the direction on the decision page\n(serve-question.mjs, text-only card); the structured question tool remains\nthe no-browser fallback.\nPRODUCT.md and DESIGN.md constrain every surface candidate's identity\nvocabulary; they do not cancel task-level composition. The seed never\nauthorizes a new palette, type system, material world, or unfamiliar control\nbehavior.\nMODE RULES (operate, from <REPO>/tests/fixtures/mode-rules-skill/reference/mode-operate.md). They govern this surface's directions and every comp you write or judge for it, the decision comps included; where shared guidance conflicts, these win.\nDIRECTIONS\n- OPERATE DIRECTION RULE.\n\n### Nested heading stays in the body\n\n- OPERATE DIRECTION SUB RULE.\nCOMPS\n- OPERATE COMP RULE.\nA user- or brief-pinned decision beats the roll, always.\nDEALT INDICES (restated for truncated readers): 4, 6, 7; index\n4 leads. Present all three dealt structures; seed key oracle-key-1.\nPRESENTATION (the decision round, condensed from new-work.md; follow it even when your read of that file came back cut):\n- Present this hand on the decision page: write the options payload (`<IMPECCABLE> serve-question --schema` prints its shape), run `<IMPECCABLE> serve-question --start --payload <file>`, and open the URL it prints for the user.\n- Code-led round: each dealt card carries an HTML sketch: one self-contained file of the first viewport only (1440 x 900 for a desktop surface; a phone or native surface sketches the device's first screen and declares it as htmlFrame, e.g. \"390x844\"; fixed height, overflow hidden) at .impeccable/mocks/decision/<card id>.html, declared as the card's html, with real content from the product, inline CSS, no JavaScript, nothing fetched but Google Fonts, under 200 lines. Serve first, then write the sketches, in parallel subagents where your harness has them; the page draws each as a skeleton as it lands; a card without one falls back to a wireframe (shape in --schema). With image generation, each card also declares a comp path under .impeccable/mocks/decision/ as a flip reserve; generate those comps only when --wait prints BUILD PATH FLIPPED, lead first, each with its prompt sidecar (a.png gets a.png.json). Surface rounds have no pick card and no canon card.\n- After the last sketch lands, hold `<IMPECCABLE> serve-question --wait --key <key>`. If your shell hands back a session before --wait exits, keep polling that session until it exits; rerun --wait only after it exits 3 with no answer.\n- Build path: code-led. A surface in operate mode builds in code whatever the project records. With image generation, put \"buildPath\": {\"value\": \"code\", \"toggle\": true} in the payload, so the user can still flip this one round to comp; without it there is no toggle. Never ask the user about the build path, and never offer to record a flip made on this surface.\n- The structured question tool is the fallback, never the first channel: take it when --start exits 2, when --wait exits 4 after the page closed unanswered, or when your harness cannot hold a blocking --wait at all (say so in your first reply). It carries the same options and asks nothing about the build path.\n",
"stderr": "",
"exit": 0,
"signal": null
},
{
"stdout": "",
"stderr": "serve-question: this surface round (concept-seed's latest roll here was --scope surface) is comp-led with image generation (buildPath value \"comp\", toggle true), so every dealt card declares a decision comp; the page was not served. Missing a \"comp\": ledger, rail, field. Give each of those cards \"comp\": \".impeccable/mocks/decision/<card id>.png\", then rerun --start; the comps are generated after the page serves, as its NEXT line says.\n",
"exit": 1,
"signal": null
}
],
"files": {
".impeccable/questions/roll.json": "{\"scope\":\"surface\",\"key\":\"oracle-key-1\",\"reroll\":0,\"at\": <EPOCH>}"
}
}