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

Implement Daily Run orchestration script (10-minute ritual) #703

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

Description

Under timmy_automations/, implement a script that:

  • Connects to local Gitea
  • Fetches "Daily Run candidate" issues using labels, e.g.:
    • daily-run
    • size:XS, size:S
    • Optional layer:* labels
  • Produces a short agenda for approximately 10 minutes:
    • Up to 3 items with issue number, title, layer, and suggested action type

Also include a "review mode" that summarizes the last 24 hours:

  • Issues/PRs touched
  • Items closed or merged
  • Tests that failed or flaked (if information is available)

Use a config file under timmy_automations/config/ for label names, number of items, and lookback window.

Acceptance Criteria

  • Script runs locally and prints a concise Daily Run agenda plus a simple day summary
  • Behavior is configurable via a file (no code edits needed for basic tuning)
  • Usage is documented in timmy_automations/README.md

From: Timmy Automations Backlog §2.1

Migrated from perplexity/the-matrix#94

## Description Under `timmy_automations/`, implement a script that: - Connects to local Gitea - Fetches "Daily Run candidate" issues using labels, e.g.: - `daily-run` - `size:XS`, `size:S` - Optional `layer:*` labels - Produces a short agenda for approximately 10 minutes: - Up to 3 items with issue number, title, layer, and suggested action type Also include a "review mode" that summarizes the last 24 hours: - Issues/PRs touched - Items closed or merged - Tests that failed or flaked (if information is available) Use a config file under `timmy_automations/config/` for label names, number of items, and lookback window. ## Acceptance Criteria - [ ] Script runs locally and prints a concise Daily Run agenda plus a simple day summary - [ ] Behavior is configurable via a file (no code edits needed for basic tuning) - [ ] Usage is documented in `timmy_automations/README.md` _From: Timmy Automations Backlog §2.1_ --- _Migrated from perplexity/the-matrix#94_
kimi was assigned by Timmy 2026-03-21 18:02:16 +00:00
kimi commented 2026-03-21 19:24:26 +00:00
Collaborator
Copy Link

PR created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/783

Summary

Implemented the Daily Run orchestration script (10-minute ritual) under timmy_automations/daily_run/.

Key Features

  • Agenda generation: Fetches candidate issues by labels (daily-run, size:XS/S), scores and prioritizes them, outputs up to 3 items
  • Review mode (--review): Summarizes last 24h — issues touched, closed, PRs merged, test failures
  • Configurable: All settings in timmy_automations/config/daily_run.json (labels, item count, lookback window)
  • Multiple output formats: Human-readable (default) and JSON (--json)
  • Graceful degradation: Handles Gitea unavailability

Usage

python3 timmy_automations/daily_run/orchestrator.py          # Basic agenda
python3 timmy_automations/daily_run/orchestrator.py --review # With day summary

Files Changed

  • timmy_automations/daily_run/orchestrator.py (new)
  • timmy_automations/config/daily_run.json (config section added)
  • timmy_automations/config/automations.json (manifest entry added)
  • timmy_automations/daily_run/README.md (documentation)
  • timmy_automations/README.md (cross-reference)

All tests pass (2650 passed, 1 skipped).

PR created: http://143.198.27.163:3000/rockachopa/Timmy-time-dashboard/pulls/783 ## Summary Implemented the Daily Run orchestration script (10-minute ritual) under `timmy_automations/daily_run/`. ### Key Features - **Agenda generation**: Fetches candidate issues by labels (`daily-run`, `size:XS/S`), scores and prioritizes them, outputs up to 3 items - **Review mode** (`--review`): Summarizes last 24h — issues touched, closed, PRs merged, test failures - **Configurable**: All settings in `timmy_automations/config/daily_run.json` (labels, item count, lookback window) - **Multiple output formats**: Human-readable (default) and JSON (`--json`) - **Graceful degradation**: Handles Gitea unavailability ### Usage ```bash python3 timmy_automations/daily_run/orchestrator.py # Basic agenda python3 timmy_automations/daily_run/orchestrator.py --review # With day summary ``` ### Files Changed - `timmy_automations/daily_run/orchestrator.py` (new) - `timmy_automations/config/daily_run.json` (config section added) - `timmy_automations/config/automations.json` (manifest entry added) - `timmy_automations/daily_run/README.md` (documentation) - `timmy_automations/README.md` (cross-reference) All tests pass (2650 passed, 1 skipped).
Timmy closed this issue 2026-03-21 19:24:43 +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
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#703
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?