Define outcome-sized delivery rules

[capituwuistgoonsquad]

Outcome

Make complete, demonstrable capabilities and roadmap acceptance criteria the default unit of delivery for future agents.

Rules added

• Define the outcome and acceptance criteria before implementation.
• Keep related schema, backend, frontend, tests, and documentation in one reviewable PR when they share a rollback boundary.
• Split only for an independently useful result or a documented risk, evidence, repair, or external-dependency boundary.
• Aim for one to three meaningful commits and avoid file-by-file or cosmetic churn.
• Use targeted tests while iterating, one full relevant validation before push, and full scraper runs only when they prove the outcome.
• Report progress in usable capabilities and completed acceptance criteria rather than activity counts.

Scope

Only the authoritative root AGENTS.md changes. The nested frontend agent file remains focused on its Next.js compatibility warning. This standalone governance PR is intentional because the maintainer explicitly requested that the rules be established before project work continues.

Validation

• git diff --check
• Commit includes DCO sign-off
• No runtime tests required for an agent-documentation-only change

Greptile Summary

The update adds outcome-sized delivery guidance to AGENTS.md, covering acceptance criteria, cohesive rollback boundaries, meaningful commit organization, focused and complete validation, scraper-run discipline, release proof, and capability-oriented progress reporting.

The updated guidance was checked for Markdown structure and for the new delivery, acceptance, validation, release, and scraper-safety requirements. The changed document passed those checks, and the diff contains no whitespace errors.

Confidence Score: 5/5

Safe to merge: no defects were found in the documentation-only change.

The changed guidance passed a deterministic before-and-after contract check, Python compilation of that check, and Git whitespace validation.

Files Needing Attention: No files need additional attention.

T-Rex Logs

What T-Rex did

• • Ran the AGENTS guidance validator before the PR; it exited 1 because the base document lacked the newly added delivery, release, and scraper-operation requirements.
• • Ran the AGENTS guidance validator after the PR; it exited 0 with PASS (after): markdown structure, delivery, acceptance, validation, release, and scraper safety contract are coherent.
• • Ran Python compile and git diff checks; the compile step and the whitespace diff check exited 0, confirming the validation script is syntactically valid and the documentation diff has no whitespace errors.
• • Uploaded artifacts: the deterministic AGENTS guidance validator and governance contract logs before/after the PR.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "Define outcome-sized delivery rules" | Re-trigger Greptile}