Comps are pages not vignettes, and the prompt travels with the asset

Two findings from the first human-validated probe. The comps rendered
as scene vignettes because the generation prompts led with the world's
atmosphere; the model painted the fish market instead of the fish
market's website. The comp guidance now demands the page's literal
skeleton in the prompt, nav and its items, headline block, sections in
order, footer, with a self-check: a render that could hang as a poster
is not a comp. And generation context is part of the asset: the thread
that wrote a prompt knows what the image contains and why, so build-
critical imagery prefers the build thread, and subagent-produced assets
must carry their prompts, via the tool's new sidecar or the manifest,
read by the builder before composing.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Paul Bakaus
2026-07-28 13:27:03 -07:00
co-authored by Claude Fable 5
parent 14c27e43af
commit 39532a65a2
3 changed files with 10 additions and 2 deletions
+6 -1
View File
@@ -229,4 +229,9 @@ if (!b64) {
process.exit(1);
}
fs.writeFileSync(out, Buffer.from(b64, 'base64'));
console.log(`IMAGE: ${out} (${size}, ${quality}, gpt-image-2, billed to your OpenAI key)`);
// The prompt travels with the asset: any thread that later composes this image
// can recover the intent behind it without the generating thread's context.
try {
fs.writeFileSync(`${out}.json`, JSON.stringify({ prompt, createdAt: new Date().toISOString(), tool: 'generate-image.mjs', model: 'gpt-image-2' }, null, 2));
} catch { /* sidecar is best-effort */ }
console.log(`IMAGE: ${out} (${size}, ${quality}, gpt-image-2, billed to your OpenAI key); prompt sidecar at ${out}.json`);