docs: landscape.md is a per-family status inventory in the explanation quadrant #242

Closed
opened 2026-09-09 18:31:01 +09:00 by natsukium · 0 comments
Owner

docs/explanation/protocols/landscape.md defines status labels (Adopt / Tolerate / Reject) and walks every CSI, OSC, DCS, APC and vendor family row by row. Most rows carry no argument and duplicate what docs/reference/protocols/support-matrix.md already states, so a status flip must be edited in two places with two legends. That is doc-cascade trap 2 (status inventories belong in reference) and the docs-audit gate reviewer flagged it as the one structural item left open.

Proposed shape:

  • keep in landscape.md only the governing admission rationale (why the boundary sits where it does), the rejected alternatives, and the Revisit if triggers, grouped by family rather than by sequence;
  • move any per-family stance that the support matrix does not already carry into the matrix (or a short "stance" column there), so one reference table owns every status;
  • update the docs/README.md blurb and the add-escape-sequence skill, which sends contributors to the landscape for the recorded stance.

Deferred from the docs audit PR because it is a page restructuring rather than a correction.

`docs/explanation/protocols/landscape.md` defines status labels (Adopt / Tolerate / Reject) and walks every CSI, OSC, DCS, APC and vendor family row by row. Most rows carry no argument and duplicate what `docs/reference/protocols/support-matrix.md` already states, so a status flip must be edited in two places with two legends. That is doc-cascade trap 2 (status inventories belong in reference) and the docs-audit gate reviewer flagged it as the one structural item left open. Proposed shape: - keep in `landscape.md` only the governing admission rationale (why the boundary sits where it does), the rejected alternatives, and the `Revisit if` triggers, grouped by family rather than by sequence; - move any per-family stance that the support matrix does not already carry into the matrix (or a short "stance" column there), so one reference table owns every status; - update the `docs/README.md` blurb and the `add-escape-sequence` skill, which sends contributors to the landscape for the recorded stance. Deferred from the docs audit PR because it is a page restructuring rather than a correction.
Sign in to join this conversation.
No description provided.