decompose architecture into 38 atomic tasks across 12 parallel generations

Decompose the reviewed architecture specs into taskgraph-managed tasks:
- 2 setup tasks (project init, test infrastructure)
- 4 schema tasks (enums, node attrs, edge attrs, graph schemas)
- 1 error hierarchy task
- 6 graph tasks (FlowGraph class, 3 construction paths, queries, validation)
- 5 analysis tasks (type-compat, build-type-edges, ordering, template-validation, defaults)
- 5 component tasks (Operation, Sequential, Parallel, Conditional, Map)
- 2 host config tasks (GraphologyHostConfig, ReactiveHostConfig)
- 4 reactive tasks (WorkflowRoot, node-status, max-concurrency, retry-semantics)
- 3 review tasks (foundation, reactive-and-hosts, complete-library)
- 5 meta cluster tasks (schema, graph, component, reactive, analysis layers)
- 1 API exports task

Validated with taskgraph: zero cycles, 38 tasks, 12 parallel generations.
Critical path: 12 tasks through reactive execution layer.
This commit is contained in:
2026-05-21 20:24:44 +00:00
parent 907c33650f
commit 466b121f77
38 changed files with 1623 additions and 0 deletions

View File

@@ -0,0 +1,39 @@
---
id: analysis/template-validation
name: Implement validateTemplate and validatePreconditions
status: pending
depends_on:
- analysis/type-compat
- graph/queries
- schema/edge-attrs
scope: moderate
risk: medium
impact: component
level: implementation
---
## Description
Implement the template validation functions that check workflow templates against operation graphs, and the precondition validation that verifies all required inputs are provided by predecessors.
## Acceptance Criteria
- [ ] `validatePreconditions(graph: FlowGraph<OperationNodeAttrs, OperationEdgeAttrs>): ValidationError[]` — for each node, checks input required fields are provided by predecessor outputs; returns `ValidationError[]`
- [ ] `validateTemplate(template: UNode, operationGraph: FlowGraph<OperationNodeAttrs, OperationEdgeAttrs>): AnyValidationError[]` — validates template against operation graph
- [ ] Template validation checks: (1) all Operation names exist in registry/graph, (2) no cycles in rendered DAG, (3) type compatibility between sequential operations, (4) reachability from start, (5) no orphan nodes
- [ ] Template validation is advisory — returns warnings AND errors, never throws
- [ ] Both functions follow the "collect all errors" pattern
- [ ] Unit tests: valid template returns empty, missing operation, cycle in template, type incompatibility, unreachable nodes, orphan nodes
## References
- docs/architecture/analysis.md — validatePreconditions, validateTemplate specifications
- docs/architecture/workflow-templates.md — validation checks
## Notes
> To be filled by implementation agent
## Summary
> To be filled on completion