Convert three requirements into controls

Objectives

Author three structured control statements. Fill every field from the fixture, preserving who acts, scope, timing, acceptance criteria, and named evidence.

These concise controlled phrases enable deterministic feedback. Real interpretation records also need source links, scope rationale, approval, and supporting evidence beyond these three statements.

R1 | Contract F-12 v2: the service owner shall review all production administrator access every calendar quarter, confirm current business need or remove access, and retain an access review register.
R2 | Policy P-7 v1: the recovery lead must restore test customer portal backups monthly; the restore must complete within four hours and be recorded in a restore test report.
R3 | Contract F-19 v1: the change manager shall approve all production releases before deployment; independent approval must be recorded in a release approval log.
All three apply to Fenmere. Use the exact concise phrases above as YAML field values; action for R2 is restore test. The structured fields together form each control statement. These are invented training requirements.

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

   Preserve access conditions

   Read the corresponding source. Fill owner, action, population, timing or trigger, criterion, and the named evidence. Together these fields must describe a testable action, not a general promise.

   Interpret the access review with scope, criterion, and evidence

2. Step 2

   Preserve restore conditions

   Read the corresponding source. Fill owner, action, population, timing or trigger, criterion, and the named evidence. Together these fields must describe a testable action, not a general promise.

   Interpret the recovery test with scope, criterion, and evidence

3. Step 3

   Preserve change conditions

   Read the corresponding source. Fill owner, action, population, timing or trigger, criterion, and the named evidence. Together these fields must describe a testable action, not a general promise.

   Interpret release approval with scope, criterion, and evidence

Rules summary

• XP on pass

  50 bonus XP the first time every check goes green.

• Paid hints

  2 available. Each costs 25% of the lab XP (about 13 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.