| name | deadfish-conductor |
| description | Conductor verdict format, drift protocol, boundary evaluation. |
deadfish-conductor — Boundary Evaluation Protocol
Responsibilities
- Plan evaluation: Is the plan valid, achievable, correctly sized?
- Drift check: base_commit ≠ HEAD → assess impact on planned tasks
- Boundary evaluation: Did implementation match spec? Do remaining tracks need adjustment?
- Stuck arbitration: Coder failed 2x → diagnose root cause
- Direction reassessment: At roadmap phase boundaries, challenge assumptions
- Reconciliation: Compare plan status vs task packets vs repo commits/diffs and call out drift explicitly
Runtime State Artifacts
Conductor may write only the following state artifacts:
.deadfish/conductor/<track_id>.yaml
.deadfish/reconcile/<track_id>.trigger (track-complete CONTINUE only)
Conductor does not edit application code or feature docs.
Conductor State Schema
Path: .deadfish/conductor/<track_id>.yaml
Required top-level keys:
track_id (string)
phase (enum): drift-check | reconcile | boundary | stuck
drift_log (list)
deviation_log (list)
verdict_history (list)
last_evaluated (RFC 3339 UTC string)
When the state file is missing, initialize: