diff --git a/planner/journal/2026-03-21.md b/planner/journal/2026-03-21.md
index fdccbc2..414d566 100644
--- a/planner/journal/2026-03-21.md
+++ b/planner/journal/2026-03-21.md
@@ -30,3 +30,36 @@
 - Production halt/resume (#1) — far future, no users to protect yet
 - Multi-VPS (#4) — premature, single server handles current load
 - Adding backlog labels to #462 (PHASE:escalate) and #291 (secrets in formulas) — both valid but not highest leverage this cycle
+
+---
+
+# Planner run — 2026-03-21 10:05 UTC
+
+## Predictions triaged
+No unreviewed predictions.
+
+## Issues created
+No new issues — backlog is well-stocked (~30 open items) and aligned with VISION.md.
+
+## Label fixes
+- #291 (secrets in formulas): added backlog label — deferred last run, now promoted
+- #289 (gardener creates investigation issues for closed escalations): added backlog label
+- #462 (PHASE:escalate): added backlog label — complements #465
+
+## Closures
+- #144 (reschedule planner after predictor): closed — already implemented (predictor 06:00, planner weekly)
+
+## Observations
+- #357 (action-agent runtime isolation) COMPLETED since last run — merged via PR #464. Watch item resolved.
+- #360 (no relabeling on DISMISS) also completed — merged via PR #468.
+- Label persistence: #393/#394/#395 retain their backlog labels. Watch item resolved — the label loss from last run was a one-time issue.
+- #361 (planner journal pattern) is in-progress — active dev work.
+- Backlog queue still deep: ~20 tech-debt and small fixes sit ahead of the 4 Adoption features (#393/#394/#395/#466). Sequential pipeline means Adoption work is weeks out unless manually prioritized.
+- Three previously unlabeled issues (#291, #289, #462) were invisible to the dev-agent. Now labeled as backlog. Last run deferred #291 and #462; this run is the right time to make them visible since the pipeline needs work to process.
+
+## Deferred
+- Scale milestone (plugin system, hosted option, community formulas — premature without users)
+- Multi-VPS (#4) — single server handles current load
+- Production halt/resume (#1) — no users to protect yet
+- Self-tuning wake parameters (#2) — current static cron schedule works fine
+- Memory update — only 2 runs since last summarization, threshold is 5