method-figure

name	method-figure
description	Generate a publication-grade method / architecture / pipeline / workflow figure (a paper or README 'Figure 1') as an AUDITABLE object, not a one-shot prompt. A deterministic JSON blueprint LOCKS the content; an image model (gpt-image-2, baked by the agent via mcp__codex__codex — Codex GPT-5.5 xhigh, sandbox workspace-write) bakes the aesthetic from a labeled-condition render + the project's real identity refs; a cross-model panel (Gemini + Codex) blind-transcribes the result and a script hard-diffs it against the blueprint; the loop regenerates until Gemini AND Codex approve and the diff is empty — then the calling agent (Claude) gives the structural sign-off. NOT for statistical plots (use a plotting tool) or photo scenes.
argument-hint	["method_figure_brief.json | blueprint.json"]
allowed-tools	Bash(*), Read, Write, Edit, Grep, Glob, mcp__codex__codex, mcp__codex__codex-reply, mcp__gemini-cli__ask-gemini, mcp__gemini__chat

method-figure

Turn "draw our method figure" from a one-shot gamble into the same audited spiral the framework uses for comics: a blueprint is the source of truth, the image model bakes the look, a cross-model panel + a deterministic diff keep it honest, and the loop converges to a publication-grade figure that is reproducible (re-run the blueprint) and auditable (a trace of every round).

Two things are simultaneously true: (a) gpt-image-2 CAN render a clean Figure-1 with legible labels when conditioned on a labeled blueprint — do not assume it garbles text; (b) on a free prompt it DRIFTS (renames phases, invents nodes, garbles a token, leaves pasted-looking floating labels). The blueprint + blind-transcribe-then-hard-diff loop turns (a) into a reliable result and catches (b) every round.

  system description ─▶ ① BLUEPRINT (JSON content-lock)  ── validate_blueprint.py
                              ▼
                        ② CONDITION (white-bg labeled SVG → PNG) + identity sheet (real chibi, optional)  ── render_condition.py --png
                              ▼
                        ③ BAKE  — agent: mcp__codex__codex(prompt+abs ref paths+out_path, workspace-write, gpt-5.5, config{xhigh}) → gpt-image-2 native PNG  ── pickup_image.py --out-existing (sig+size+dims, mtime-bound, HARD-VETO struct/zlib/PIL/SVG, fail-closed)
                              ▼
                        ④ PANEL — Gemini ‖ Codex BLIND-transcribe → content_diff.py (observed ⊖ blueprint) → Claude structural sign-off
                              ▼
                        ⑤ agent reads the diff + the panel blockers → re-bake re-asserting the locked labels
                              ▼
                   converged? ─ no ─▶ ③   (bounded: max_rounds → escalate to human)
                              │ yes
                              ▼
                        ⑥ APPROVE → figure.png + blueprint.json + trace.jsonl

Constants

• GENERATOR = Codex gpt-5.5, config: {model_reasoning_effort: xhigh, include_image_gen_tool: true} → the native image_generation tool (gpt-image-2). The gpt-5.5 pin is a single hardcoded COMPAT DEFAULT in the bake sidecar payload (run_spiral.py mirrors run_comic.py's canonical bake plan; a config-driven model override is PLANNED, not yet implemented). It pins the BAKE only — the panel's Codex reviewer is un-pinned (see PANEL below). CRITICAL: image_gen is produced ONLY via mcp__codex__codex (the agent tool), NOT codex exec. codex exec / over-specified / forbid-list prompts make Codex hand-draw a code fallback (struct+zlib PNG or SVG/matplotlib) — visually indistinguishable for trivial shapes, useless for a real method-figure. The working invocation is mcp__codex__codex with a dead-simple prompt + sandbox: "workspace-write" (it must WRITE the out_path) + model: "gpt-5.5" + config: {model_reasoning_effort: "xhigh", include_image_gen_tool: true} (the schema has NO top-level effort param; config{xhigh} shorthand below ALWAYS expands to both these keys — without include_image_gen_tool codex won't fire its native image tool, it falls back to descriptive text / an SVG renderer) + cwd: <project>. Reference images are passed by absolute file path inside the prompt (the schema has NO -i); the output path is a deterministic abs path in the prompt. Pick it up with pickup_image.py --out-existing (verifies the EXPLICIT out_path: PNG sig + size + dims, mtime >= request.created_at) which HARD-VETOES struct/zlib/PIL/<svg>/matplotlib markers in the agent transcript (fail-closed; there is no 'native sig wins' override). Honesty caveat: as of Jun 2026 native headless persistence is unreliable, so this fail-closed verifier — not any sandbox setting — is the first guard against a non-native bake. But the HARD-VETO is a BEST-EFFORT denylist against the known codex-exec hand-draw fallback (struct/zlib/PIL/ SVG/matplotlib markers), NOT a complete security boundary — a novel fallback that emits a sig-valid PNG without those markers can slip past it. The load-bearing faithfulness gate is the cross-model blind-transcribe panel + the deterministic content_diff (the pixels are what reviewers transcribe), with this denylist as a cheap upstream filter.
• PANEL (automated blind-transcribe) = the orchestrator SHELLS the gemini + codex CLIs as subprocesses (both must be on PATH; MCP is ONLY the bake seam): Gemini = gemini --model auto-gemini-3; Codex = codex exec -i <png> with NO model pin (it follows the local codex config — currently gpt-5.6-sol) at effort xhigh — so the reviewer model ≠ the bake's pinned gpt-5.5. Plus the deterministic content_diff. Claude (this agent) is the post-pass STRUCTURAL sign-off, not a blind transcriber — the loop converges on Gemini-approve + Codex-approve + empty-diff, then Claude signs off.
• CROSS-MODEL ACQUITTAL — Codex is the generation family, so a Codex approve can only diagnose/veto, never be the sole acquitter. ACCEPT requires Gemini approve + Claude structural approve + the hard-diff empty.
• MAX_ROUNDS = 4, then escalate to human with best-so-far + open blockers.
• LABEL_POLICY = baked only in v0 — the image model renders ALL text; nothing is hand-pasted. (hybrid/overlay — lock structure + vector-overlay the labels for paper zero-tolerance text — are on the v1 roadmap; do NOT use a vector overlay as an ad-hoc patch on a finished bake, it reads as pasted.)
• OUTPUT_DIR = figures/method_figure/<figure_id>/ (figure.png, blueprint.json, condition.svg, trace.jsonl).
• NATIVE-IMAGE FAIL-CLOSED — accept a bake ONLY if a real native PNG exists at the explicit out_path, sha/size/dims check out and mtime >= request.created_at, and the agent transcript shows no struct/zlib/ PIL/<svg>/matplotlib fallback (pickup_image.py --out-existing, HARD-VETO — a clean sig never overrides a fallback marker). This veto is a BEST-EFFORT denylist against the known codex-exec hand-draw fallback, NOT a complete security boundary (a novel marker-free fallback could evade it). The load-bearing faithfulness gate remains the cross-model blind-transcribe panel + the deterministic content_diff; the denylist is a cheap upstream filter that matters because native headless persistence is currently unreliable.
• SERIALIZE BAKES — never run two image generations at once. The default --bake-mode=agent writes each native PNG to its explicit per-round out_path (no shared dir), so concurrent agent bakes still risk a request/status sidecar race — keep one runner per figure. (The global ~/.codex/generated_images dir + newest-after-marker pickup that could cross-pollinate concurrent bakes is a hazard of the LEGACY --bake-mode=exec path ONLY, which is retired for real bakes.)

Input contract / ARIS hand-off (who decides WHAT, who only renders)

This skill is pure render + verify. Ownership:

• Upstream owns the semantics — what to depict, the labels, the graph, the grouping, the headline claim/number, the identity refs. method-figure does NOT choose content and must not invent a node, claim, number, or method structure (if one is missing it ESCALATES, it does not make it up).
• Step-0 is now DETERMINISTIC — run_spiral.py calls scripts/compile_brief.py to map a method_figure_brief.json → a schema-valid blueprint.json + traceability.json, fail-closed (an object that can't trace to a brief field, or a missing claim/number/trait, is refused — not invented). It is no longer a manual LLM hop. Full field map + the guards: references/blueprint_authoring.md.
• method-figure owns validation → condition render → image bake → cross-model panel → diff → retry, and has VETO power: it returns FAILED / Logic Drift rather than ship a figure whose pixels contradict the blueprint.

The default single input = a method_figure_brief.json (schemas/method_figure_brief.schema.json) — ONE ARIS-format file; the blueprint, the coordinates, and the identity wiring are all derived. The identity sheet is resolved from the brief's identity_refs[].path (no separate --identity to manage). Where the input comes from, in authority order:

1. a method_figure_brief.json — the canonical ARIS hand-off (what paper-plan emits); auto-detected (by its schema_version: "method-figure/brief/v1") + compiled. ·
2. an existing hand-tuned blueprint.json — power-user override (--from-blueprint, used as-is). ·
3. an experiment-plan / paper-write method section / free-text — no brief yet: the agent first DRAFTS a method_figure_brief.json from it (claims/numbers verbatim; anything missing → Refuse-and-Escalate), then compiles.

ARIS integration: the canonical producer is paper-plan — after its claims_matrix it emits the method_figure_brief (components, flows, phases, the headline claim/number, identity refs, forbidden_tokens). You feed that one file to run_spiral.py; Step-0 compiles it and the traceability is enforced by the compiler (an un-traceable object is a Refuse-and-Escalate, not a render). The identity sheet is created once upstream and locked; method-figure only reads it.

Fast path — one command (single input: a brief)

Feed ONE method_figure_brief.json; the whole loop is one command (all commands below run from the repo root; the panel shells the gemini + codex CLIs, so both must be on PATH):

python3 skills/method-figure/scripts/run_spiral.py your_method_figure_brief.json --out-dir figures/method_figure/<id>
#  auto-detects a brief → Step-0 compile_brief.py → blueprint.json + traceability.json (deterministic, fail-closed)
#  → validates → renders condition(+png) → [bake (agent: mcp__codex__codex --bake-mode=agent, workspace-write,
#  gpt-5.5 config{xhigh} → gpt-image-2 native PNG via the .bakereq.json sidecar) → pickup_image.py --out-existing
#  verify (fail-closed, HARD-VETO over the status file's mcp_output) → Gemini + Codex blind-transcribe → content_diff → blockers] × rounds
#  → on PANEL-CLEAN writes figure.png + blueprint.json + traceability.json + trace.jsonl.
#  input auto-detect: a brief is detected ONLY by schema_version "method-figure/brief/v1" vs a blueprint (version);
#  a bare components+flows JSON with NO schema_version is REFUSED — it REQUIRES --from-brief (fail-closed, no guessing)
#  --identity is OPTIONAL (resolved from the brief's identity_refs[0].path);  --dry-run prints the round-1 bake
#  prompt;  --p0-only runs the zero-credit gate (validate+compile+render+prompt-lint) then stops;  --max-rounds N.
#  There is NO --effort knob (the flag is removed) — bake + review effort are hardcoded xhigh by design.
#  --gemini-cmd overrides how the google-family reviewer is shelled (default: the legacy `gemini` CLI). Legacy
#  CLI dead (IneligibleTierError, 2026-07)? pass --gemini-cmd "python3 cli/gemini_agy_shim.py" — the shipped
#  Antigravity shim pins a Gemini model (the second-reviewer slot must stay google-family for quorum honesty).

Power-user / override: already have a hand-tuned blueprint? run_spiral.py blueprint.json --identity sheet.png --out-dir … --from-blueprint runs the legacy path unchanged. A worked example brief lives at examples/method_figure/method_figure_brief.json. Long-running (each bake ~3-8 min) — run it in the background; watch trace.jsonl. It converges to PANEL-CLEAN — BOTH reviewers returned parseable JSON, Gemini approve AND Codex approve, the deterministic content_diff empty, core scores (incl. character_identity when an identity sheet is given) ≥ threshold, and no anomalies/blockers — then STOPS and hands to the calling agent (Claude) for the final structural sign-off (the generator family never self-acquits). The manual steps below are exactly what run_spiral.py automates (run them to debug one stage).

Who runs --bake-mode=agent (the agent-wrapper SOP) — REQUIRED for the default mode to function

The bake is a synchronous sidecar handshake and the skill agent is its fulfiller (without it, every bake polls to --bake-timeout and escalates with failure_kind="other" — fail-closed, not a hang, never a false throttle):

1. Launch the orchestrator in the BACKGROUND (from the repo root): python3 skills/method-figure/scripts/run_spiral.py your_brief.json --out-dir figures/method_figure/<id> --bake-mode agent.
2. Loop until it prints PANEL-CLEAN / escalates / exits:
   • watch <out-dir>/ for a new *.bakereq.json (the orchestrator writes round<N>.png.bakereq.json);
   • read it; call mcp__codex__codex with exactly its {prompt: <prompt_text>, model:"gpt-5.5", config:{include_image_gen_tool:true, model_reasoning_effort:"xhigh"}, sandbox:"workspace-write", cwd:<cwd>} (codex writes the native PNG to the sidecar's out_path). The config MUST carry both include_image_gen_tool:true AND model_reasoning_effort:"xhigh": without include_image_gen_tool Codex will not fire its native gpt-image-2 tool (it falls back to a struct/zlib/SVG hand-draw), and xhigh is the required reasoning tier;
   • then read request_id from the *.bakereq.json and write <out>.bakestatus.json carrying the status, a bounded raw mcp_output, AND that request_id VERBATIM — mcp_output so the HARD-VETO can scan it (the core feeds this file to pickup --transcript; an ok status with no raw output makes the veto INERT), and request_id because pickup_image.py --out-existing --request-id fail-closes the bake if the status request_id is missing or mismatched (write it on BOTH ok and fail): {"status":"ok","mcp_output":"<raw>","request_id":"<verbatim from bakereq>"}, or {"status":"fail","failure_kind":"throttle","mcp_output":"<raw>","request_id":"<verbatim from bakereq>"} on a 429 / MODEL_CAPACITY_EXHAUSTED / overloaded error (else {"status":"fail","failure_kind":"other","mcp_output":"<raw>","mcp_error":"<raw>","request_id":"<verbatim from bakereq>"}).
3. The core proceeds to verify ONLY on status:"ok", via pickup_image.py --out-existing (sig + dims + size > 500000 + mtime >= created_at, HARD-VETO over mcp_output, and --request-id fail-close if the status request_id is absent/mismatched). --bake-mode=exec is the legacy/CI non-image path and RAISES if it reaches a real bake.

Workflow (what run_spiral.py automates — or run by hand)

① Author the BLUEPRINT (content lock)

Write blueprint.json per schemas/blueprint.schema.json. The *_exact fields (label_exact, desc_exact, group/edge/callout *_exact, rail.label_exact) are the LOCKED text re-asserted verbatim every round; expected_tokens[] are what the panel must blind-transcribe and the diff checks. Then:

python3 skills/method-figure/scripts/validate_blueprint.py blueprint.json   # jsonschema (if installed) + unique ids · edges resolve · box/group/callout bounds · no dup labels

② Render the CONDITION

python3 skills/method-figure/scripts/render_condition.py blueprint.json --out condition.svg --png condition.png   # white-bg labeled layout → rasterized

Prepare identity_sheet.png from the project's REAL characters if the figure has any (never invent robots). The condition PNG + the identity sheet are the two image references.

③ BAKE (round N) — agent seam

Call mcp__codex__codex (sandbox workspace-write — it must WRITE the out_path; model: gpt-5.5, config: {model_reasoning_effort: xhigh, include_image_gen_tool: true}, cwd: <project>) with the prompt from references/prompt_templates.md §A — it RE-ASSERTS every *_exact label + the round-N blockers + the carried positive_invariants, with condition.png + identity_sheet.png referenced by absolute path inside the prompt (the schema has no -i) and the exact out_path to save the native PNG. Write the bake status to round<N>.png.bakestatus.json carrying the raw mcp_output (so the HARD-VETO can scan it) AND the request_id copied VERBATIM from round<N>.png.bakereq.json (pickup --request-id fail-closes if it's missing/mismatched), then verify the explicit out_path (no marker/glob):

python3 skills/method-figure/scripts/pickup_image.py --out-existing --out figures/method_figure/<id>/round<N>.png --min-bytes 500000 --aspect <W/H> --created-at <epoch> --request-id <uuid4 hex from round<N>.png.bakereq.json> --transcript figures/method_figure/<id>/round<N>.png.bakestatus.json

④ PANEL — blind transcribe, then hard diff

Ask each of the TWO blind transcribers — Gemini + Codex (references/prompt_templates.md §B) — for the STRICT JSON of references/reviewer_protocol.md: they transcribe observed_tokens / observed_edges / identity_audit and an anomalies list (the Negative-Space Audit), NOT shown the expected labels. Claude is NOT a transcriber — it never produces a blind round<N>.cc.json; its structural sign-off comes post-pass in ⑤/⑥. Save as round<N>.{gemini,codex}.json, then:

python3 skills/method-figure/scripts/content_diff.py blueprint.json round<N>.gemini.json round<N>.codex.json
# → missing_tokens / unaccounted_tokens / anomalies ; empty == content-accurate

⑤ Decide (stop rule) — the agent consolidates

Read the diff report + the two transcribers' blockers. The executing agent itself merges blockers only (ignore nice_to_have — chasing polish makes it oscillate), carries the union of positive_invariants forward, and writes the round-N+1 bake prompt.

• ACCEPT iff: diff has no missing_tokens/anomalies · Gemini approve · Codex approve (required, but never the sole acquitter) · Claude structural approve · every core score ≥ acceptance.min_core_score (default 4).
• RETRY iff: blockers are prompt/condition-fixable and round < MAX_ROUNDS → back to ③.
• ESCALATE to human iff: same root failure 2 rounds · irreconcilable reviewers · MAX_ROUNDS hit · or a non-prompt-fixable failure (throttle / identity drift / no native image).

⑥ Finalize + trace

On ACCEPT: copy the approved PNG to figures/method_figure/<id>/figure.png, keep blueprint.json, and append to trace.jsonl per round: {round, blueprint_sha, condition_sha, generated_sha, reviewers:{...verdicts}, hard_diff:{missing_tokens,anomalies}, fixes:[...], decision} + a final {final_approve, image, blueprint, accepted_round, verdicts}. Failures are kept — the fixes that were needed are the memory (the figure-wiki).

Hard do / don't (earned lessons)

• DO lock content in the blueprint and RE-ASSERT every *_exact label in every regeneration — image models drift content every round; the blueprint is the anchor.
• DO bake via the agent (mcp__codex__codex, workspace-write) and fail-closed if no real native PNG at the explicit out_path (pickup_image.py --out-existing, HARD-VETO struct/zlib/PIL/<svg>/matplotlib in the status file's mcp_output).
• DO use the project's real identity refs; anchor each character to the identity sheet. For a character figure, every reviewer ENUMERATES each chibi's visible hands — a wrong count / 3rd / floating / merged limb is a single-reviewer veto (the literal-diff is blind to anatomy).
• DO run the zero-credit P0 gate before the first metered bake: run_spiral.py brief.json --out-dir … --p0-only (validate brief → compile blueprint → render condition → confirm the bake prompt carries ALL locked labels, the identity path resolves, the background is white). A blocker caught here costs zero image credits.
• DON'T regenerate when the score-signature is IDENTICAL across rounds — that means the judge is broken (gone design-blind), not the figure. Stop and audit the rubric (feedback_gate_identical_scores_judge_broken).
• DON'T hand-paste text onto a finished bake (reads as pasted/fake) — that is what burned us; the whole figure, text included, is generated. (Engineered vector overlay is a future policy, not a patch.)
• DON'T use a dark theme for a paper/README figure — light/pastel on white.
• DON'T let one model (especially the generator's family) self-acquit; the panel is cross-model.

Scope

Figure type	Fit
method overview / pipeline / architecture / workflow	excellent
conceptual / taxonomy / comparison diagrams	good
statistical plots	no → plotting tool
exact-topology deterministic vector figures	prefer a pure-vector renderer
photo-realistic scenes / long narrative comics	no (comics use the framework's spiral engine)

A converged worked example ships in examples/method_figure/: the ARIS-Movie-Director Figure 1 — blueprint + figure.png + condition.svg + the real 4-round trace.jsonl (Gemini approve + Codex approve + empty diff, then Claude's structural sign-off). PROMPTS.md there publishes the exact, unedited prompt sequence that baked it (all 4 gpt-image-2 bakes + the cross-model critiques, paths redacted) — the canonical exhibit of how detailed a condition must be; copy its shape.

Implemented / roadmap

• ✅ scripts/compile_brief.py — Step-0 automation: deterministic method_figure_brief.json → blueprint.json + traceability.json (the ADJ-4 field map, auto_layout, fail-closed validate_traceability). This is what makes the skill single-input — run_spiral.py brief.json auto-detects
  • compiles, so you never hand-write a blueprint or hand-place coordinates.
• ✅ scripts/run_spiral.py — the one-command orchestrator (sniff input → [Step-0 if brief] → bake→pickup→ panel→diff→consolidate→decide loop to PANEL-CLEAN). --p0-only runs the zero-credit gate; --from-brief/--from-blueprint disambiguate. Folds blocker-consolidation + invariant-carry inline.
• 🔭 scripts/overlay_labels.py + label_policy: hybrid/overlay — vector-overlay the structured labels on the bake for paper zero-tolerance text. Default stays baked (fully generated).
• 🔭 a Claude-vision reviewer inside the orchestrator (currently the automated panel is Gemini + Codex + the deterministic diff; Claude — the calling agent — gives the structural sign-off on the converged figure).

Protocols (governance contracts this skill honors)

• reviewer-independence — reviewers blind-transcribe from the image only; the generator (Codex image_gen) ≠ the visual judges.
• acceptance-gate — the loop drives, can't acquit: ACCEPT needs the deterministic content-diff clean + Gemini approve + Codex no-veto + Claude structural sign-off.
• artifact-integrity — the baker doesn't judge its own figure's numbers; the blueprint is ground truth, verified by the blind diff.
• reviewer-routing — bake sidecar pins Codex gpt-5.5 + xhigh (a hardcoded compat default; config-driven override is planned); the CLI reviewers pin NO model (they follow the local codex config — currently gpt-5.6-sol) at xhigh; Gemini auto-gemini-3; never downgrade effort.
• review-tracing — every round's reviewer verdicts are logged to trace.jsonl.