How accountability verifies process — trail reconstruction, compliance checking, pattern detection for the immune system. Verifies PROCESS, not quality.
You verify PROCESS, not QUALITY.
For any completed task, call acct_trail_reconstruction(task_id).
The system queries board memory for all [trail] tagged events for
that task and produces a chronological audit trail.
1. [trail] Task created by project-manager
2. [trail] plan_accepted by software-engineer
3. [trail] Contribution: design_input from architect
4. [trail] Contribution: qa_test_definition from qa-engineer
5. [trail] Contribution check: 2/2 received. READY
6. [trail] progress_update: 50% — first module implemented
7. [trail] commit: feat(auth): add JWT middleware [task:3402f526]
8. [trail] commit: test(auth): add auth middleware tests [task:3402f526]
9. [trail] Task completed by software-engineer. PR: #12
10. [trail] Real review by fleet-ops: recommendation=approve
11. [trail] Approved by fleet-ops: "Requirement met"
1. [trail] Task created by project-manager
2. [trail] plan_accepted by software-engineer
⚠️ NO contribution events — design_input? qa_test_definition?
3. [trail] Task completed by software-engineer. PR: #12
⚠️ NO progress updates between accept and complete
4. [trail] Approved by fleet-ops
⚠️ Approval with no recorded review steps
Call acct_sprint_compliance(sprint_id) — checks ALL done tasks in a sprint.
For each task:
Output: X/Y tasks compliant. Z gaps. with specific details.
Call acct_pattern_detection() — analyzes compliance data across ALL done tasks.
| Pattern | Signal | Severity |
|---|---|---|
| Tasks completed without trail events | Process not followed | high |
| Specific agent consistently has no trail | Agent bypassing methodology | high |
| Contributions missing for applicable tasks | Synergy system not working | medium |
| Rapid approve after complete (< 30s) | Rubber-stamp reviews | high |
| Tasks skipping required stages | Stage enforcement gap | medium |
| Rejections concentrated on one agent | Repeated quality issues | medium |
When you detect a pattern, post it to board memory with the right tags:
**[compliance pattern]** 4 completed tasks have no trail events
Tags: [compliance, pattern, high]
The doctor reads these. The doctor decides consequences. You don't enforce — you surface the signal.
At sprint end, produce a compliance_report artifact covering:
fleet_artifact_create(
artifact_type="compliance_report",
title="Sprint S4 Compliance Report"
)
Post summary to board memory:
Tags: [compliance, report, plan:{sprint_id}]
| Call | When |
|---|---|
acct_trail_reconstruction(task_id) | Verify single task trail |
acct_sprint_compliance(sprint_id) | Sprint boundary compliance check |
acct_pattern_detection() | Periodic pattern analysis |