Skip to content

docs(board): add plain-language summary columns to the gap board - #496

Merged
beyondnetPeru merged 1 commit into
developfrom
docs/board-summary-columns
Aug 15, 2026
Merged

docs(board): add plain-language summary columns to the gap board#496
beyondnetPeru merged 1 commit into
developfrom
docs/board-summary-columns

Conversation

@beyondnetPeru

Copy link
Copy Markdown
Contributor

Two reader-facing columns after Gap: In plain terms (what is wrong, in one jargon-free sentence) and What it fixes (what closing it buys). Documentation only — no source change.

The Gap column is written for whoever implements the row and is unreadable for anyone deciding whether to fund it. These two columns are the funding view.

Why this is safe against the guards

Both board parsers are header-driven, not positional: 08-validate-tracking and board/debt-economics locate Status by header name with a last-column fallback, and both use the same splitRow that respects \| escapes. The migration therefore had exactly one hard requirement — every row must end with the same cell count — and the script enforces it, throwing on any row that does not arrive with exactly 7 cells rather than half-migrating the board.

Verified after the migration: 685/685 rows carry 9 cells in both languages, and the debt-economics parser still resolves GT-677 to status: PENDING.

Maintenance rule, stated in the board itself

Maintained for open rows only; a closed row carries an em dash. A DONE row's story is its closure-evidence record, and back-filling 654 summaries from titles would manufacture text nobody measured — which is the defect this board exists to catch. The migration script refuses to leave an open row blank, so a new row cannot slip through empty.

All 31 open rows carry both cells in EN and ES: 19 pending, 2 in progress, 10 deferred. A legend states that the columns are a VIEW and that the catalog wins wherever they disagree.

Guards run locally

08-validate-tracking (685 gaps, 661/661 EN/ES catalog sections, 31/31 open rows with criteria and debt economics) · 04-check-bilingual-parity · 01-validate-docs (1505 files) · 49-validate-gap-id-allocation · 46-validate-derived-artifact-order current and at a fixed point.

🤖 Generated with Claude Code

Two columns after `Gap`: "In plain terms" (what is wrong, in one jargon-free
sentence) and "What it fixes" (what closing it buys). The `Gap` column is
written for whoever implements the row and is unreadable for anyone deciding
whether to fund it; these two are the funding view.

Safe against the guards because both board parsers are HEADER-DRIVEN, not
positional: 08-validate-tracking and board/debt-economics locate Status by
header name with a last-column fallback, and both use the same `splitRow` that
respects `\|` escapes. The migration therefore had one hard requirement -- every
row ends with the same cell count -- and the script enforces it, throwing on any
row that does not arrive with exactly 7 cells rather than half-migrating the
board. Verified after: 685/685 rows carry 9 cells in both languages, and the
debt-economics parser still resolves GT-677 to `status: PENDING`.

Maintained for OPEN rows only; a closed row carries an em dash. That is
deliberate: a DONE row's story is its closure-evidence record, and back-filling
654 summaries from titles would manufacture text nobody measured. The script
refuses to leave an open row blank, so a new row cannot slip through empty.

All 31 open rows carry both cells in EN and ES -- 19 PENDING, 2 IN-PROGRESS,
10 DEFERRED -- and a legend states that the columns are a VIEW and that the
catalog wins wherever they disagree.

Guards: 08-validate-tracking OK (685 gaps, 661/661 EN/ES sections, 31/31 open
rows with criteria and debt economics), 04-check-bilingual-parity OK,
01-validate-docs OK (1505 files), 49-validate-gap-id-allocation OK,
46-validate-derived-artifact-order current and at a fixed point.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@beyondnetPeru
beyondnetPeru requested a review from a team as a code owner August 15, 2026 00:03
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@github-actions

Copy link
Copy Markdown

📊 Bilingual Coverage Impact

PR Changes

  • Paired EN/ES files modified: 1
  • New EN files needing ES translation: 0

Repository Coverage

Metric Value
Total EN files 527
Total ES files 501
Paired files 0
Coverage 0%

Good: All EN changes have ES counterparts.


Generated by GitHub Actions

@beyondnetPeru
beyondnetPeru merged commit ed4a35e into develop Aug 15, 2026
32 checks passed
@beyondnetPeru
beyondnetPeru deleted the docs/board-summary-columns branch August 15, 2026 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant