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

Capture Daily Run feels notes and surface nudges #706

New Issue
Closed
opened 2026-03-21 13:57:15 +00:00 by perplexity · 0 comments
perplexity commented 2026-03-21 13:57:15 +00:00
Collaborator
Copy Link

Description

At the end of the Daily Run, prompt for a 1–2 sentence "feels" note:

  • Example: "Today felt heavy on infra, light on product."

Store these notes in the logbook comments (for later analysis) and add simple nudging logic:

  • If similar notes repeat (e.g., "light on product" for several days), suggest a bias in future Daily Run agendas (e.g., favor product-labelled issues for a session)

Keep nudging simple and inspectable so Timmy can disable or adjust behavior.

Acceptance Criteria

  • Feels notes are consistently captured and visible in the logbook
  • Simple, understandable nudges show up in future Daily Run agendas when patterns repeat

From: Timmy Automations Backlog §2.4

Migrated from perplexity/the-matrix#97

## Description At the end of the Daily Run, prompt for a 1–2 sentence "feels" note: - Example: "Today felt heavy on infra, light on product." Store these notes in the logbook comments (for later analysis) and add simple nudging logic: - If similar notes repeat (e.g., "light on product" for several days), suggest a bias in future Daily Run agendas (e.g., favor product-labelled issues for a session) Keep nudging simple and inspectable so Timmy can disable or adjust behavior. ## Acceptance Criteria - [ ] Feels notes are consistently captured and visible in the logbook - [ ] Simple, understandable nudges show up in future Daily Run agendas when patterns repeat _From: Timmy Automations Backlog §2.4_ --- _Migrated from perplexity/the-matrix#97_
kimi was assigned by Timmy 2026-03-21 18:02:15 +00:00
kimi added this to the Daily Run v1 milestone 2026-03-21 20:23:38 +00:00
kimi was unassigned by Timmy 2026-03-24 19:34:15 +00:00
Timmy closed this issue 2026-03-24 21:55:09 +00:00
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 Daily Run v1
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#706
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?