From 0ac083dc461796b1f6d4d40883ec8c4e38f1a993 Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Sun, 26 Apr 2026 11:07:16 +0100 Subject: [PATCH] Add push reminder for major passes --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 2170e182..b3bd2461 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -93,6 +93,7 @@ When the user says to prepare for imminent compaction: - Keep maps and prose together; do not replace useful maps with prose-only explanations. - Before adding natural-language explanations or metaphors to an algorithmic map, first read the relevant source paths and anchor the explanation to concrete code references. Metaphor is compression after source grounding, not a substitute for it. - Commit completed work before it rots in the worktree unless the task is deliberately mid-surgery or the user asked to leave changes uncommitted. +- After committing a major completed pass, push upstream unless the user asked not to push yet or there is a concrete reason to keep the commit local for a moment. - Before handoff, compaction, or phase boundaries, sync `state/map.yaml`, add distilled evidence when the lesson changes future belief, refresh `notes/fresh-workspace-handoff.md`, and make the next action explicit. - Do not write handoff notes that trap the next session in indefinite tiny hardening work. Bounded slices are a landing discipline, not a roadmap; when a phase is complete enough, name the next larger organ to build.