# Technical diligence guide

Prepare the evidence an investor, acquirer, enterprise buyer, technical advisor, or incoming engineering leader will request.

Good diligence connects technical evidence to business consequences. It distinguishes a known defect from a missing artifact and a temporary workaround from structural risk.

## Architecture and ownership

Explain how the system changes.

- [ ] System context and critical dependencies
- [ ] Module, service, and decision owners
- [ ] Known coupling and replacement constraints

## Security and data

Show the boundaries that protect value.

- [ ] Identity, authorization, and tenant model
- [ ] Sensitive-data inventory and retention
- [ ] Secrets, vendors, and privileged-access controls

## Delivery evidence

Prove changes can ship safely.

- [ ] Critical-path tests and CI results
- [ ] Deployment, migration, and rollback process
- [ ] Release cadence and failure history

## Operations and resilience

Show how failure is detected and repaired.

- [ ] Monitoring and alert ownership
- [ ] Incident, backup, and recovery evidence
- [ ] Capacity limits and scaling assumptions

## Commercial risk

Translate findings into decisions.

- [ ] Key-person and vendor concentration
- [ ] Licensing and dependency exposure
- [ ] 30/60/90-day remediation priorities

## Evidence to keep

- One-page system map
- Risk register with evidence links
- Last successful build and deployment record
- Prioritized remediation plan with owners