Dependency Map: Work Charts & Builder
1. Critical Path Dependencies
| Dependency | Type | Impact |
|---|---|---|
| Workflow Engine | Hard | API must be 100% stable before UI can connect. The Engine orchestrates the workflow logic. |
| Skill Registry | Hard | Contains the nodes. No registry, no capabilities to drag onto the visual canvas. |
| Confidence Scorer | Hard | Builder sets thresholds, Engine enforces them during execution. |
| Schema Jobs | Hard | Builder saves JSONB templates to work_chart_definitions and reads from work_chart_executions. |
| Triggers Integration | Soft | Core gap. Workchart requires triggers (workchart_triggers) to automate runs via CRON or Events. |
Questions
Which dependency in the workflow and process mgt map represents the highest systemic risk — and is there a path to eliminating it?
- If the most critical dependency failed, which capabilities would cascade and which could operate independently?
- Are any dependencies in this map bidirectional — and does that create circular risk that should be decomposed?
- Which dependency was added because of a constraint that no longer exists?