Mulberry, completed
Refine the INSTRUCTION.md, launch, author and certify the task setting, and agree a Mulberry taxonomy that each tick reads until the plan decodes. Then two iterations: a measured task in the frontier band, a task rejected after a setter repair, and a measured task no rollout solved. Finally, share the finished campaign.
Press Play to walk one campaign instance step by step, from the INSTRUCTION.md in the composer to its stored evidence and share link. Each step sets the nodes it touches alight: the browser controller, the client transport, the owner router and its handler, the Postgres tables behind it, the external worker running each trial, and the components that render the answer. Calls that start other calls are nested in the Call tree.
Illustrative: cmp_b1e5c0de0000000000000001, trial IDs, timings, and content are simulated. Every request and response shape is replayed through the real campaign-api.ts client and decoders by campaign-blueprint.test.ts. Space plays or pauses; the arrow keys step when the canvas is not focused.
- Spinethe request path and the worker lifecycle
- Fanone node spinning off the next calls
- Treecomponents rendered from the view model
- Convergetrials reporting into one outcome
- Dataa read or write against a table