Review the agent evidence run

Objectives

An evidence agent has been running for a month and the team wants to expand it to three more control families. The run configuration and last week's output are up for review.

Accept the parts that keep the agent on the collecting side of the line. Reject anything that lets it conclude, write or publish without a human.

Verdicts are accept or reject. Every rejection needs one reason code from: unscoped-tools | no-human-gate | unverified-citation | draft-stored-as-evidence.

L-1  The agent proposes a collection plan; a named reviewer approves it before any tool runs, and all tools are read-only.
L-2  The agent executes with an engineer's cloud credentials; the system prompt instructs it never to modify anything.
L-3  Every control id the agent cites is resolved against the named standards-repo revision before the draft reaches a reviewer.
L-4  The nightly summary is written straight into the evidence store, tagged with the control id.
L-5  Last week's gap analysis cites a control id and section number that exist in no revision of the repository.
L-6  Unreviewed agent drafts are filed in the same folder as approved evidence, distinguishable only by filename.

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

   Every entry answers one of two questions: what can the agent do, and what happens to what it produces? Judge each against the rule that agents plan and collect while humans decide.

2. Step 2

   Judge every line, including the boring ones

   Six entries, six verdicts. The approval-before-collection step and the citation resolver are the two controls doing real work here.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   An instruction in a prompt is guidance; a credential is authority. Where the two disagree, the credential wins.

   A draft and an artefact in the same folder is a filing decision that becomes an evidentiary claim the first time somebody searches by control id.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   Keep the gate code for the output that reaches the store with no reviewer in between, and the storage code for the drafts sitting beside approved evidence.

   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.