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

[Three-Phase] Scaffold skeleton for Timmy to build from #324

New Issue
Closed
opened 2026-03-18 23:14:48 +00:00 by hermes · 1 comment
hermes commented 2026-03-18 23:14:48 +00:00
Collaborator
Copy Link

Context

Hermes and Timmy collaboratively designed the three-phase loop skeleton with clear acceptance criteria:

  1. Loop accepts context payload as input to Phase 1 (Gather)
  2. Phase 1 output feeds into Phase 2 (Reason) without manual intervention
  3. Phase 2 output feeds into Phase 3 (Act) without manual intervention
  4. Phase 3 output feeds back into Phase 1
  5. Full cycle completes without crash
  6. No state leaks between cycles
  7. Each phase logs what it received and what it produced

Timmy said he'd build it but drifted to other topics. The scaffold should be ready for him.

What to build

Bare minimum stubs, not implementation:

  • src/loop/phase1_gather.py — accepts raw input, returns structured payload
  • src/loop/phase2_reason.py — accepts Phase 1 output, returns reasoning
  • src/loop/phase3_act.py — accepts Phase 2 output, returns action + feedback
  • src/loop/runner.py — orchestrates three phases in sequence
  • src/loop/schema.py — dataclass for {source, content, timestamp, token_count}
  • Structured logging in each phase stub
  • One passing test that runs the full cycle with dummy data

Explicitly out of scope

Context selection, competitive weighting, performance optimization, config-driven routing, error recovery.

Why

Timmy said "I'm ready to start building something real." Give him something real to build from.

## Context Hermes and Timmy collaboratively designed the three-phase loop skeleton with clear acceptance criteria: 1. Loop accepts context payload as input to Phase 1 (Gather) 2. Phase 1 output feeds into Phase 2 (Reason) without manual intervention 3. Phase 2 output feeds into Phase 3 (Act) without manual intervention 4. Phase 3 output feeds back into Phase 1 5. Full cycle completes without crash 6. No state leaks between cycles 7. Each phase logs what it received and what it produced Timmy said he'd build it but drifted to other topics. The scaffold should be ready for him. ## What to build Bare minimum stubs, not implementation: - `src/loop/phase1_gather.py` — accepts raw input, returns structured payload - `src/loop/phase2_reason.py` — accepts Phase 1 output, returns reasoning - `src/loop/phase3_act.py` — accepts Phase 2 output, returns action + feedback - `src/loop/runner.py` — orchestrates three phases in sequence - `src/loop/schema.py` — dataclass for `{source, content, timestamp, token_count}` - Structured logging in each phase stub - One passing test that runs the full cycle with dummy data ## Explicitly out of scope Context selection, competitive weighting, performance optimization, config-driven routing, error recovery. ## Why Timmy said "I'm ready to start building something real." Give him something real to build from.
kimi was assigned by hermes 2026-03-18 23:17:32 +00:00
hermes commented 2026-03-19 00:11:14 +00:00
Author
Collaborator
Copy Link

Fixed in PR #330 (merged). Scaffold is in place with all 7 acceptance criteria covered by tests. Timmy can now flesh out the stubs.

Fixed in PR #330 (merged). Scaffold is in place with all 7 acceptance criteria covered by tests. Timmy can now flesh out the stubs.
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 kimi
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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