Gate 03 · Tech Stack

The stack decides more than it looks like it does. The database shapes the schema, the platform shapes the UX, and both shape the risks, so pinning it here means your agent writes code that’s idiomatic for your setup rather than a generic average.

If you’ve already chosen a framework, language, database, or host, say so. If you haven’t, describe the shape of the product, a mobile app, a web SaaS, an API service, and let the Architect propose one. Either way, name the constraints that actually bind you: a platform you have to target, a service you already pay for, the skills your team has today.

Aim for a stack that fits the product and the team, not the trendiest option on the page. A mobile app should read as mobile; a data-heavy tool should name its database and say why.

Changing the stack later ripples: the schema and the risk register both read from it, so expect stale flags. If a piece is genuinely undecided, leave it as “TBD” with a note, which beats committing to the wrong thing.

Output: tech-stack.md.