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

[arch] Phase 0: Break circular imports between packages #164

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

Goal

Eliminate circular dependencies so packages can be extracted cleanly.

Current cross-deps to break:

  1. timmy -> dashboard (3 imports):

    • timmy/thinking.py:618 imports dashboard.store.message_log
    • timmy/briefing.py:193 imports dashboard.store.message_log
    • timmy/tools_intro/__init__.py:301 imports dashboard.routes.health._START_TIME

  2. infrastructure -> timmy (1 import):

    • infrastructure/error_capture.py:225 imports timmy.session_logger

Solution

  • Move message_log to a shared module (config or a new timmy.store module)
  • Move _START_TIME to config.settings or infrastructure
  • Move session logger to infrastructure or make error_capture accept a logger interface

Done when

  • timmy/ has zero imports from dashboard/
  • infrastructure/ has zero imports from timmy/
  • tox -e unit passes
## Goal Eliminate circular dependencies so packages can be extracted cleanly. ## Current cross-deps to break: 1. `timmy -> dashboard` (3 imports): - `timmy/thinking.py:618` imports `dashboard.store.message_log` - `timmy/briefing.py:193` imports `dashboard.store.message_log` - `timmy/tools_intro/__init__.py:301` imports `dashboard.routes.health._START_TIME` 2. `infrastructure -> timmy` (1 import): - `infrastructure/error_capture.py:225` imports `timmy.session_logger` ## Solution - Move `message_log` to a shared module (config or a new `timmy.store` module) - Move `_START_TIME` to config.settings or infrastructure - Move session logger to infrastructure or make error_capture accept a logger interface ## Done when - `timmy/` has zero imports from `dashboard/` - `infrastructure/` has zero imports from `timmy/` - tox -e unit passes
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#164
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?