docs: articulate AI-infra fit and how Substrate compares#315
Merged
Conversation
The README asserted 'test harness for AI-generated infrastructure' but never
earned it, and the only competitor mention was a throwaway LocalStack jab. Make
both arguments explicit, grounded, and honest — they share one root cause (the
API-surface scope boundary is both the differentiator and the AI-fit reason).
README + docs/scope.md:
- 'Why Substrate for AI-generated infrastructure': determinism (flakes mislead
the loop), free/fast/offline (run on every generation), cost as a
machine-gradeable guardrail (Intent{MaxCost}), seedable failure paths.
- 'How it compares': honest trade-off table vs LocalStack/moto/Real AWS that
INCLUDES where Substrate is weaker (doesn't run workload code, by design) —
framed as 'a different tier,' not better-than. Links to Scope & Philosophy.
- Renamed the differentiators heading 'Why Substrate' → 'Core capabilities'
(the new subsection now owns the 'why').
Docs build clean (strict link check passes).
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Makes two arguments the README previously only asserted — explicit, grounded, and honest. Added to both the README and the docs Scope & Philosophy page.
1. Why it suits AI-generated infrastructure
AI generates IaC at volume inside generate → test → fix loops, which need:
Intent{MaxCost}fails a deploy that would blow a budget (an AI has no bill-shock instinct).2. How it compares
An honest trade-off table vs LocalStack / moto / Real AWS that includes where Substrate is weaker — it doesn't run your workload code, by design. Framed as "a different tier," not "better than," consistent with the scope boundary. The one deliberate ❌ links to Scope & Philosophy.
Replaces the old throwaway "LocalStack hides bugs" line. Renamed the differentiators heading
Why Substrate→Core capabilitiesso the new subsection owns the "why."Docs build clean (strict link check passes). Deploys to Pages on merge.