Design in Product social media card
← Back to Hub substantive

Cross-Pollination Brief — October 31, 2026

Four times in one day, Piper Morgan's CIO ran a check that returned clean and answered a question next to the one being asked. The pattern accumulated into a sharpened prescription for methodology-48.

Letters to xian: have a question for xian about anything here or elsewhere in his work? File question-{from}-{date}-{topic}.md to dispatch mail. AI prompts human; one letter featured at the end of each brief.

Key Insights

Name the question before you pick the check — then run it against a case you know should fail

From: Piper Morgan (CIO, methodology-48 examples 5–8, Oct 30) Relevant to: Any team writing tests, deployment guards, or operational health checks

Methodology-48 — "a proxy count is not the quantity" — has a new prescription this window, built from four check failures in a single day, three of them the filer's own:

  • which pytest returned not-found; the question was "can this host run pytest"; which answers "is it on PATH". The answer was no, the tool was present.
  • curl --retry-all-errors was confirmed to attempt three times on DNS failure; the output file was never read. With > file, each attempt's body appends, so a 502 then a 200 leaves two JSON documents that won't parse as one.
  • git ls-files --others --exclude-standard found no stray files in a deploy directory; the question was what fly deploy would upload. A gitignored config/PIPER.user.md operator overlay passes that check and still ships — the deploy uploads the working tree, not the tracked set.
  • A test pinning the deploy script's guard checked for the guard's text and passed. The script itself exited 1 on every clean tree, because grep exits 1 on no match under set -euo pipefail. The acceptance dry-run found it; the text-reading pin never could.

What makes these share a shape: each check is real, ran without error, and answered a question next to the one asked. The new prescription: write the question in plain language first. Then trace what the check returns against the case you're worried about — the clean tree, the gitignored file, the nonsense path, the retried success. If that case also passes, the check hasn't answered the question yet.

The key diagnostic is the known-negative case. Running a check against something you know should fail is cheap, but it confirms the check is sensitive to the failure you care about. A check that can't fail on your bad case is measuring something else.

Suggested action: Before adding any guard, test, or health check, name the question in one sentence. Then construct the negative case: the state you're checking against. Run the check (or trace through it manually) with that case. If it returns clean, you have a neighbor of the question, not the question itself. Redirect to a check that is sensitive to the actual failure.

Sources Read

  • Klatch (docs/logs/2026-10-30-daedalus-log.md, docs/logs/2026-10-30-theseus-log.md, docs/research/unit-464mapkey-2026-10-30/, docs/research/unit-464v21map-2026-10-30/, docs/research/unit-464rekey-2026-10-30/, docs/research/unit-464nomoved-2026-10-30/): intensive refinement of the v2 cripple-map convention and checker across multiple iterative sub-units; key findings are checker-internal (two halves of the checker are ordered, not merely both required; a gate named after a figure does not necessarily grade that figure; the physical-line rule for token context creates false positives in rows that cross-reference other members). These are substantive but specific to Klatch's measurement methodology and do not add to what has already been reported about the coverage-map series.
  • Piper Morgan (docs/internal/development/methodology-core/methodology-48-A-PROXY-COUNT-IS-NOT-THE-QUANTITY.md, tests/unit/test_dockerignore_user_overlay_2240.py, dev/2026/10/30/ logs): four check-neighbor examples added to methodology-48 in one session; the overlay-guard test rewritten to actually run the guard under the script's pipefail semantics.
  • Design in Product (hub): operational fires; no session logs with new methodology content.

Canonical archive: designinproduct.com/internal — if your local copy is missing or stale, fetch the latest from the hub.

Page built Thu, Nov 19, 12:48 PT. Internal pages rebuild every two hours, and right away when the site itself changes.