1.8 KiB
1.8 KiB
id, name, status, depends_on, scope, risk, impact, level
| id | name | status | depends_on | scope | risk | impact | level | |
|---|---|---|---|---|---|---|---|---|
| graph/construction-operation | Implement operation graph construction (fromSpecs, addOperation, addTypedEdge) | completed |
|
moderate | medium | phase | implementation |
Description
Implement the construction methods specific to operation graphs: FlowGraph.fromSpecs(), addOperation(), and addTypedEdge(). These build the static type-compatibility graph from OperationSpec arrays.
Acceptance Criteria
FlowGraph.fromSpecs(specs: OperationSpec[]): OperationGraph— creates nodes for each operation (key:${namespace}.${name}), adds type-compatibility edges viabuildTypeEdges(), throwsCycleErrorif resulting graph has cyclesaddOperation(spec: OperationSpec): void— adds operation node, key is${spec.namespace}.${spec.name}, throwsDuplicateNodeErrorif key existsaddTypedEdge(source, target, attrs: { compatible, detail?, mismatches? }): void— adds edge withedgeType: "typed", validates endpoints exist, validates no cycle createdfromSpecs()callsbuildTypeEdges()internally after adding all operation nodesbuildTypeEdges()must be callable separately for incremental construction afteraddOperation()- Operation graph is conventionally immutable after
fromSpecs()— documented in JSDoc - Unit tests: fromSpecs with valid specs, duplicate operations, cycle detection, incremental addOperation + buildTypeEdges
References
- docs/architecture/operation-graph.md — fromSpecs construction, incremental construction, immutability
- docs/architecture/flowgraph-api.md — fromSpecs, addOperation, addTypedEdge signatures
Notes
To be filled by implementation agent
Summary
To be filled on completion