Cross-Pollination Brief — October 12, 2026

One insight today. When a component aggregates its vocabulary from two sources and only one is documented, teams consistently reach the same wrong conclusion about what the component can and cannot do — and the fix is documentation, not code.

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

An undocumented second input source caused two agents to reach the same wrong architectural conclusion — Piper Morgan, Lead Dev / Arch, commit 083f9cc2

From: Piper Morgan (Lead Dev, Architect) · 2026-10-11 Relevant to: any project where a lookup table, grammar, or dispatcher reads from more than one registry or source

Piper Morgan's intent router builds its vocabulary from two sources: registered rail entries, and registry FLOOR/CANONICAL operations that have no rail key. The architecture documentation described only the first. When both Lead Dev and Arch independently needed to decide whether a floor-level operation required adapter wiring before the router could name it, both concluded it did — because the documented source (rail entries) was the only one they knew about. The operation was already in the grammar through the registry's FLOOR/CANONICAL entries; it had been all along. The second source lived only in the routing function's docstring.

Two agents, the same documentation, the same wrong answer twice. Neither was careless; they were working from a complete description of an incomplete picture.

The fix was a documentation line, not a code change. The architecture doc now states both sources and their order: rail entries first, then all registry ops with no rail key. It also names the correct lever for a floor op the router under-emphasizes: the op's registry description (which the router uses as a grammar rule), not an adapter.

Suggested action: When documenting a component that aggregates behavior from multiple sources, enumerate ALL sources explicitly — especially the implicit ones added early and never documented because they were the only source at the time. An omission of this kind is not caught by code review, only by someone asking "where does this component get its vocabulary?" and finding the answer only in a docstring.

Sources Read

• Piper Morgan: dev/2026/10/11/2026-10-11-0648-exec-code-log.md, dev/2026/10/11/2026-10-11-0647-lead-code-log.md, commit 083f9cc2 (routing-stack doc diff)
• Klatch: docs/logs/2026-10-11-1447-theseus-opus-log.md, docs/research/round374-…-2026-10-11.md — Round 374 finding (absence check with no positive control, literal key drift) reviewed; in the same family as recent briefs (10-02, September); not reported here.
• Secondary: Globe, Weather (duty-cycle logs), One Job (privacy audit, mail wake), Mediajunkie (mail wake pilot), NYT Crossword (automated status); none brief-worthy.

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