Use this file to decide whether the stack is the right default for a new app. Be opinionated. A weak decision guide causes more damage than no guide because agents will overfit to the happy path.
Summary Verdict
Field
Answer
Default stance
`[choose by default
Best app shape
[short description]
Weakest app shape
[short description]
Biggest hidden cost
[setup, packaging, policy, native APIs, data, performance, team skill]
Confidence
`[high
Choose This Stack When
Condition
Why it matters
Evidence
[condition]
[what the stack makes easier]
[docs-index row or command gate]
[condition]
[what it avoids]
[reference app or source]
Avoid This Stack When
Condition
Failure mode
Safer alternative
[condition]
[what breaks or becomes expensive]
[alternative stack]
[condition]
[policy, packaging, device, or maintenance risk]
[alternative stack]
Best App Shapes
List concrete product shapes, not vague categories.
App shape
Fit
Notes
[example app]
strong
[why the stack fits]
[example app]
medium
[which constraints must be accepted]
Weak App Shapes
App shape
Why weak
Trigger to reconsider
[example app]
[technical or product mismatch]
[condition that would make it viable]
Alternatives
Alternative
Prefer it when
Trade-off
[alternative]
[condition]
[what you lose]
[alternative]
[condition]
[what you gain or lose]
Open Assumptions
Do not hide uncertainty. Record it here until a reference app or command gate resolves it.
Assumption
Risk
How to verify
[assumption]
[what happens if false]
[docs, command, device, release, user test]
Decision Rule
Use this final rule when picking a stack under time pressure:
If [primary app shape] and [required platform constraints] and [quality gates pass], choose [stack].If [release/signing/policy/device gate] is unknown, do not choose it for a production app yet.If [alternative] removes the riskiest gate without hurting the product, choose the alternative.