Judge sufficient and reliable evidence

Objectives

Judge whether each independent evidence item supports its stated claim, not whether every control passed. Reject means insufficient support for that claim, not proven noncompliance.

Baseline: April has 12 production departures. AC-4 version 3 requires removal within 24 elapsed hours. Evidence for full-population compliance must cover all 12 with traceable timestamps, completeness reconciliation, and trustworthy source source and history. Accept appropriately bounded supported claims.

Verdicts are accept or reject. Every rejection needs one reason code from: inquiry-only | insufficient-coverage | unverifiable-provenance | wrong-period.

AF-1 | Claim: all 12 April departures complied. Evidence: an undated manager statement saying our workflow always works, with no records.
AF-2 | Claim: all 12 April departures complied. Evidence: read-only exports with retained source IDs and UTC timestamps verify timely removal for two records; the other ten are explicitly untested.
AF-3 | Claim: account P7 met the deadline. Evidence: a cropped image showing disabled, with no account identifier, timestamp, or source provenance.
AF-4 | Claim: April departures complied. Evidence: authentic reconciled HR and identity events for all May departures, with no April records.
AF-5 | Claim: all 12 April departures complied. Evidence: direct read-only HR and identity provider event exports with extraction metadata, query filters, reconciled complete totals, UTC timestamps and retained source IDs; independent recalculation verifies every removal within 24 hours.
AF-6 | Claim: P9 was late, not that all other departures passed. Evidence: authenticated read-only HR and identity event records for P9 with retained IDs, validated UTC timestamps, and independent recalculation show removal 40 hours after departure.

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

   Judge each row independently against the stated baseline.

2. Step 2

   Judge every line, including the boring ones

   Include each AF identifier once.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Accept only evidence that supports its stated claim. A bounded finding can be well evidenced.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   For rejection select the closest listed defect: inquiry alone, limited coverage, missing source and history, or a different period.

   Each rejection cites a valid reason code

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.