mvschwarz e7346bbdbd Strip internal QA seat-name attribution from the shipped design note ...

Leak gate on ce6476b..ba33aa1 flagged one thing: routing-data-boundary.md — a
shipped public design doc — named the internal "sdk-qa" seat five times in the
MF1 lineage prose. Naming an internal seat in shipped product documentation
violates the mechanism-only condition for public lineage (distinct from
commit-message and source-comment attribution, which the standing rule keeps).

Per orch's ruling: preserve the lineage, strip the attribution. The value of the
crossing progression in a routing-data-boundary doc is WHY the boundary is
shaped this way — the six crossing types — not which seat found each. The five
references now read as mechanism only (round numbers, "the trojans", "the
spellings tried"), no seat name. The WHO stays in the commit messages.

Doc-only, one file; no code, test, or contract change. 378/378 unchanged.

2026-08-08 17:58:38 -07:00

..

routing-data-boundary.md

Strip internal QA seat-name attribution from the shipped design note

2026-08-08 17:58:38 -07:00