Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
Build, test and deployment
Purpose
The path from a commit to production, and who owns each gate.
Source notes
Deployment-and-Operations, Step-10-Hardening-and-Operations, Step-11-UAT-and-Release.
Current state
Proposed. No pipeline exists. Deploy is a placeholder until hosting is decided (D08 in Proposal-Decisions-D01-D10, Q09).
Path
Local, then CI (tests, build, scan; every pull request, ADR-0005-CI-on-Every-Pull-Request), then staging with synthetic data, then DG user acceptance and readiness review, then separate written launch approval from DG, then production with smoke checks and monitoring. Production is never deployed on silence.
Rules
- DG owns production accounts and funds hosting, identity, email and later providers.
- Local, staging and production have separate data and credentials.
- Versioned builds and migrations; reversible rollout where feasible; migration backup or forward-recovery plan; documented rollback decisions.
- The 99.5% monthly availability in the proposal is a planning reference, not an SLA and not a staging-proven result.
- The agent never deploys. The owner merges and deploys.
Scenarios
Change history
| Date | Change |
|---|---|
| 2026-10-20 | Created (bootstrap Phase 2) |