Files
dotfiles/claude/memory/feedback-close-low-hanging-fruit-not-defer.md
T

15 lines
1.4 KiB
Markdown

---
name: feedback-close-low-hanging-fruit-not-defer
description: Steward prefers closing low-hanging fruit / loose ends now over deferring them; deferred non-blockers fall through the cracks.
metadata:
node_type: memory
type: feedback
originSessionId: 255d028e-361d-404c-b89c-cac6c028234b
---
Steward directive (2026-07-14): **close loose ends and low-hanging fruit NOW rather than defer, even when non-blocking** — deferred items "fall through the cracks when they're constantly deferred." Determination is why he pushes.
**Why:** deferral is a form of drift / context-rot; an open loose end that's cheaply closeable should be closed, not accumulated behind "not blocking." The accumulation is the hazard, not any single item.
**How to apply:** when surveying outstanding work, don't stop at "here's what's non-blocking, rest." Sort every item by **closeable-now-as-executor (no ruling)** vs **draftable-ready-for-gate** vs **genuine-decision (needs steward/jurist)** — then *do* the executor-closeable ones and *advance* the gate-needing ones to drafted-ready, rather than listing them as deferred. Critically, distinguish **decision-fatigue** (he wants fewer DECISIONS on him — [[feedback-shorter-concentrated-sessions]]) from **loose-end-closure** (he wants MORE of those done, *by me*, precisely *because* they don't need his decision). The two are not in tension: closing executor-side fruit reduces his load AND satisfies the determination.