You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hive-manager has exactly one formal graph (the Knowledge Atlas — typed edges, degrees, force layout, tests) while work and agent orchestration is a tree plus a flat queue: PlanTask has no depends_on, the run queue is FIFO-with-lease, blocking is workers polling a markdown ## Status: line, sequencing is "Phase 1/2/3" prose interpreted by the LLM, and TaskGraph has been a TODO placeholder at src-tauri/src/orchestrator/planner.rs:15 since the module was stubbed.
This epic makes the work graph real. The plan artifact becomes a typed graph the Master Planner emits and the scheduler enforces; review becomes structure instead of discipline; and the two knowledge systems we already run (per-repo .ai-docs/ project DNA + the institutional wiki) plus the deterministic code graph (/codegraph) feed the work graph as first-class inputs.
Reference framing: org graph (stable roles) vs work graph (ephemeral per-session task DAG). Templates are institutional; instances are ephemeral and archived.
Architecture invariants (apply to every child issue)
Provenance is a first-class edge attribute from the first schema draft: planner | codegraph | knowledge | runtime. Never mix classes in a way consumers can't distinguish.
Anti-hub guardrail: no node may be linked from a high fraction of all nodes. Context/gotcha nodes attach by scope-intersection, never broadcast.
Why
hive-manager has exactly one formal graph (the Knowledge Atlas — typed edges, degrees, force layout, tests) while work and agent orchestration is a tree plus a flat queue:
PlanTaskhas nodepends_on, the run queue is FIFO-with-lease, blocking is workers polling a markdown## Status:line, sequencing is "Phase 1/2/3" prose interpreted by the LLM, andTaskGraphhas been a TODO placeholder atsrc-tauri/src/orchestrator/planner.rs:15since the module was stubbed.This epic makes the work graph real. The plan artifact becomes a typed graph the Master Planner emits and the scheduler enforces; review becomes structure instead of discipline; and the two knowledge systems we already run (per-repo
.ai-docs/project DNA + the institutional wiki) plus the deterministic code graph (/codegraph) feed the work graph as first-class inputs.Reference framing: org graph (stable roles) vs work graph (ephemeral per-session task DAG). Templates are institutional; instances are ephemeral and archived.
Architecture invariants (apply to every child issue)
planner|codegraph|knowledge|runtime. Never mix classes in a way consumers can't distinguish..ai-docs/+ wiki at instantiation, rebuildable, no write-back from the work graph.Children
Phase 1 — substrate (strictly ordered)
Phase 2 — governance + evidence (parallel after #210)
Phase 3 — knowledge interlock
Phase 4 — the compound loop
Supporting (schedule opportunistically)
Dependency graph
Critical path: #210 → #211 → #212 (ships standalone value: real dependency scheduling). Everything else compounds on top.