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

Generate weekly narrative summary of work and vibes #719

New Issue
Closed
opened 2026-03-21 13:57:20 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-21 13:57:20 +00:00
Collaborator
Copy Link

Description

Once per week, generate a short narrative summary (human-readable, not just metrics):

  • What changed (themes, areas of focus)
  • How agents and Timmy contributed
  • Any shifts in tests, triage, or token economy

Post this summary in the logbook and/or dashboard for quick review.

Acceptance Criteria

  • Weekly narrative is generated and easy to skim
  • Timmy can adjust or turn off the feature via config

From: Timmy Automations Backlog §7.2

Kimi context: Kimi's deep research capability is well-suited for analyzing the week's activity across repos and generating the narrative.

Migrated from perplexity/the-matrix#110

## Description Once per week, generate a short narrative summary (human-readable, not just metrics): - What changed (themes, areas of focus) - How agents and Timmy contributed - Any shifts in tests, triage, or token economy Post this summary in the logbook and/or dashboard for quick review. ## Acceptance Criteria - [ ] Weekly narrative is generated and easy to skim - [ ] Timmy can adjust or turn off the feature via config _From: Timmy Automations Backlog §7.2_ **Kimi context:** Kimi's deep research capability is well-suited for analyzing the week's activity across repos and generating the narrative. --- _Migrated from perplexity/the-matrix#110_
kimi was assigned by Timmy 2026-03-21 18:02:09 +00:00
kimi added this to the Automation Hub v1 milestone 2026-03-21 20:23:49 +00:00
kimi commented 2026-03-21 21:36:31 +00:00
Collaborator
Copy Link

PR created: #791

Implementation Summary

Created timmy_automations/daily_run/weekly_narrative.py — a weekly narrative summary generator that produces human-readable summaries of development activity.

Key Features

  • Narrative output: Markdown summary with sections for activity highlights, focus areas, agent contributions, and notable events
  • Vibe classification: Automatically categorizes the week as productive/steady/struggling/quiet
  • Dual output: Both JSON (for programmatic use) and Markdown (for human reading)
  • Configurable: Can be enabled/disabled via weekly_narrative_enabled in config or TIMMY_WEEKLY_NARRATIVE_ENABLED env var
  • Graceful degradation: Works with local data when Gitea is unavailable

Files Changed

  • timmy_automations/daily_run/weekly_narrative.py (new)
  • tests/timmy_automations/test_weekly_narrative.py (new)
  • timmy_automations/config/automations.json (added weekly_narrative entry)
  • timmy_automations/config/daily_run.json (added weekly schedule)
  • src/config.py (added weekly_narrative_enabled setting)

Testing

  • All 2737 tests pass
  • 26 new tests added for weekly narrative functionality
  • Lint and format checks clean

Usage

# Generate weekly narrative
python3 timmy_automations/daily_run/weekly_narrative.py

# Output files
.loop/weekly_narrative.json  # Structured data
.loop/weekly_narrative.md    # Human-readable summary
PR created: #791 ## Implementation Summary Created `timmy_automations/daily_run/weekly_narrative.py` — a weekly narrative summary generator that produces human-readable summaries of development activity. ### Key Features - **Narrative output**: Markdown summary with sections for activity highlights, focus areas, agent contributions, and notable events - **Vibe classification**: Automatically categorizes the week as productive/steady/struggling/quiet - **Dual output**: Both JSON (for programmatic use) and Markdown (for human reading) - **Configurable**: Can be enabled/disabled via `weekly_narrative_enabled` in config or `TIMMY_WEEKLY_NARRATIVE_ENABLED` env var - **Graceful degradation**: Works with local data when Gitea is unavailable ### Files Changed - `timmy_automations/daily_run/weekly_narrative.py` (new) - `tests/timmy_automations/test_weekly_narrative.py` (new) - `timmy_automations/config/automations.json` (added weekly_narrative entry) - `timmy_automations/config/daily_run.json` (added weekly schedule) - `src/config.py` (added weekly_narrative_enabled setting) ### Testing - All 2737 tests pass - 26 new tests added for weekly narrative functionality - Lint and format checks clean ### Usage ```bash # Generate weekly narrative python3 timmy_automations/daily_run/weekly_narrative.py # Output files .loop/weekly_narrative.json # Structured data .loop/weekly_narrative.md # Human-readable summary ```
kimi closed this issue 2026-03-21 21:36:41 +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 Automation Hub v1
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees kimi
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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