Sweep per-WP D1 out-of-package notes into tracked follow-ups

[kyle-sexton]

Context

Each ai-adoption-ladder work package's D1 design round produced out-of-package notes — capabilities and concerns deliberately deferred from that WP's scope. They currently live only inside the per-WP plan documents; without tracked follow-ups they risk being lost once the WP PLANs are archived.

Proposed work

• Sweep the WP1–WP3 (and later WP4–WP7) PLAN/design docs under docs/topics/ for D1 out-of-package notes.
• File each note that is still relevant as its own tracked item (or fold it into an existing one), with a pointer back to the originating WP doc.
• Mark swept notes in the source docs as tracked.

Acceptance criteria

• Every D1 out-of-package note in the shipped WP docs is either tracked as an item or explicitly recorded as dropped with rationale.

References

• docs/topics/ai-adoption-ladder/index.md
• Per-WP PLAN docs under docs/topics/

---

Reference: Boris Cherny, "Steps of AI Adoption" (Google Doc)

[kyle-sexton]

D1 sweep disposition (2026-07-20)

Mined every out-of-package / deferred note from the seven merged WP PLAN blocks (PR bodies #333/#343/#356/#372/#377/#600/#676) — 31 notes. Disposition of each class:

Disposition	Notes
Already tracked as issues	Fleet dogfood wiring (WP1/WP2-D1/WP3-D1) → #352 · native-vs-hook audit (WP2) → #351 · classifier tuning + allowlist distribution (WP5) → #697/#695 · e2e + default-on review residue → #694/#696
Contract-recorded triggers (already durable in merged contract text)	Immutable-ID join attribute (reference/telemetry.md) · interactive-work capture expansion + estimation revisit (reference/return-accounting.md) · non-v1 class leaves w/ T7 join triggers (routine contract)
Delivered by a sibling WP	WP1 wiring depth → WP2–WP6 Briefs · WP2 return fields → WP3 · WP3 transport → WP2 sink classes · WP4 routine catalog → WP6 · WP4 dispatch policy → WP5 · WP5/WP6 escalation UX → WP7
Resolved /architect deferred questions	All (naming, pins, schema tokens, templates, band spellings) — resolved in their own rounds per the PLAN records
User-held dormant triggers (no filing, per operator direction)	Runner build (T4) · L3 backend (first C5 admission) · merge serialization (observed collisions) · mid-run interrupt (kill-and-resume cost evidence) · org-enablement (day-job adoption) · cross-team ownership (multi-team adoption) · runner-route fleet materializations (runner-dependent)
Newly recorded durable trigger rows (PR #698)	Fleet guardrail materializations (WP5) · fleet routine stand-up + scheduler reconciliation (WP6) · vendor-binding capability templates (WP6) · cost enforcement (3→4) · cross-repo binding drift check (WP1) · per-class precision graduation (WP3)
Recorded posture, nothing to track	"No sink vendor recommendation" (WP2) — permanent contract stance, not a deferral

Note on the "mark swept notes in the source docs" criterion: the per-WP topic slices were pruned at effort end (#685); the PLAN records now live in the merged PR bodies, which stay as-is — this comment plus the PR #698 trigger rows are the durable sweep record.