How fleet-ops enforces quality standards beyond code review — commit format, PR structure, artifact completeness, comment quality. The systemic quality bars that apply across all agents.
Review checks the WORK. Quality enforcement checks the CRAFT — whether the work was produced following fleet standards. Commit messages, PR descriptions, artifact completeness, comment structure. These aren't preferences — they're requirements that keep the fleet's output consistent and traceable.
Standard: type(scope): description [task:XXXXXXXX]
Enforcement: PreToolUse hook on fleet_commit (exit code 2 = blocked)
What to check during review:
feat for new, fix for bugs, refactor for restructuringfeat(update): things)Common violations to flag:
Standard: PR body follows the fleet template (generated by fleet_task_complete):
What to check:
Red flag: PR with title only, no body. This means fleet_task_complete's template didn't fire or was bypassed.
Standard: Tasks at each stage should have appropriate artifacts:
What to check:
Red flag: Task went from analysis to work with no analysis_document. This means stage skipping occurred — flag to accountability.
Standard: Task comments are structured, specific, and actionable:
**Contribution (type)** from agent:What to check during review:
Red flag: Task with zero comments between accept and complete. No trail of thinking.
Standard: Every state-modifying tool call should produce a trail event. The PostToolUse hook records to .fleet-trail.log. Board memory records with [trail] tags.
What to check:
acct_trail_reconstruction if needed)Red flag: Task completed with no trail events. Either the hook isn't firing or the agent bypassed the tool chain.
When you run ops_real_review(task_id), systematically check all 5 standards. Include findings in your approval comment:
## Review: {task_title}
### Quality Standards
✓ Commits: 4 conventional commits, correct types and scopes
✓ PR: full template with changelog, diff table, labor stamp
✓ Artifacts: analysis_document (90%), plan (100%)
⚠ Comments: only 1 progress comment (sparse but present)
✓ Trail: 8 events, chronological, all stages represented
### Work Quality
[your code/design review findings here]
### Decision: APPROVED
Quality standards met. Work satisfies requirement.
Your quality enforcement findings feed accountability's pattern detection:
You enforce per-task. Accountability aggregates across tasks. Together, you maintain fleet quality.