feat: Ship the adversarial migration workflow

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

dries/ocman#326

dries commented

2026-07-13 19:46:15 +02:00

Owner

Parent

#311

What to build

Ship and demonstrate a reusable Bun-style migration workflow that discovers work once, maps stable items through implementation and two independent adversarial reviews, joins findings, fixes issues, validates output, and commits through a serialized coordinator.

Acceptance criteria

A source-controlled example/preset defines shared guidance and a discovery command that emits stable JSON work items.
Map runs one pinned per-item subworkflow for each discovered unit.
The implementer receives only declared guidance/item inputs and produces a diff artifact.
Two reviewer agents run in parallel and receive only the diff plus review policy.
Join aggregates both structured review outputs for the fixer.
A bounded review/fix repeat policy can require another review round.
Validation commands gate success and commit; agent claims alone cannot bypass them.
Work uses bounded shards/path leases and serialized commit capacity without destructive Git interference.
A second fixture demonstrates capturing compile/test diagnostics once and mapping partitions without rerunning discovery per agent.
A fixture-backed end-to-end test executes at least two items through the complete graph using fake/controlled executors.
The run UI makes phase, item, review, validation, resource, workspace, and artifact state understandable.
User documentation explains authoring, running, safety, permissions, troubleshooting, and adapting the template.
Architecture diagrams and terminology documentation reflect the completed workflow system.

Blocked by

## Parent #311 ## What to build Ship and demonstrate a reusable Bun-style migration workflow that discovers work once, maps stable items through implementation and two independent adversarial reviews, joins findings, fixes issues, validates output, and commits through a serialized coordinator. ## Acceptance criteria - [ ] A source-controlled example/preset defines shared guidance and a discovery command that emits stable JSON work items. - [ ] Map runs one pinned per-item subworkflow for each discovered unit. - [ ] The implementer receives only declared guidance/item inputs and produces a diff artifact. - [ ] Two reviewer agents run in parallel and receive only the diff plus review policy. - [ ] Join aggregates both structured review outputs for the fixer. - [ ] A bounded review/fix repeat policy can require another review round. - [ ] Validation commands gate success and commit; agent claims alone cannot bypass them. - [ ] Work uses bounded shards/path leases and serialized commit capacity without destructive Git interference. - [ ] A second fixture demonstrates capturing compile/test diagnostics once and mapping partitions without rerunning discovery per agent. - [ ] A fixture-backed end-to-end test executes at least two items through the complete graph using fake/controlled executors. - [ ] The run UI makes phase, item, review, validation, resource, workspace, and artifact state understandable. - [ ] User documentation explains authoring, running, safety, permissions, troubleshooting, and adapting the template. - [ ] Architecture diagrams and terminology documentation reflect the completed workflow system. ## Blocked by - #316 - #317 - #318 - #319 - #320 - #321 - #324

dries added the

label

dries closed this issue

2026-07-16 00:56:10 +02:00

Rows
Columns

feat: Ship the adversarial migration workflow #326

Parent

What to build

Acceptance criteria

Blocked by