t3-p3-05authored3–5h
Shared decisions log across agents
requires: t3-p3-04
Spec
Solve the practical problem of the reviewer needing to know decisions the planner made - for example a migration decisions log all three roles read and write. This is your shared-state mechanism.
Why this matters
Multi-agent systems fail at the seams. Without shared state the reviewer rejects work for violating a convention the planner invented and never told it about - and the loop never converges.
Verify
No result yet. Run `learn verify t3-p3-05` locally, or push to trigger CI.
repo
unrun
judge
unrun
Rubric
# t3-p3-05 — Shared decisions log across agents
**Task:** Solve the practical problem of the reviewer needing to know decisions the planner made - for example a migration decisions log all three roles read and write. This is your shared-state mechanism.
**Strong:** Directly answers every one of the review questions below in the affirmative, with specific evidence from the actual work, not a restatement of the task.
- Do entries show all three roles reading and writing, or only one?
**Passing but weak:** The deliverable exists and technically satisfies the spec, but is generic, restates the task instructions instead of engaging with them, or only partially addresses the review questions below.
**Fails:** The deliverable is missing, or engages with none of the review questions below - e.g. it describes what was built without explaining the reasoning the task actually asks for.