Skip to content

docs(gaps): close GT-532 on its criteria, and carve out GT-651 - #394

Merged
beyondnetPeru merged 1 commit into
developfrom
docs/close-gt-532
Aug 2, 2026
Merged

docs(gaps): close GT-532 on its criteria, and carve out GT-651#394
beyondnetPeru merged 1 commit into
developfrom
docs/close-gt-532

Conversation

@beyondnetPeru

@beyondnetPeru beyondnetPeru commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Correcting my own bookkeeping from #393: GT-532's two acceptance criteria were both satisfied and I left the boxes unticked.

  • Portfolio views existed already (TowerMd3).
  • Per-tenant governance packages landed in evolith_tracker#115.
  • Nothing in the Core references the package types.

So the row closes — on its criteria, not on its title.

The half that did not ship

The title also names marketplace-style adapters. No criterion ever asked for them, and they did not ship. Registered as GT-651 rather than left implicit inside a DONE row.

That distinction is the whole point: an unstated intent inside a closed item is exactly the staleness this board keeps finding, and it is the mirror of the eight rows found this week that described work already done. One direction wastes a week rebuilding something that exists; the other quietly drops something somebody wanted.

GT-651 is deliberately unscoped, and its acceptance criteria say so. What an adapter marketplace means for Evolith — a connector catalogue, a distribution channel for the governance packages GT-532 just made portable, or both — is a product decision. Writing criteria for a shape nobody has chosen would produce a row that can be satisfied without anybody wanting the result.

Bookkeeping

The closure record cites only in-repository paths, as GT-605's does, because every implementing file lives in the Tracker; the rationale says so instead of listing paths that cannot resolve here.

Board: 634 done / 649 total, five pending.

🤖 Generated with Claude Code

Correcting my own bookkeeping from the previous change: GT-532's two acceptance
criteria were both satisfied and I left the boxes unticked.

Portfolio views existed already (TowerMd3) and the per-tenant packages landed in
evolith_tracker#115; nothing in the Core references the package types. So the
row closes.

It closes ON ITS CRITERIA, NOT ON ITS TITLE. The title also names
marketplace-style adapters, which no criterion ever asked for and which did not
ship. That is registered as GT-651 rather than left implicit inside a DONE row -
an unstated intent inside a closed item is exactly the staleness this board
keeps finding, and it is the mirror of the eight rows found this week that
described work already done.

GT-651 is deliberately UNSCOPED, and its acceptance criteria say so: what an
adapter marketplace means for Evolith - a connector catalogue, a distribution
channel for the governance packages GT-532 just made portable, or both - is a
product decision. Writing criteria for a shape nobody has chosen would produce a
row satisfiable without anybody wanting the result.

The closure record cites only in-repository paths, as GT-605's does, because
every implementing file lives in the Tracker; the rationale says so instead of
listing paths that cannot resolve here.
@beyondnetPeru
beyondnetPeru requested a review from a team as a code owner August 2, 2026 23:39
@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

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown

📊 Bilingual Coverage Impact

PR Changes

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

Repository Coverage

Metric Value
Total EN files 526
Total ES files 500
Paired files 0
Coverage 0%

Good: All EN changes have ES counterparts.


Generated by GitHub Actions

@beyondnetPeru
beyondnetPeru merged commit 38e5806 into develop Aug 2, 2026
32 checks passed
@beyondnetPeru
beyondnetPeru deleted the docs/close-gt-532 branch August 2, 2026 23:44
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