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

[arch] Phase 4: Extract dashboard/ into timmy-dashboard repo #168

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

The dashboard is a FastAPI web application. It should be deployable independently.

Current state

  • 5,067 lines, 32 files
  • Dependencies: config, dashboard, infrastructure, integrations, spark, timmy, timmy_serve
  • Heaviest cross-dependency — imports from everything
  • Contains: routes, templates, middleware, store, static assets

Steps (after Phases 0-3)

  1. Create hermes/timmy-dashboard repo
  2. Move src/dashboard/ + templates + static assets
  3. Dashboard depends on: timmy-config, timmy-infra, timmy (as API client)
  4. Define API boundaries — dashboard talks to timmy via HTTP/events, not direct imports
  5. Move integrations that are dashboard-specific (telegram routes, discord routes) here

Done when

  • Dashboard is its own deployable app
  • Communicates with timmy agent via defined API, not direct imports
  • Has its own CI pipeline
## Goal The dashboard is a FastAPI web application. It should be deployable independently. ## Current state - 5,067 lines, 32 files - Dependencies: config, dashboard, infrastructure, integrations, spark, timmy, timmy_serve - Heaviest cross-dependency — imports from everything - Contains: routes, templates, middleware, store, static assets ## Steps (after Phases 0-3) 1. Create `hermes/timmy-dashboard` repo 2. Move src/dashboard/ + templates + static assets 3. Dashboard depends on: timmy-config, timmy-infra, timmy (as API client) 4. Define API boundaries — dashboard talks to timmy via HTTP/events, not direct imports 5. Move integrations that are dashboard-specific (telegram routes, discord routes) here ## Done when - Dashboard is its own deployable app - Communicates with timmy agent via defined API, not direct imports - Has its own CI pipeline
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#168
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?