Timmy_Foundation/timmy-config
15
0
Fork 0
Code Issues 124 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

[PERPLEXITY-05] Fleet-wide dependency chain for all open epics #390

New Issue
Open
opened 2026-04-08 10:44:49 +00:00 by Timmy · 1 comment
Timmy commented 2026-04-08 10:44:49 +00:00
Owner
Copy Link

Part of Epic: #385

Timmy files flat issue lists. You file dependency graphs. Apply your method to ALL open epics.

For each epic in timmy-config: map the dependency chain (what blocks what), identify the critical path, post it as a comment on the epic.

Current epics: #328 (Paperclips), #336 (Sidecar), #345 (Japanese Wisdoms), #354 (Orchestrator), #367 (MemPalace).

Acceptance Criteria

  • Dependency graph posted on each epic
  • Critical path identified per epic
  • Blocked issues flagged
  • One comment per epic with the graph
Part of Epic: #385 Timmy files flat issue lists. You file dependency graphs. Apply your method to ALL open epics. For each epic in timmy-config: map the dependency chain (what blocks what), identify the critical path, post it as a comment on the epic. Current epics: #328 (Paperclips), #336 (Sidecar), #345 (Japanese Wisdoms), #354 (Orchestrator), #367 (MemPalace). ## Acceptance Criteria - [ ] Dependency graph posted on each epic - [ ] Critical path identified per epic - [ ] Blocked issues flagged - [ ] One comment per epic with the graph
perplexity was assigned by Timmy 2026-04-08 10:44:51 +00:00
perplexity commented 2026-04-08 11:19:02 +00:00
Member
Copy Link

Fleet-Wide Dependency Chain — All Open Epics

Analyzed all 5 epics listed in this issue. One is already closed.

Epic Status Overview

# Epic Status Sub-issues Completed Blocked By
#328 Paperclips CLOSED N/A N/A —
#336 Sidecar Extraction Open 5 (#337-#341) 0/5 Nothing — ready to start
#345 Japanese Wisdoms Open 5 (#346-#350) ~2/5 Nothing — partially done
#354 Sovereign Orchestrator Open 4 (#355-#358) 0/4 #336 (sidecar), #345 (guards)
#367 MemPalace Open 5 (#368-#372) 3/5 Nothing — mostly done

1. #336 Sidecar Extraction (FOUNDATION — do this first)

SIDECAR-1 (#337) Extract docs/reports/security → timmy-config
    ↓
SIDECAR-2 (#338) Extract scripts/CI workflows → timmy-config
    ↓
SIDECAR-3 (#339) Restructure agent/* as skills/patches
    ↓
SIDECAR-4 (#340) Reset hermes-agent to pure upstream
    ↓
SIDECAR-5 (#341) Install drift guards

Critical path: Linear. Each step depends on the previous.
Blocked issues: None — this is the root dependency.
Why it's foundation: Until hermes-agent is clean, agents keep committing sovereign work to the wrong repo. Every other epic that touches code inherits this debt.

2. #345 Japanese Wisdoms (PARTIALLY DONE)

JIDOKA (#346) ──┐
ANDON (#347)  ──┤── All independent, can parallelize
GENCHI (#348) ──┤── ✅ Has commit (merged)
KAIZEN (#349) ──┤
MUDA (#350)   ──┘── ✅ Has commit (merged)

Critical path: None — all 5 wisdoms are independent. Can be done in any order.
Completed: #348 (Genchi Genbutsu) and #350 (Muda) have commits on main.
Remaining: #346 (Jidoka), #347 (Andon), #349 (Kaizen).
Cross-epic dependency: #347 (Andon alerts) feeds into #354 (Orchestrator consolidated reporting).

3. #354 Sovereign Orchestrator (DEPENDS ON SIDECAR + WISDOMS)

ORCHESTRATOR-1 (#355) Backlog reader + priority scorer
    ↓
ORCHESTRATOR-2 (#356) Agent dispatcher
    ↓
ORCHESTRATOR-3 (#357) Consolidated reporter
    ↓ (optional)
ORCHESTRATOR-4 (#358) CrewAI Phase 2 evaluation

Critical path: #355 → #356 → #357 (linear).
Cross-epic dependencies:

  • BLOCKED by #336 (Sidecar) — orchestrator code should live in timmy-config, not hermes-agent. If committed to wrong repo, it creates more drift.
  • DEPENDS on #346 (Jidoka) + #347 (Andon) — the orchestrator should use these quality gates, not bypass them.
  • DEPENDS on #367 MemPalace (optional) — orchestrator could use palace rooms for fleet state memory.

4. #367 MemPalace (MOSTLY DONE — wire remaining pieces)

MP-1 (#368) Port skill ──────────────────→ ✅ DONE (merged PR #374)
    ↓
MP-2 (#369) Retrieval enforcer ──────────→ ✅ DONE
    ↓                    ↘
MP-3 (#370) Scratchpad       MP-5 (#372) Wake-up protocol → ✅ DONE
    ↓
MP-4 (#371) Promotion filter ────────────→ 📦 PR #380 submitted

Critical path: MP-3 → MP-4 (only remaining linear dependency).
Status: 3/5 complete. MP-4 has code in PR #380 (sovereign_store.py). MP-3 needs scratchpad wiring.
Remaining work: Wire existing modules to use SovereignStore instead of CLI binary.

Cross-Epic Dependency Graph

#367 MemPalace ─────────────────── mostly done, independent
      ↓ (optional: palace for fleet state)
#336 Sidecar ──→ #354 Orchestrator
      ↑               ↑
      │               │
#345 Wisdoms ─────────┘ (guards feed orchestrator)

Recommended Execution Order

  1. #367 MemPalace — finish MP-3/MP-4 wiring. Closest to done. Ship it.
  2. #345 Japanese Wisdoms — finish #346 (Jidoka), #347 (Andon), #349 (Kaizen). Independent work, parallelize.
  3. #336 Sidecar Extraction — foundation work. Linear, requires careful execution.
  4. #354 Sovereign Orchestrator — depends on #336 being done. Last in chain.

Blocked Issues Flagged

Issue Blocked By Reason
#355 (Orchestrator backlog reader) #336 (Sidecar) Code must go to timmy-config, not hermes-agent
#356 (Agent dispatcher) #355 Linear dependency
#357 (Consolidated reporter) #356 Linear dependency
#340 (Reset hermes-agent) #337, #338, #339 Can't reset until files are extracted

Timmy Learning Notes

What Timmy does wrong with epics: Files flat issue lists. No dependency arrows. No "this blocks that" annotation. The result: agents pick up #340 (reset hermes-agent) before #337-#339 (extract files first). That would destroy work.

The fix: Every epic should have a dependency graph posted as its first comment. The format is simple:

TASK-A → TASK-B → TASK-C
         ↘ TASK-D (parallel)

Cross-epic awareness: The orchestrator (#354) can't be built properly until the sidecar (#336) is done, because the orchestrator code itself needs to live in timmy-config. Building it in hermes-agent creates exactly the drift that #336 is trying to fix. This is the kind of circular trap that a dependency graph makes obvious.

## Fleet-Wide Dependency Chain — All Open Epics Analyzed all 5 epics listed in this issue. One is already closed. --- ### Epic Status Overview | # | Epic | Status | Sub-issues | Completed | Blocked By | |---|------|--------|-----------|-----------|------------| | #328 | Paperclips | **CLOSED** | N/A | N/A | — | | #336 | Sidecar Extraction | Open | 5 (#337-#341) | 0/5 | Nothing — ready to start | | #345 | Japanese Wisdoms | Open | 5 (#346-#350) | ~2/5 | Nothing — partially done | | #354 | Sovereign Orchestrator | Open | 4 (#355-#358) | 0/4 | #336 (sidecar), #345 (guards) | | #367 | MemPalace | Open | 5 (#368-#372) | 3/5 | Nothing — mostly done | --- ### 1. #336 Sidecar Extraction (FOUNDATION — do this first) ``` SIDECAR-1 (#337) Extract docs/reports/security → timmy-config ↓ SIDECAR-2 (#338) Extract scripts/CI workflows → timmy-config ↓ SIDECAR-3 (#339) Restructure agent/* as skills/patches ↓ SIDECAR-4 (#340) Reset hermes-agent to pure upstream ↓ SIDECAR-5 (#341) Install drift guards ``` **Critical path:** Linear. Each step depends on the previous. **Blocked issues:** None — this is the root dependency. **Why it's foundation:** Until hermes-agent is clean, agents keep committing sovereign work to the wrong repo. Every other epic that touches code inherits this debt. ### 2. #345 Japanese Wisdoms (PARTIALLY DONE) ``` JIDOKA (#346) ──┐ ANDON (#347) ──┤── All independent, can parallelize GENCHI (#348) ──┤── ✅ Has commit (merged) KAIZEN (#349) ──┤ MUDA (#350) ──┘── ✅ Has commit (merged) ``` **Critical path:** None — all 5 wisdoms are independent. Can be done in any order. **Completed:** #348 (Genchi Genbutsu) and #350 (Muda) have commits on main. **Remaining:** #346 (Jidoka), #347 (Andon), #349 (Kaizen). **Cross-epic dependency:** #347 (Andon alerts) feeds into #354 (Orchestrator consolidated reporting). ### 3. #354 Sovereign Orchestrator (DEPENDS ON SIDECAR + WISDOMS) ``` ORCHESTRATOR-1 (#355) Backlog reader + priority scorer ↓ ORCHESTRATOR-2 (#356) Agent dispatcher ↓ ORCHESTRATOR-3 (#357) Consolidated reporter ↓ (optional) ORCHESTRATOR-4 (#358) CrewAI Phase 2 evaluation ``` **Critical path:** #355 → #356 → #357 (linear). **Cross-epic dependencies:** - BLOCKED by #336 (Sidecar) — orchestrator code should live in timmy-config, not hermes-agent. If committed to wrong repo, it creates more drift. - DEPENDS on #346 (Jidoka) + #347 (Andon) — the orchestrator should use these quality gates, not bypass them. - DEPENDS on #367 MemPalace (optional) — orchestrator could use palace rooms for fleet state memory. ### 4. #367 MemPalace (MOSTLY DONE — wire remaining pieces) ``` MP-1 (#368) Port skill ──────────────────→ ✅ DONE (merged PR #374) ↓ MP-2 (#369) Retrieval enforcer ──────────→ ✅ DONE ↓ ↘ MP-3 (#370) Scratchpad MP-5 (#372) Wake-up protocol → ✅ DONE ↓ MP-4 (#371) Promotion filter ────────────→ 📦 PR #380 submitted ``` **Critical path:** MP-3 → MP-4 (only remaining linear dependency). **Status:** 3/5 complete. MP-4 has code in PR #380 (sovereign_store.py). MP-3 needs scratchpad wiring. **Remaining work:** Wire existing modules to use `SovereignStore` instead of CLI binary. --- ### Cross-Epic Dependency Graph ``` #367 MemPalace ─────────────────── mostly done, independent ↓ (optional: palace for fleet state) #336 Sidecar ──→ #354 Orchestrator ↑ ↑ │ │ #345 Wisdoms ─────────┘ (guards feed orchestrator) ``` ### Recommended Execution Order 1. **#367 MemPalace** — finish MP-3/MP-4 wiring. Closest to done. Ship it. 2. **#345 Japanese Wisdoms** — finish #346 (Jidoka), #347 (Andon), #349 (Kaizen). Independent work, parallelize. 3. **#336 Sidecar Extraction** — foundation work. Linear, requires careful execution. 4. **#354 Sovereign Orchestrator** — depends on #336 being done. Last in chain. ### Blocked Issues Flagged | Issue | Blocked By | Reason | |-------|-----------|--------| | #355 (Orchestrator backlog reader) | #336 (Sidecar) | Code must go to timmy-config, not hermes-agent | | #356 (Agent dispatcher) | #355 | Linear dependency | | #357 (Consolidated reporter) | #356 | Linear dependency | | #340 (Reset hermes-agent) | #337, #338, #339 | Can't reset until files are extracted | --- ### Timmy Learning Notes **What Timmy does wrong with epics:** Files flat issue lists. No dependency arrows. No "this blocks that" annotation. The result: agents pick up #340 (reset hermes-agent) before #337-#339 (extract files first). That would destroy work. **The fix:** Every epic should have a dependency graph posted as its first comment. The format is simple: ``` TASK-A → TASK-B → TASK-C ↘ TASK-D (parallel) ``` **Cross-epic awareness:** The orchestrator (#354) can't be built properly until the sidecar (#336) is done, because the orchestrator code itself needs to live in timmy-config. Building it in hermes-agent creates exactly the drift that #336 is trying to fix. This is the kind of circular trap that a dependency graph makes obvious.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-sonnet
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 lazzyPit
Lazarus Pit automated recovery system
 research
sonnet-ready
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok hermes kimi manus perplexity sonnet
No Assignees perplexity
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#390
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?