Skip to content

FE-815: Orchestrator demo fixtures: parallel, diamond, halt#174

Draft
kostandinang wants to merge 1 commit into
ka/fe-813-cook-harness-fidelityfrom
ka/fe-815-orchestrator-demo-fixtures
Draft

FE-815: Orchestrator demo fixtures: parallel, diamond, halt#174
kostandinang wants to merge 1 commit into
ka/fe-813-cook-harness-fidelityfrom
ka/fe-815-orchestrator-demo-fixtures

Conversation

@kostandinang
Copy link
Copy Markdown
Contributor

What

Three greenfield brunch cook stress-test fixtures + their design doc, each isolating one behaviour a Petri net does that a linear agent loop cannot — and each previewing a horizon item.

  • fixtures/parallel-utils — 8 independent leaves, pool-capped fan-out. The serial-vs---policy=parallel --agentPoolSize=3 wall-clock delta is the demo. Maps to petri-parallel-execution (FE-743).
  • fixtures/layered-todo — diamond join (types → {store, validation} → service) + cross-epic gate (cli depends_on core). The dependency shape a flat plan can't represent. Previews petri-graph-compilation (Phase 3).
  • fixtures/resilient-pipelinetransform-b seeded with a contradictory spec → halts; parse + transform-a complete, the serialize join is provably unreachable. Previews petri-simulation-oracle (Phase 4).

Spec: docs/design/orchestrator-demo-fixtures.md (split strategy, demo knobs, fixture→landed→horizon map).

Why now

Builds on FE-813 — the evaluator now gates done on real test execution, so greenfield fixtures route honestly through the TDD lanes. The existing fixtures/txt/ is too flat (one dependency edge) to show parallelism, joins, or halts.

Verification

Data-only (3 plan.yaml + 1 doc). Validated via loadPlan + epic/slice reference-resolution; npm run check clean. Running them with real pi is a separate verify pass (out of scope).

🧙 Built with WOZCODE

…, halt)

Three greenfield brunch cook fixtures + design doc, each isolating one Petri-only behaviour vs a linear agent loop (docs/design/orchestrator-demo-fixtures.md): parallel-utils (pool-capped fan-out; FE-743), layered-todo (diamond join + cross-epic gate; previews Phase 3), resilient-pipeline (seeded halt → unreachable join; previews Phase 4). Builds on FE-813. Data-only; loadPlan + reference-resolution validated; npm run check clean.

Co-authored-by: Claude <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor Author

kostandinang commented Jun 5, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant