Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

[arch] Phase 5: Clean timmy-core as the agent package #169

New Issue
Closed
opened 2026-03-15 15:37:46 +00:00 by hermes · 2 comments
hermes commented 2026-03-15 15:37:46 +00:00
Collaborator
Copy Link

Goal

After extracting spark, config, infra, and dashboard, what remains is the core agent.

What stays in timmy-core

  • src/timmy/ — agent, tools, memory, thinking, session, voice_loop
  • src/integrations/ — chat bridges (or these move to dashboard)
  • src/timmy_serve/ — the lightweight serving layer

Dependencies after extraction

  • timmy-core depends on: timmy-config, timmy-infra
  • timmy-dashboard depends on: timmy-core, timmy-config, timmy-infra
  • timmy-spark depends on: timmy-config, timmy-infra (via event bus)

Dependency graph (clean)

timmy-config (shared settings)
     |
timmy-infra (router, events, models)
   /    \
timmy-core   timmy-spark
   |
timmy-dashboard

Done when

  • Clean dependency graph, no cycles
  • Each repo has its own CI
  • Adding a new agent capability = updating timmy-core
  • Adding a new UI feature = updating timmy-dashboard
  • Kimi can work on any single repo without scanning the others
## Goal After extracting spark, config, infra, and dashboard, what remains is the core agent. ## What stays in timmy-core - src/timmy/ — agent, tools, memory, thinking, session, voice_loop - src/integrations/ — chat bridges (or these move to dashboard) - src/timmy_serve/ — the lightweight serving layer ## Dependencies after extraction - timmy-core depends on: timmy-config, timmy-infra - timmy-dashboard depends on: timmy-core, timmy-config, timmy-infra - timmy-spark depends on: timmy-config, timmy-infra (via event bus) ## Dependency graph (clean) ``` timmy-config (shared settings) | timmy-infra (router, events, models) / \ timmy-core timmy-spark | timmy-dashboard ``` ## Done when - Clean dependency graph, no cycles - Each repo has its own CI - Adding a new agent capability = updating timmy-core - Adding a new UI feature = updating timmy-dashboard - Kimi can work on any single repo without scanning the others
hermes commented 2026-03-19 01:03:12 +00:00
Author
Collaborator
Copy Link

[Deep Triage 2026-03-18] Closing: Superseded by 2026-03-15 architecture pivot. See #165.

[Deep Triage 2026-03-18] Closing: Superseded by 2026-03-15 architecture pivot. See #165.
hermes commented 2026-03-19 01:03:27 +00:00
Author
Collaborator
Copy Link

[Deep Triage 2026-03-18] Superseded by 2026-03-15 architecture pivot. Timmy moved to Claude Code substrate. Monorepo extraction plan no longer applies.

[Deep Triage 2026-03-18] Superseded by 2026-03-15 architecture pivot. Timmy moved to Claude Code substrate. Monorepo extraction plan no longer applies.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#169
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?