Playbook › Track 1: Environment readiness
Track 1: Environment readiness
Track 1: from questionnaire to one-click environment. Led by the client delivery team with environment
expertise. The finish line is stated up front: the entire environment can be stood up on demand, because every parameter it needs has been
gathered, validated, and filled into the binding, and the provisioning pipeline has already run green in a sandbox.
Step by step
Discover
- Environment questionnaire. A structured instrument built from Discovery sections E and H: identity provider, access slicing and information walls, residency and jurisdictions, retention and legal hold, data sensitivity tiers, cloud mandates, budget ranges, latency expectations, alert recipients.
- Current-state assessment. How the client's environment is set up today: account and subscription structure, identity, network posture, key management, CI/CD maturity, data platforms, and any existing AI infrastructure. Each element is classified: keep and integrate, wrap, or provision fresh.
- Interviews and data gathering. Sessions with IT, security, and platform owners; the document requests from Discovery E collected in parallel so the security review clock starts early and never blocks the pilot.
Specify
- Draft the environment specification. Both halves in one document: the harness aspects (per-run machinery configuration: budgets, guardrail scopes, session policy) and the platform aspects (accounts, identity, network, secrets, CI/CD, backup and recovery). Every line resolves to a C5 or C7 plane slot or to a provisioning parameter; the business-blindness rule applies to all of it.
- Select the platform. Map the specification onto the chosen cloud overlay (AWS, Azure, or GCP on the Cloud platform overlays page) and pick the portable-shelf options; record the managed-harness buy-versus-build evaluation on the Decision Register.
- Fill the binding. Environment values land in the C5 and C7 bands; anything the questionnaire could not answer becomes a named open item with an owner interview scheduled, never a guess.
Prove
- Dry-run the one-click setup. Execute the 28-step greenfield sequence as an automated pipeline against a sandbox account: the stamped SSRA skeleton, identity, data plane, tool layer, agent runtime, observability. Every step's done-when check must pass without manual intervention.
- Gate. The environment is declared ready to provision on demand. From this point, standing up the client environment is an execution decision, not an engineering project.
Deliverables
| Deliverable | Lands as |
|---|---|
| Environment specification (harness + platform) | Engagement record; each value traced to a plane slot |
| Current-state assessment | Keep / wrap / provision classification per element |
| Filled C5 and C7 environment values | The binding |
| Proven provisioning pipeline | Green dry-run of the setup sequence in a sandbox |
This track uses: Discovery sections E and H, the Cloud platform overlays and Greenfield setup sequence pages, and the C5 and C7 bands.