RIGOR Agent-First Narrative Image Prompt

Status: Visual concept only — not product requirements, implementation status, qualification evidence, or a substitute for the normative PRD.

This is the maintained production prompt for the RIGOR product-vision figure. It separates implemented software and simulated behavior from target scheduling and future physical qualification so the image can remain aspirational without being read as release evidence.

Assets

• Original: rigor-agent-first-narrative.png
• Previous result: rigor-agent-first-narrative-v3.png
• Current result: rigor-agent-first-narrative-v4.png
• Recommended format: landscape PNG, 16:9, 1672 × 941 px or larger

The prompt uses image-editing mode with the v3 asset as the edit target. Earlier assets remain available as visual history.

Production Prompt

Use case: scientific-educational
Asset type: Nature/Cell-quality scientific graphical abstract for RIGOR
documentation and presentations

Input image role: edit target (`rigor-agent-first-narrative-v3.png`). Preserve the overall visual identity, wide 16:9
composition, ivory background, navy/teal/coral/gold palette, title, subtitle,
three-act narrative, module chain, laboratory illustration, Evidence/PRISM
loop, provenance rail, and clean editorial typography.

Primary request: Refine the existing RIGOR narrative so Rehearsal, the final
Operation gate, current software scope, human exception paths, target
availability-aware scheduling, future physical qualification, and end-to-end
provenance are visually distinct.

REQUIRED EDITS

1. REHEARSAL
Keep the cyan/teal Rehearsal stage after Composer and before execution. Preserve
its digital-twin icon, checkmark, and correction arrow to Composer.

Exact label:
“Rehearsal”
“exact intent · completed branch”

Add a small tag:
“predicted”

It must mean isolated prediction before a side effect. A failed rehearsal loops
back to planning; a passed rehearsal proceeds with immutable lineage.

2. FINAL OPERATION GATE
Add a compact warm-orange gate at the LabBridge-to-laboratory interface, after
PACE and LabFlow scheduling and immediately before any side effect.

Exact label:
“FINAL OPERATION GATE”
“exact input · current catalog”

This gate is distinct from Rehearsal. It rechecks the exact request and current
capability catalog before creating the durable Operation.

3. HUMAN EXCEPTIONS AND SCHEDULING TARGET
Replace the exception card with:

“Needs you”
“Attention · Human Task”

Keep this dashed coral branch outside the normal route.

Keep the professional technician, calendar/clock, and subtle
connection to LabFlow. Add a small outlined tag directly above this card.

Exact tag:
“FUTURE STUDY”

Replace the card label with:
“Availability-aware scheduling”
“declared windows · handoffs”

The card expresses a target scheduling capability. Keep the coral “Needs you”
branch for implemented exception handling and required human work; distinguish
it from future availability-aware scheduling. Do not show inferred workload,
learned schedules, identity tracking, or worker scoring.

4. CURRENT AND FUTURE ENDPOINTS
Keep the central laboratory illustration. Enclose its physical instruments in a
dashed warm-gold boundary labelled “TARGET PHYSICAL LAB”. Keep simulated
laboratory imagery translucent teal.

Add one compact two-line scope key without covering any module or arrow.

Exact text:
“CURRENT SOFTWARE SCOPE  agent-first software · simulation · algorithmic analysis · governed human work”
“FUTURE QUALIFICATION  physical instruments · physical effects”

Use solid teal for the current base and a short dashed gold sample for future
qualification. Do not imply that the depicted instruments are integrated.

5. PROVENANCE
Preserve the continuous indigo-to-gold trace line spanning Goal + Constraints,
ASCEND, Composer, Rehearsal, PACE/LabFlow, laboratory operations, Evidence,
PRISM, the immutable vault, and the next decision. Keep anchor dots at major
stages.

Exact label near the lower edge:
“Provenance — goal · plan · rehearsal · operation · evidence · analysis · decision”

This trace must communicate traceability, versions, lineage, and auditability,
not a generic data arrow.

NARRATIVE HIERARCHY

- Act 1: people define intent and constraints.
- Act 2: agents plan, rehearse, schedule humans and machines, and autonomously
  advance safe execution.
- Act 3: evidence is analyzed and committed, with provenance feeding the next
  decision.
- Keep the deterministic safety rail visible:
  “Policy · Locks · Timeout · Cancel · Safe-stop · Audit”.

COMPOSITION GUIDANCE

- Slightly reorganize and scale existing elements to create breathing room.
- Preserve the researcher, Goal + Constraints card, existing module names
  ASCEND, Composer, PACE, LabFlow, and LabBridge, the mobile robot, laboratory
  equipment, Evidence, PRISM, vault, Agent-first Loop, and Needs you.
- Make Rehearsal visually distinct from production execution using a
  translucent digital-twin motif.
- Availability-aware scheduling should look operational and respectful, not like
  worker surveillance, and its target tag must remain visible.
- Current software/simulated behavior and future physical qualification must
  use the solid-versus-dashed scope key consistently.
- Attention and Human Task share one `Needs you` surface but retain distinct
  semantics: one records a decision; the other records work in an Operation.
- Provenance should be legible but visually subordinate to the main teal
  autonomous loop.
- Use English text that is correctly spelled, natural, horizontal, and easy to
  read.
- Produce a publication-ready, precise, restrained, elegant scientific
  editorial illustration.

AVOID

- Decorative quotation marks, fake citations, and watermarks.
- Raw GPIO, MQTT, device SDK, or other implementation details.
- Excessive tiny text, duplicated labels, visual clutter, or crossing arrows.
- Depicting rehearsal as evidence that a physical experiment succeeded.
- Depicting target scheduling as implemented, planned human work as mandatory
  approval, or people as a surveillance target.
- Presenting the illustrated instruments as integrated or physically qualified.
- Depicting provenance as a single central database rather than linked lineage.

Review Checklist

• Rehearsal is on the main route and has a visible correction path to Composer.
• The final Operation gate rechecks exact input and the current catalog after Rehearsal and before the physical-effect boundary.
• Planned human work is distinct from the exceptional Needs you channel.
• Declared availability and handoffs are visible target scheduling inputs.
• The scope key separates the current software/simulated base from future physical qualification.
• Provenance spans goal, plan, rehearsal, operation, evidence, analysis, and decision.
• The safety rail remains deterministic and visually distinct from model reasoning.
• Evidence and PRISM analysis still drive the next iteration.

Interpretation Boundary

The figure tells a product-vision story. Rehearsal checks an exact intent in an isolated environment; the final Operation gate rechecks that lineage against the requested input and current catalog. Neither gate qualifies a physical result. Availability-aware scheduling remains a study target and does not imply employee monitoring. Provenance represents linked domain records and stable references, not one shared database. The illustrated physical laboratory remains a future endpoint that requires separate device and effect qualification.

For normative behavior, consult the Agent-First System Design PRD.