illustrated_modular_agentic_matribo.txt

Figure type and communication goal:
Create a publication-ready 16:9 scientific architecture infographic titled “Agentic-MatriBO”. The MLEvolve figure is a style reference only. Borrow its friendly hand-drawn academic visual language—pastel region fills, dark rounded outlines, doodle line icons, handwritten headings, generous white space, and clear narrative composition—but copy none of its text, robots, search trees, benchmarks, logos, or topology. All factual content and topology must come exclusively from the instructions below.

Layout and visual language:
Use a pure white canvas and three asymmetric rounded regions with 3–4 px dark-ink 042433 outlines, no gradients, no glossy effects, no 3D, and no heavy banner bars. Reserve a small centered title area for the single short title “Agentic-MatriBO”; it must not become a full-width colored banner. Use a legible Comic Neue or Kalam-like handwritten typeface. Main headings are bold and colored to match their region; body text is dark ink. Keep text sparse, large, horizontal, and perfectly spelled. Preserve 12–15% white space and keep every border and arrowhead inside the canvas.

Left region, Agentic Reasoning:
Use a large pale-blue EDF4FA panel occupying about 35% of the width, with heading color 163E64. Arrange a compact clockwise reasoning loop using floating illustrated stations rather than dense nested rectangles. Place “Task & State” with a small paper-and-flask doodle and subtitle “intent • hypotheses • gaps”. Place “Evidence Scope” with a graph-and-magnifier doodle and subtitle “memory • graph • manifest”. Make “Typed Policy” the visual focal point and show four colored decision pills: “KEEP”, “CHANGE”, “PROBE”, and “STOP”. Place “Reflection” with a circular-arrow notebook doodle and subtitle “state update • rule candidate”. Draw Task & State to Evidence Scope to Typed Policy as solid dark arrows. Place “Optional Council” in a small lavender FBF0F9 advisory cloud above Typed Policy, with a purple 77206E dashed arrow into Typed Policy. Draw a purple dashed curved PROBE arrow from Typed Policy back to Evidence Scope and label it exactly “No Oracle Budget”. Do not connect Typed Policy directly to Reflection.

Right top region, Deterministic BO Harness:
Use a large pale-peach FBE3D6 panel with heading color C04E15. Place a clean left-to-right executed pipeline: “BO Compilation” to “Candidate Decision” to “Oracle Observation”. Use simple dark-ink doodle icons for a gear or recipe, a four-dot candidate grid, and a table or database. Under BO Compilation show only “capability gates • BORecipe • OOS diagnostics”. Make Candidate Decision wider and visualize three small stages rather than a text wall: “4 sources” to “validate” to “rank fusion / selected ID”. Under Oracle Observation show “ID lookup • commit result • budget +1”. Render executed arrows as solid dark ink.

Between the blue reasoning region and peach harness, draw a vertical dashed dark-blue boundary labeled exactly “Typed Proposal Boundary”. A solid routed arrow labeled “KEEP / CHANGE” must originate at Typed Policy, cross this boundary, and enter BO Compilation. Place a lavender “Dimension Review” note above Candidate Decision and connect it to Candidate Decision with a purple dashed advisory arrow. Draw one solid routed arrow from Oracle Observation back across the boundary into Reflection. Reflection then sends a distinct purple dashed feedback arrow back to Task & State; the arrow must visibly originate at Reflection. There is no Typed Policy to Reflection arrow. Draw one coral FA7E6E dashed bypass from the STOP pill in Typed Policy directly to a small coral callout “Report” with subtitle “Direct Exception”. It must bypass BO Compilation, Candidate Decision, and Oracle Observation. Never draw STOP from Oracle Observation.

Right bottom region, Memory, Provenance & Recovery:
Use a pale-green F3FBF0 rounded panel with heading color 3B7D22. At the top edge beneath Oracle Observation, label a strong downward milestone “Durable Boundary” and “experiment_results”. From that milestone, use one shared horizontal persistence bus that branches independently to four equal illustrated cards arranged side by side. The cards are “TaskMemory” with “Campaign Local”, “EventGraph” with “Round Chain”, “Playbook” with “Rule Ledger”, and “Checkpoints” with “Recovery State”. These are parallel stores; do not draw arrows from one card to the next. Use paper-stack, node-graph, ledger, and save-or-database doodles.

Closed topology:
Draw exactly these connections and no others. Task & State to Evidence Scope to Typed Policy is solid executed flow. Optional Council to Typed Policy is purple dashed advisory flow. Typed Policy KEEP or CHANGE to BO Compilation is solid executed flow across Typed Proposal Boundary. Typed Policy PROBE to Evidence Scope is purple dashed and labeled “No Oracle Budget”. Typed Policy STOP to Report is coral dashed direct exception flow. BO Compilation to Candidate Decision to Oracle Observation is solid executed flow. Dimension Review to Candidate Decision is purple dashed advisory flow. Oracle Observation to Reflection is solid executed flow. Reflection to Task & State is purple dashed feedback flow. Oracle Observation to Durable Boundary and experiment_results to the shared persistence bus is solid committed flow, with four independent branches to TaskMemory, EventGraph, Playbook, and Checkpoints. Do not draw Typed Policy to Reflection, Oracle Observation to Report, a serial TaskMemory to EventGraph to Playbook to Checkpoints chain, or a PROBE loop inside the deterministic harness. Every arrow must visibly touch its named source and target; do not merge unrelated arrows, branch implicitly, cross labels, or terminate in empty space.

Visible text closed list:
Render only these exact strings: “Agentic-MatriBO”, “Agentic Reasoning”, “Task & State”, “intent • hypotheses • gaps”, “Evidence Scope”, “memory • graph • manifest”, “Typed Policy”, “KEEP”, “CHANGE”, “PROBE”, “STOP”, “Optional Council”, “No Oracle Budget”, “Reflection”, “state update • rule candidate”, “Typed Proposal Boundary”, “KEEP / CHANGE”, “Deterministic BO Harness”, “BO Compilation”, “capability gates • BORecipe • OOS diagnostics”, “Candidate Decision”, “4 sources”, “validate”, “rank fusion / selected ID”, “Dimension Review”, “Oracle Observation”, “ID lookup • commit result • budget +1”, “Report”, “Direct Exception”, “Memory, Provenance & Recovery”, “Durable Boundary”, “experiment_results”, “TaskMemory”, “Campaign Local”, “EventGraph”, “Round Chain”, “Playbook”, “Rule Ledger”, “Checkpoints”, “Recovery State”, “executed by harness”, and “advisory / feedback”. Render every other word, number, formula, axis tick, production note, or placeholder as absent.

Legend and defect constraints:
Add a tiny unobtrusive legend showing that a solid arrow means “executed by harness” and a dashed purple arrow means “advisory / feedback”. Use only the specified blue, peach, green, lavender, coral, neutral grey D9D9D9, and dark ink. Avoid generic corporate flowchart aesthetics, excessive text, emojis, photorealism, drop shadows, gradients, transparent or dark backgrounds, decorative circuitry, copied branding, independent-agent claims, wet-lab robots, performance claims, blockchain imagery, extra modules, extra edges, clipping, overlap, garbled text, and duplicated labels. Aspect ratio 16:9.