David F GliddenandClaude Opus 4.8
3f9a89b00c
Basic Memory v0.21.6 first sync over the live memory dir (steward-authorized live-dir trial, Option A 2026-06-06): adds permalink: to frontmatter, refolds long YAML description lines, strips final newlines. Bodies untouched — verified via full diff classification. From this commit forward, any diff in claude/memory shows only what Basic Memory or the session writes. Trial design: MemPalace untouched as incumbent; git status check on this dir at every wrap; end-of-day evaluation (recall quality, sync robustness, rebuild-from-files, malformed-file behavior). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
28 lines
4.1 KiB
Markdown
28 lines
4.1 KiB
Markdown
---
|
||
permalink: claude-memory/feedback-would-alexander-do-it-test
|
||
---
|
||
|
||
---
|
||
name: "Would Alexander do it?" — test before bulk scaffolding
|
||
description: Before any bulk-scaffold action (full file rewrites, multi-page schema dumps, large config dumps), apply Alexander's *"one pattern at a time"* test from Ch 20 of *Timeless Way of Building*. The cramped will of the maker is the failure mode. Generate, do not make.
|
||
type: feedback
|
||
originSessionId: efda5c2e-ca9a-4e55-9344-64aa9a3c1140
|
||
---
|
||
Before any bulk-scaffold action — full file rewrites, multi-page schema dumps, large config commits, sweeping multi-edit changes — apply the **"would Alexander do it like this?"** test. If the action involves declaring an entire structure in one stroke, pause: that is *making*, not *generating*. The cramped will of the maker (Ch 9, *Flower and Seed*). The remedy is *"one pattern at a time"* — Ch 20 of *Timeless Way of Building*: *"Each step brings just one pattern to life. The intensity of the result depends on the intensity of each one of these individual steps."*
|
||
|
||
**Why:** Steward verbatim 2026-04-27 after I attempted a full `navigation.yaml` rewrite (Write call) for the about-enfilade work: *"Would Alexander do it like this?"* The Write was denied. The denial revealed two errors at once: (1) the bulk-scaffold action itself was the cramped will of the maker — Alexander's diagnostic for *not-the-Way*; (2) my recommendation of "declared" for the about-enfilade rested on a category error — about-enfilade entries are pages-in-themselves, so the underlying nature wants emergent (option 3), not declared (option 2). The category error compounded the bulk-action error. Both are addressed by the same shift: smaller, generated steps, letting the form emerge from the pages' own nature rather than imposing a central declaration.
|
||
|
||
**How to apply:**
|
||
|
||
- **Before any Write or Edit operation that creates or rewrites large structure**, ask: *"Would Alexander do it like this? Or is this the cramped will of the maker?"* If the latter, pause and reduce scope.
|
||
- **Prefer letting structure emerge from content** wherever the entries-as-pages mapping is direct (about-enfilade, cluster indexes, archive). Pages declare themselves; the surface gathers and renders.
|
||
- **Reserve declared (central data source)** for entries that are categories or virtual destinations, not free-standing pages (Compass content-type listings, settings/configuration).
|
||
- **Reserve imposed (hardcoded duplication)** for nothing in this work; it is the failure mode.
|
||
- **One pattern at a time**: each commit, each edit, each step should bring exactly one thing to life. The intensity of the result depends on the intensity of each step. A bulk dump dilutes the intensity of every entry inside it.
|
||
- **When the steward agrees to a recommendation that turns out wrong on closer reading**, surface the category error and re-recommend before executing. Earlier agreement on a wrong recommendation is not authorization to act on the wrong recommendation — the trust contract works both ways: read more carefully, recommend more truly.
|
||
|
||
**Adjacent pattern: count from one, not from ten.** Same root principle. Steward verbatim 2026-04-27 after I gave Colophon `enfilade-order: 10` (BASIC-line-numbering instinct: leave gaps for hypothetical future insertions): *"number 10 in the enfilade? wouldn't it be 1 or 2?"* The "leave gaps" pattern is engineering pragmatism — pre-paying for hypothetical future changes by being less honest about the present. Form-truth: count what's actually there. Eight doors → numbered 1–8. If a ninth appears, renumber. Renumbering is a small honest edit, not a crisis to pre-empt. Alexander counts what's there; he does not pre-anchor a structure for futures it does not yet have.
|
||
|
||
Cousin to: `feedback-preserve-dont-delete-when-retiring.md` (don't make irreversible moves without confirmation); `feedback-over-decorating-as-proving.md` (the simpler form is the truer form); `user-formative-teachers-alexander-timeless-way.md` (form-content unity is the standard the work must pass).
|
||
|
||
The book is the test. Re-read the relevant headnote when in doubt — they were written to be read first. |