Projects · The seven stack questions
Projects
The seven stack questions
The seven infrastructure answers the Architect treats as hard rules when it decides the stack.
The Architect cites these seven answers as hard rules. They are asked on the same card as the project questions, right after the brief is clear enough to price.
| Id | Question | You can skip |
|---|---|---|
cloud_current | Where does your infrastructure run today? | No |
systems_of_record | Which systems hold the data this will touch? | Yes |
load_volume | How much traffic should it handle? | No |
data_sensitivity | How sensitive is the data? | No |
operator_after | Who operates it after go-live? | No |
infra_budget_monthly | Monthly infrastructure budget? | No |
downtime_tolerance | How much downtime can you accept? |
Options are fixed (AWS, GCP, Azure, a PaaS, nothing in the cloud yet; PII / PHI / residency; in-house engineers vs Citeaxis operating it; and so on). Most questions allow an “other” write-in.
What happens if you skip
systems_of_record can be skipped. Everything else should be answered. If you force the price early, skipped answers become assumptions on the Blueprint card visible as known issues, not silent defaults.
