Verification
A checklist for validating enterprise project architecture and operations.
Use this page to verify that an enterprise project is ready to scale beyond an initial team.
| Check | Pass condition |
|---|
| Workspace boundaries | Apps, packages, tooling, and docs have clear roles |
| Dependency direction | Packages do not depend on apps |
| Ownership | Each app and shared package has an accountable owner |
| Shared contracts | Public package APIs and breaking-change rules are documented |
| Check | Pass condition |
|---|
| Turbo pipeline | Tasks, outputs, cache, and env rules are explicit |
| CI/CD | Static checks, tests, build, security, and deploy gates run predictably |
| Preview review | User-facing changes can be validated before production |
| Testing | Coverage matches business and operational risk |
| Check | Pass condition |
|---|
| Agent workflow | Context packs, task scopes, and review gates exist |
| Security | Secrets, access, dependencies, and high-risk changes are governed |
| Monitoring | Logs, metrics, traces, alerts, and dashboards are owned |
| Incident response | Runbooks, escalation, and postmortem process are documented |
| Area | Pass condition |
|---|
| Next.js | Proxy and cache guidance matches Next.js 16 docs |
| Turborepo | CI and cache guidance matches 2.9 behavior |
| Vercel | Rollout, protection, rollback, and function guidance links to current docs |
| Skills | Commands use npx skills, not deprecated npx add-skill |
| Codex | Managed policy examples use documented requirements.toml keys |
- Shared packages change without consumer verification.
- Deployment depends on undocumented local steps.
- Agents receive broad tasks without system context or ownership boundaries.
- Incidents close without follow-up tasks and runbook updates.