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.
Step 10 · Hardening and operations
Goal. Responsive accessibility, agreed load, restore, migration and release evidence on the integrated build.
Not started. This is a specification; no code has been written. The primary-step mapping is an index, not proof that each full scenario can be completed in its step: see Dependency-and-Regression-Table.
Prerequisites
Steps 01–09 on one integrated build. Blocked until DG decides: load, recovery and accessibility targets, retention (Q09) and acceptance criteria (Q11); a target nobody agreed is not measured as a pass.
Changes (illustrative, not a final schema)
Accessibility fixes, load and recovery measurements, restore drill, runbooks.
Build items:
- Accessibility checks on core screens
- Agreed load/recovery targets measured
- Backup restore into isolated environment with measured recovery
- Runbooks and failed-job recovery
Expected outputs and invariants
Each agreed target is measured on the integrated build; unmeasured targets stay unverified.
Tests-first subset
Primary scenarios of this step (write these tests first): T39, T40.
Assertions to write first: T39, T40 (restore and migration part), the operations part of T36.
Method: make one meaningful test fail for the expected reason, implement the minimum behaviour, refactor without changing the observable contract. A scenario whose decision is still pending stays Pending decision; no oracle is invented.
Deferred integration checks
Scenarios whose primary step is this one but whose full variants need later components:
- T39 — needs step 04, 05, 06, 08: Core screens exist only after those steps; measured at step 10 on the integrated build.
- T40 — needs step 11: Release evidence is to be verified in step 11.
Follow-up verification brought here
Earlier scenarios that can only be completed or rechecked once this step exists:
- T36 — The operations part needs the integrated build and runbooks.
- T38 — Worker-failure visibility and staging email-sink isolation need the worker (07); the integrated operations review is at step 10.
Decisions DG must settle (dependent behaviour stays blocked until DG chooses)
Exit evidence
Evidence recorded per agreed target on a named integrated build.
Evidence is recorded only for a named build and fixture. A software scenario is not recorded as Passed until all its relevant variants have been exercised on a named integrated build (step 11).
Navigation: Step-09-DG-Membership-Tool-and-Metadata ← this step → Step-11-UAT-and-Release · Implementation-Order-Overview