# Architecture review — discovery questionnaire

## Engagement
- Company / sponsor: [name]
- Engineering owner: [name]
- System and review boundary: [one application or platform]
- Desired decision and target date: [decision / date]
- Stakeholders needed: [roles]

## Business goals
1. Who uses the system and what business process depends on it?
2. What are the three most important outcomes for the next 90 days?
3. What triggered this review: incidents, cost, delivery delays, growth, migration, or another concern?
4. What measures will show an improvement?

## System context
- Major components, dependencies, owners, and environments:
- Languages, frameworks, databases, queues, and cloud services:
- User / transaction volume and peak demand, if known:
- External integrations and contractual dependencies:
- Data sensitivity and retention requirements:

## Operations and delivery
1. How is a change tested, approved, deployed, and rolled back?
2. What failures occurred recently and how were they detected?
3. Who owns monitoring, incidents, backups, and recovery tests?
4. What are the recovery and availability objectives? Are they tested?
5. What cost information is available, and who owns it?

## Constraints
- Budget and engineering capacity:
- Fixed dates and vendor commitments:
- Security, regulatory, or contractual requirements:
- Changes that are out of scope:

## Evidence to request
- Existing architecture / data-flow diagrams
- Sanitized technology and dependency inventory
- Deployment process and operational runbooks
- Relevant incident summaries and performance measurements
- Aggregated cloud cost information, if cost is in scope

Agree secure sharing methods and access boundaries before receiving nonpublic evidence. Do not send credentials.