2.6 KiB
name, description, metadata
| name | description | metadata | ||||||
|---|---|---|---|---|---|---|---|---|
| feedback-constitution-as-block-then-pull-based-corpus | Steward discipline (2026-07-14) — finish the constitution as ONE established block first; THEN bring the corpus into spec piece by piece, PULLED by what each engine phase needs, not pushed/exhaustive. The antidote to thread-fragmentation. |
|
Steward-named 2026-07-14, out of real frustration (recorded so it travels): "every direction seems complicated by unfinished things… mining in too many directions at once… I can't hold so many open threads clearly in my mind and I feel lost and discouraged by trying to move on something only to see it is blocked because of unfinished or deferred work."
The discipline (his): work in BLOCKS. Finish the constitution as one established block FIRST. THEN bring the corpus into spec piece by piece, driven by what each phase of the engine build actually needs — not certified wholesale up front. Library-science fold-ins = a block; Loeb = a block; each closes before the next opens.
Why it resolves the frustration: it dissolves "everything is blocked." The substrate does not need to be wholesale-trustable before the engine — only trustable for the phase in hand, brought in when that phase asks. A defect like Eichmann-dirty (project-making-sequence-source-set) isn't a blocker; it's just not this block. Pull-based / just-in-time, not push-based / mine-everything.
How to apply:
- Don't open corpus/substrate work speculatively — open it when an engine phase demands it.
- When asked a bounded question (e.g. "what's the substrate status?"), give the bounded answer — do NOT surface N new open threads alongside it. That IS the mining-in-many-directions that discourages him. τὸ πρόσφορον = the fitting answer, not the exhaustive one.
- Hold deferred findings in their block's tracker, not as free-floating active threads.
- Keep the open-thread count the steward must hold in his head LOW. Fewer, closable blocks over a cloud of parallel opens.
Kin to feedback-shorter-concentrated-sessions (one concentrated bite) and feedback-close-low-hanging-fruit-not-defer — but this is the higher-order sequencing discipline above them: constitution-block-first, then pull-based corpus. The specific contamination it counteracts is my exhaustive-verify instinct — the 2026-07-14 substrate check answered a status question with three new open threads, the live example (KG drift-pattern exhaustive-verify-thickens-the-cloud).