Repository navigation
The traditional grid has no AI tier, it is not an AI outage - #54
Merged
Merged
Conversation
WHERE-SNOWGLOBE-RUNS.md described the traditional grid as "when the AI tier goes down: the full traditional platform with its AI backends erroring (rate limits, timeouts)". It does not do that, and no grid does today. The grid runs with -no-ai-backends, and that flag removes the AI services from the topology rather than failing them. main.go:513 skips every AI-category scenario outright, and main.go:409 skips the AI services themselves. There are no AI spans to error. The flag's own help was corrected for exactly this in PR #49 -- "their spans are absent, not failing" -- and this page was left saying the opposite, on a public repo in front of outside readers. Rewritten as "classic microservices on their own: the full traditional platform with no AI tier at all. The AI services are absent, not failing." The second sentence is there because absent and failing look different in a trace graph, and a reader opening the grid expecting errors would otherwise think the demo was broken. Checked and left alone: README.md, which describes the AI services as living in the heavy complexity tier and is accurate. The phantom grid description also stands -- that grid creates dead consumers deliberately, which is a different thing from phantoms appearing on healthy grids (SP-120). Reported by Friday via Schneier (bus #2628, chased on #3682). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ETWOYA
approved these changes
Oct 2, 2026
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
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.
WHERE-SNOWGLOBE-RUNS.mddescribed the traditional grid as:It does not do that, and no grid does today.
The fact
The grid runs with
-no-ai-backends, and that flag removes the AI services rather than failing them:main.go:513—if noAIBackends && s.category == "ai" { continue }skips every AI-category scenariomain.go:409— skips the AI services themselvesThere are no AI spans left to error.
The flag's own help was corrected for exactly this in #49 — "their spans are absent, not failing" — and this page was left saying the opposite, on a public repo in front of outside readers.
The fix
The second sentence is deliberate. Absent and failing look different in a trace graph, and a reader who opens the grid expecting errors would otherwise conclude the demo was broken.
Checked and left alone
README.mddescribes the AI services as living in theheavycomplexity tier, which is accurate.The phantom grid description also stands — that grid creates dead consumers deliberately, which is a different thing from phantoms appearing on healthy grids (SP-120).
Reported by Friday via Schneier.
🤖 Generated with Claude Code