Repair the billing release gate

Objectives

Halcyon Clinics is preparing a billing release. The lead says an author can approve because staging passed, and that printing tokens will speed troubleshooting. Neither claim meets the release policy.

Complete the YAML plan using the binding requirements in the fixture. Keep the field structure. The plan must protect production, limit exposure and make its recovery trigger measurable; no real credentials belong in your submission.

Target: production; staging rehearsal uses synthetic data and isolated credentials.
Author cannot approve; independent approval required.
Initially expose 5 percent using a feature flag.
Recover to previous compatible artefact if error percentage exceeds 2
across a 5-minute window; require at least 200 requests.
Credential delivery: runtime secrets service; never store secrets in code.
Credential rotation must revoke the old credential after consumer cutover.
Security logs include actor, action, outcome, correlation ID.
Never log passwords or tokens. Page on-call when telemetry heartbeat is missing.

Step-by-step hints

The guided walkthrough, in full. It is free: no XP cost, and it does not touch the paid hint ladder or the reveal gate.

1. Step 1

   Locate the trust boundaries

   Identify the destination and how rehearsal data and credentials differ from live resources. Check that isolation is a real boolean rather than prose.

   Production and rehearsal boundaries are explicit

2. Step 2

   Trace decision authority

   Ask whether a second person must authorise the release and whether any field still permits the creator to authorise it alone.

   Approval cannot be granted by the author

3. Step 3

   Separate installation from reach

   Choose the mechanism that changes which users enter a path, then copy the initial cohort size from the binding policy.

   Initial exposure is constrained

4. Step 4

   Make recovery testable

   Describe restoring a compatible release. Check the trigger's rate, duration and sample size against the fixture, rather than choosing a familiar default.

   Recovery has an executable action and exact trigger

5. Step 5

   Follow credentials through retirement

   Describe retrieval at execution time and decide where credentials must not persist. Ensure consumer cutover does not leave the superseded credential usable.

   Credential delivery and retirement are safe

6. Step 6

   Design evidence and its failure alarm

   Compare event fields and prohibited content with the policy. Ensure a collection outage becomes an actionable notification to a named duty role.

   Security events are safe and telemetry loss pages a responder

Rules summary

• XP on pass

  40 bonus XP the first time every check goes green.

• Paid hints

  2 available. Each costs 25% of the lab XP (about 10 XP).

• Reveal solution

  Scores 0 XP and unlocks only after 3 check runs.

• Attempt cap

  60 check runs per learner. The runner warns you in the last 10.

• Drafts

  Your editor content is saved in this browser, so a reload will not lose work.

• Walkthrough

  Always free and never penalised: use it before spending a hint.