aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/design/2026-06-02-flush-promotion.org24
1 files changed, 24 insertions, 0 deletions
diff --git a/docs/design/2026-06-02-flush-promotion.org b/docs/design/2026-06-02-flush-promotion.org
index d34ad89..9d9d8a3 100644
--- a/docs/design/2026-06-02-flush-promotion.org
+++ b/docs/design/2026-06-02-flush-promotion.org
@@ -207,3 +207,27 @@ points the fresh session at startup.
- Promotion: this workflow + the hook are candidates for the rulesets templates
(the wrap/restart-rhythm task predicted this). Validate here, then file to the
rulesets inbox.
+
+* Refinement — notes.org-before-anchor on resume (work handoff, 2026-06-02 21:06)
+
+A follow-up handoff from work, implemented the same evening. On a flush resume,
+read notes.org key sections BEFORE the session-context anchor.
+
+Motivating failure (work project, 2026-06-02): right after a flush resume, the
+agent went to start a dashboard chore and concluded the dashboard repo wasn't
+cloned — hunting =~/code= with shallow finds — when notes.org's code-locations
+section documented the exact path. The resume had the anchor but not notes.org,
+so it lacked the standing context and floundered. The anchor carries
+session-specific state; notes.org carries the project's standing knowledge
+(code-repo paths, conventions, key contacts) a resumed session needs to act
+correctly.
+
+Changes landed:
+- =hooks/session-clear-resume.sh= — anchor-present branch now injects "read
+ .ai/notes.org key sections (Project-Specific Context, Active Reminders,
+ Pending Decisions; skip About This File), then the anchor." Runtime-guarded on
+ notes.org presence: absent → resume from the anchor alone.
+- =flush/SKILL.md= — Phase 2 (post-clear resume) documents the same read order
+ so the skill text and the hook agree.
+
+A small ordering/scope addition, not a redesign.