docs(audit): scope GAP-004 blocker by blocker; Core half filed upstream as GT-650 - #110
Merged
Conversation
…am as GT-650 The row said 'Define owner and remediation action before execution' and nobody ever had. Each of the three upstream dependencies was probed today rather than assumed. Core API. The root cause is not a missing endpoint, it is that the Core has no single answer to endorse: two unreconciled artifact corpora that disagree on names, on membership in both directions, and on phase — Coverage Report is a construction artifact in one and a quality artifact in the other — while the HTTP surface serves a third file with no artifacts at all. Filed upstream as evolith_arch32 GT-650 (PR #383) with five acceptance criteria. Cannot be unblocked from this repository. UMS JWKS. Still blocked; T-053 is still Proposed. Probed today: the local UMS ingress answers 503 on every path, so nothing could even be re-tested. The Tracker already carries both validation modes, so this blocks the target state rather than the product. UMS Auth Graph. Same system, same reachability, still blocked. Also recorded: the residue of GAP-020 lands here, because tenant-aware sync of the artifact catalog is the same seam and the same blocker.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GAP-004 is CRITICAL, has been open the whole time, and its next step read "Define owner and remediation action before execution" — which nobody ever had. Each of its three upstream dependencies was probed today rather than assumed.
1. Core API — root cause found, filed upstream
Not "the Core has not built an endpoint". The Core has no single answer to endorse. It holds two unreconciled artifact corpora that disagree on names, on membership in both directions, and on phase —
Coverage Reportis a construction artifact ingate-f3and a quality artifact inUNIVERSAL_PHASE_ARTIFACTS. Neither is what the HTTP surface serves; that reads a third file with no artifacts at all.Filed as
evolith_arch32GT-650 with five acceptance criteria, including that the losing corpus must be deleted or derived — two files that agree today drift tomorrow.Cannot be unblocked from this repository. It needs an ADR upstream.
2. UMS JWKS — still blocked
T-053is stillProposed. The UMS publishes no.well-knownand issues symmetric HS256. Probed today: the local UMS ingress answers 503 on every path, so nothing could even be re-tested. The Tracker already carries both validation modes, so this blocks the target state, not the product.3. UMS Auth Graph — still blocked
Same system, same reachability.
What was mistaken for progress
This row had been closed once with "Resolved via Defensive Isolation (Mocks)". The stand-ins are real and are why the product runs — they are not why the dependency is resolved. The next step now says to re-probe before assuming any of the three moved.
Also recorded: the residue of GAP-020 (tenant-aware sync of the artifact catalog) lands here, same seam and same blocker.
🤖 Generated with Claude Code