Audit the remediation board before sign-off

Objectives

The programme manager says all six ledger decisions are ready because each has a ticket and a named person. Review the decisions against the policy below, not the colour of their status labels.

Accept defensible decisions, including a properly bounded exception that does not claim closure. Each rejected line contains one primary defect. Reason codes mean: wrong-priority = policy ranking contradicted; wrong-control = safeguard cannot address the attack; missing-verification = closure lacks independent production retest; invalid-exception = continuing exposure has no bounded approval.

Verdicts are accept or reject. Every rejection needs one reason code from: wrong-priority | wrong-control | missing-verification | invalid-exception.

Policy: confirmed cross-patient production disclosure is critical. Object access needs server-side authorisation. Verified closure requires independent retest of the deployed build. Exceptions require authorised risk approval, compensating safeguard and expiry, and do not count as timely closure.
ACR-1 | Confirmed cross-patient disclosure ranked low because login is required; otherwise assigned and tracked correctly.
ACR-2 | Record-access fix changes only button visibility; server still returns other patients' records. No closure claimed yet.
ACR-3 | Critical fix marked verified closed on a deployment receipt; independent test not performed.
ACR-4 | Critical item overdue indefinitely; delivery engineer approves own exception, no expiry or compensating safeguard.
ACR-5 | APP-AC-01 ownership check deployed in build deploy-431; security-assurance independently confirms cross-patient read and update denial with no medical fields, plus allowed own-record access; report, change, deployment and test references retained; closure timestamp recorded.
ACR-6 | Overdue high item remains open under risk authority's signed seven-day exception; vulnerable route disabled, monitoring enabled, review date and expiry recorded; original deadline retained and excluded from timely-closure numerator, not from due cohort.

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

   Read the request before the artefact

   Read the policy first, then identify the actual decision each ledger entry asks you to endorse.

2. Step 2

   Judge every line, including the boring ones

   Give every fixture identifier one verdict; retaining all rows makes the review population auditable.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Test ranking against consequence, safeguards against the exploit path, and closure against deployed behavioural evidence. For an exception, inspect authority, limits and reporting treatment instead of requiring it to pretend to be remediation.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   For each rejected decision select the code naming its primary failed gate. Do not penalise a correctly governed open risk merely because it remains unresolved.

   Each rejection cites a valid reason code

Rules summary

• XP on pass

  60 bonus XP the first time every check goes green.

• Paid hints

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