diff --git a/.mulch/expertise/seedpass.jsonl b/.mulch/expertise/seedpass.jsonl
index ad72760a..7d9c521c 100644
--- a/.mulch/expertise/seedpass.jsonl
+++ b/.mulch/expertise/seedpass.jsonl
@@ -23,3 +23,4 @@
 {"type":"convention","content":"Builders must git add + git commit immediately after completing edits, BEFORE running test suites. This prevents losing work to rate limits or session interruptions. Test results can be verified after the commit exists. If tests fail, fix and create a new commit.","classification":"foundational","recorded_at":"2026-03-10T01:40:39.450Z","id":"mx-156d3a"}
 {"type":"convention","content":"Coordinators must only merge branches where the builder confirmed full test suite pass (pytest + CI gates) — not just committed code. Untested merges risk introducing broken imports and regressions to beta.","classification":"foundational","recorded_at":"2026-03-10T19:51:50.511Z","id":"mx-dc57e3"}
 {"type":"convention","content":"Coordinators must run the full test suite on beta after each merge before merging additional branches, to catch cross-branch regressions early. Learned from the pubkey.py missing Binding import incident where untested code was merged and broke beta.","classification":"foundational","recorded_at":"2026-03-10T19:51:52.605Z","id":"mx-e37592"}
+{"type":"convention","content":"Doc update convention: when updating dev_control_center.md and tui_v3_plan.md to reflect shipped work, (1) update Last updated date, (2) update health gate test counts from pytest --co -q, (3) mark completed parity items as shipped with date, (4) add progress log section to tui_v3 plan with validation evidence, (5) advance Next Slice Definition.","classification":"tactical","recorded_at":"2026-03-11T01:16:26.999Z","outcomes":[{"status":"success","agent":"builder-doc-update"}],"id":"mx-7ef9fe"}