glm-5.1
466b121f77
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.
1.6 KiB
1.6 KiB
id, name, status, depends_on, scope, risk, impact, level
| id | name | status | depends_on | scope | risk | impact | level | ||
|---|---|---|---|---|---|---|---|---|---|
| analysis/build-type-edges | Implement buildTypeEdges — populate operation graph with type-compatibility edges | pending |
|
narrow | medium | component | implementation |
Description
Implement buildTypeEdges() which iterates over all operation pairs in the graph and adds type-compatibility edges based on typeCompat() results. Called internally by fromSpecs() and callable manually for incremental construction.
Acceptance Criteria
buildTypeEdges(graph: FlowGraph<OperationNodeAttrs, OperationEdgeAttrs>): void— standalone function insrc/analysis/type-compat.ts- For each pair (A, B): call
typeCompat(A.outputSchema, B.inputSchema), add edge with result - Compatible edges:
edgeType: "typed", compatible: true, detail: "A.output → B.input" - Incompatible edges:
edgeType: "typed", compatible: false, detail describing mismatch, mismatches array - Unknown compatibility (either schema is Unknown): no edge added
- O(n²) in worst case — documented, acceptable for 10-200 operations
- Function is callable after incremental
addOperation()calls - Unit tests: known operation specs produce expected edges, incompatible pairs get compatible: false edges, unknown schemas produce no edges
References
- docs/architecture/analysis.md — buildTypeEdges specification
- docs/architecture/operation-graph.md — edge construction, compatible: false edges rationale
Notes
To be filled by implementation agent
Summary
To be filled on completion