Aide Review

Use When

• A queue item reaches needs_review.
• A human asks for review of a completed or blocked queue task.
• Evidence must be checked against acceptance criteria.

Review Checklist

• Compare changed files against allowed and forbidden paths.
• Read task evidence and confirm validation commands were run.
• Check that blockers, deferrals, and review gates are explicit.
• Confirm no unsupported compatibility, support, capability, release, or parity claims were added.
• Verify generated outputs are deterministic and reviewable where applicable.
• Confirm status.yaml matches the reviewed outcome.

Outcomes

• PASS: acceptance criteria and validation are satisfied.
• PASS_WITH_NOTES: acceptable, with documented limitations or follow-up work.
• REQUEST_CHANGES: scope, evidence, validation, or policy issues must be fixed before passing.

Generated AIDE Source Summary

• Review outcomes are PASS, PASS_WITH_NOTES, or REQUEST_CHANGES unless a task defines a stricter blocker.
• Check scope, evidence, validation, source-of-truth boundaries, generated markers, and review-gate handling.
• Generated downstream artifacts must be deterministic, manifest-backed, and non-canonical.
• Q06 Compatibility, Q07 Dominium Bridge, Runtime, Hosts, and provider work remain out of Q05 review scope.

Source: Julesc013/aide — distributed by TomeVault.