Guides · Answer the stack questions well
Guides
Answer the stack questions well
How each of the seven answers steers the Architect, and what happens if you skip one.
The seven questions are lock rules. Answer them as the production system will run, not as the demo will run.
- Cloud where it must live, not where you wish it lived.
- Systems of record name the products. “A CRM” is weaker than “HubSpot + the finance Postgres”.
- Load pick the bucket you will actually hit in year one.
- Sensitivity PII vs PHI/PCI vs residency. This one moves hosting and auth.
- Operator “Citeaxis operates it” is a different stack from “we have a platform team”.
- Budget monthly infrastructure, not the project fee.
- Downtime be honest. “None” is expensive and the estimate will say so.
Skipped answers become assumptions on the Blueprint card.
