diff --git a/ops/SCOREBOARD.md b/ops/SCOREBOARD.md
index 6b06c05d2..9b0066bbb 100644
--- a/ops/SCOREBOARD.md
+++ b/ops/SCOREBOARD.md
@@ -6,7 +6,7 @@ Every row starts RED and moves only on evidence. AMBER blocks nothing here
 | Gate | State | Evidence |
 |---|---|---|
 | 1 — a relayflow can run | **GREEN** | Closed on `main` at `9e1d9eb` (PR #8, merged by Khaliq) and extended on WP-12 by the live authored-surface seam: the built `sdk/dist/cli.js` submits `hello-deterministic.flow.yaml` to a real `relayflowd`, distinguishes worker-unavailable and `needs_human` parked states from typed snapshots, bounds worker waits by their leases, journals `step_failed`, and resumes after `kill -9` with one successful completion per step. WP-12 branch verification: kernel **74 passed / 0 failed**, SDK **150 passed / 9 files**, including **7/7** built-binary and **7/7** live-kernel cases; the same 150-test SDK suite passed from recoverably moved `dist` and `node_modules`. Residual, documented in DESIGN.md §1.9: a worker dying after the provider call but before confirming performs an effect twice — closing it needs gate 4's mount-as-writer. |
-| 2 — proactive agent | **AMBER** | **in progress** — PR #14 landed wake.rs, event.rs, the subscription registry with (flow, subscription, key) dedupe and claim repair, and the SDK event.submit verb. Missing: the RFC-0001 Appendix A wake-time context contract, and a test proving a duplicate event does not double-execute. Was — first of the 2-4 sequence gate 6 waits on; harness shims wait on it |
+| 2 — proactive agent | **AMBER** | **in progress** — PR #14 landed wake.rs, event.rs, the subscription registry with (flow, subscription, key) dedupe and claim repair, and the SDK event.submit verb. Dedupe is DONE and mutation-bound: sequential duplicates (#14), concurrent racing deliveries under the production topology of one Engine per request (#171), and claims that survive the process that made them (#171, #182), plus resume adopting only a journal it can actually use (#177, #186). Missing: the RFC-0001 Appendix A wake-time context contract -- nothing specifies what `wake_context` guarantees, or that a resumed run observes the SAME context rather than a recomputed one. And the row has been understating the gate: RFC-0001 s3's bar is `hn-monitor` running as a relayflow IN PRODUCTION on its real events with zero bespoke persistence, not a passing test suite (#167). Was — first of the 2-4 sequence gate 6 waits on; harness shims wait on it |
 | 3 — Software Garden | **AMBER** | started — PR #20 merged the backlog picker: a flow that reads ops/BACKLOG.md and emits a work package, with selection determinism asserted across 25 repeated runs (sdk/src/backlog-picker.ts). That is the seed of flows proposing their own work; the Garden itself is far from done. |
 | 4 — chief / harness | RED | not started |
 | 5 — memory | RED | scoped by harness directive 3 (relayfile + relayhistory per customer) |