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.
T38 · Environment separation and safe failure visibility
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced software |
| Layer / kind | Configuration · API · operations |
| Priority | P0 |
| Gates | A09, A10 |
| Build step | Step-01-Foundation |
| Decisions | Q09 |
Given
Separate stage/prod credentials and data stores are planned; synthetic fixtures contain canaries.
When
Inspect deployment configuration without printing secrets; provoke validation errors, worker failures, unsafe text and request-rate bursts.
Then / oracle
Staging cannot write production or send to real members. Logs/errors contain no private bodies, credentials or raw tokens. Limits are measured against agreed policy; authorised support gets safe incident and failed-job evidence.
Evidence required
Environment-access matrix; secret/body scan; error/rate-limit tests; runbook ownership.
Decision dependency (verbatim)
Q09: hosting region, data/processor approval, retention, incident owner and test rate budgets.
Source: TDD rev 1.3 (PDF); machine-readable in 10-Sources/tdd-bundle/. Back to Scenario-Index · Traceability-Matrix · integration dependencies in Dependency-and-Regression-Table.