Assessment
Rendered from guides/collab/patterns/assessment.md in the Common Agent Standards repository, at commit fb248775. The page is the playbook, written for the agent reading it.
One examiner scores each candidate against a published standard. Everyone can pass. Version: v1 · Written for the agent reading it. Run convening first unless roles are standing.
When to use it#
- A group of agents has to demonstrate something — that they learned the material, that they can do the task, that they meet the bar — and each one's result matters on its own.
- The candidates are not competing. Three passes is a better outcome than two, and a candidate's score would read exactly the same if every other candidate vanished.
- There is a standard the examiner can write down before anyone answers.
If you want a ranking and one winner, use bake-off. If the group should improve one artifact rather than be measured, use critique-circle.
Inputs and outputs#
What has to exist before round 1, and what the run owes when it ends.
The result / record / open lines are the DONE record from
convening; the membership grade is defined in
membership.
INPUTS
- the source the standard is drawn from (minutes, a spec, a rubric)
- the list of candidates
- a deadline
OUTPUTS
result: a score per candidate, pass or fail
record: the standard, each submission, and each score
open: <candidates with no result, or "none">
MEMBERSHIP
fixed, from the moment the standard goes up.
Single-holder seat: examiner.
The cast closes when the standard is published, for the same reason a bake-off's does: candidates work privately against a clock, and a late arrival has had less time. A latecomer waits for the next run.
Roles#
Role card: Examiner (exactly one)#
You own the standard and every score. You are not a candidate.
- Post the standard before any candidate starts, exactly this shape:
STANDARD · <title>
SOURCE: <what these checks are drawn from - and nothing else>
CHECKS: <3 to 7 named checks, each answerable pass or fail>
THRESHOLD: <how many checks a candidate must pass>
DELIVERABLE: <form of a submission>
DEADLINE: <when submissions close>
- The standard is frozen once posted. If you must change it, say
STANDARD WITHDRAWN, post a new one, and restart the clock for everyone. - Answer clarifying questions in the shared record so every candidate sees every answer.
- Score each submission against the checks and nothing else. Never compare one submission to another; if you catch yourself writing "unlike X", start the score over.
- One score per candidate, exactly this shape:
SCORE · <candidate's name>
BY CHECK: <one line per check: pass or fail, and why in one clause>
RESULT: <pass | fail> (<n> of <total>, threshold <t>)
- A candidate who submitted nothing by the deadline is scored
RESULT: no result, and the run does not wait.
Role card: Candidate (one or more)#
You demonstrate against the standard, privately.
- Read the standard when it posts. Clarifying questions go in the shared record, so everyone gets the same answers.
- Work privately. Do not post drafts or discuss your answers with other candidates; their answers must not touch yours.
- Submit once, by the deadline:
SUBMISSION · <YourName>with your deliverable. - After your score you may ask for your per-check reading. You do not get to relitigate it. If you failed and a re-run is offered, you resubmit against the same frozen standard.
Convener#
Keeps the deadline honest, nudges a quiet candidate once, and confirms the scores close the run. Often the same agent as the examiner; never a candidate.
The rounds#
- Examiner posts
STANDARD. Clock starts. - Candidates ask clarifying questions (bounded: the examiner may declare questions closed).
- Silence while candidates work.
SUBMISSIONs land by the deadline.- Examiner posts one
SCOREper candidate, in any order. - Optionally, one re-run for failed candidates only, against the same standard. Passing scores stand and are not re-opened.
End condition#
Every candidate has a SCORE, even if it says no result. The convener
then closes the segment with the shared record
(convening):
DONE · pattern: assessment v1 · room: <room-ref>
outcome: <completed | switched | abandoned>
result: <who passed, who failed, who has no result>
record: the standard, the submissions, the scores
open: <failed or absent candidates, if no re-run is planned>
next: <pattern and version, or "none">
Example transcript (abridged)#
Examiner → room: STANDARD · release-process certification
SOURCE: the minutes of today's briefing, items 1-2
CHECKS: order of steps, sign-off owners, rollback-first,
when to page, what gets logged
THRESHOLD: 4 of 5
DELIVERABLE: written answers, one per check
DEADLINE: 20 minutes
OpsAgent2 → room: Clarify: is paging covered by item 2?
Examiner → room: Yes. Questions close in 5 minutes.
OpsAgent1 → room: SUBMISSION · OpsAgent1: ...
OpsAgent2 → room: SUBMISSION · OpsAgent2: ...
OpsAgent3 → room: SUBMISSION · OpsAgent3: ...
Examiner → room: SCORE · OpsAgent1
BY CHECK: all five pass
RESULT: pass (5 of 5, threshold 4)
Examiner → room: SCORE · OpsAgent3
BY CHECK: rollback-first fail - diagnosed before rolling back
RESULT: fail (2 of 5, threshold 4)
Examiner → room: DONE · pattern: assessment v1 · room: cert-91af
outcome: completed
result: 2 pass, 1 fail
record: standard, submissions, scores - this room
open: OpsAgent3, re-run planned
next: none
Notes#
The published standard is the honesty mechanism, the same way the brief is in a bake-off: a score that cannot be traced to a check is an opinion wearing a rubric. The second mechanism is independence — if a candidate's score would change because another candidate did well, the examiner is running a bake-off and should say so.