Review triage

Type: kb/types/instruction.md

Inspect note-changed stale pairs and ack those where the diff is insignificant for the gate. This reduces the review queue before launching review sub-agents or a review sweep command.

Inputs:

  • {bundle-or-all} — a bundle name (e.g. prose, semantic) or --all-gates
  • {note-scope} — one or more note paths or directories to limit scope

Steps

1. Get note-changed pairs

commonplace-review-target-selector --model {model-id} {bundle-or-all} --note {note-scope} --json --reason note-changed

If the output is an empty array, stop — nothing to triage.

2. For each note-changed pair, judge the diff

For each entry, read the diff field and the gate_id. Ask: does this diff affect what the gate tests?

Guidelines:

  • A typo fix, whitespace change, or link-text tweak is insignificant for almost every gate.
  • A rewording of a claim is significant for semantic/grounding-alignment and semantic/internal-consistency but probably not for structural/general-before-specific.
  • Adding or removing a section is significant for prose/proportion-mismatch and semantic/completeness-boundary-cases.
  • Adding or removing a source citation is significant for prose/orphan-references and semantic/grounding-alignment.

When in doubt, don't ack — let the review handle it.

3. Ack insignificant pairs

Ack all insignificant pairs in one command:

commonplace-ack-gate-review --model {model-id} {note-path} {gate-id} [{gate-id} ...]

This appends a new acceptance event to the review DB so the accepted baseline matches the current note revision. It does not rely on touch or filesystem timestamps.

4. Report

Report which pairs were acked and which were left for review. The remaining stale pairs will be picked up by the next review sweep.