[BRIEFINGS] Official morning report automation — browser open + Telegram + evidence-rich overnight digest #87

Closed
opened 2026-03-29 00:18:37 +00:00 by Timmy · 2 comments
Owner

Goal:
Make Alexander's morning report an official, durable Timmy automation that matters in practice, not as a one-off Gitea issue.

What the report must do:

  • open a beautiful morning report in the browser automatically on the Mac
  • cover the most interesting overnight local activity (system, repos, agent work, local model/runtime state)
  • include relevant research/frontier updates that matter to Alexander's actual priorities
  • send rich markdown to Telegram group "Timmy Time"
  • save durable local artifacts (markdown + HTML)
  • include evidence excerpts / links, not unsupported claims

Architecture constraints:

  • prefer existing integrated channels over bespoke new systems
  • reuse the existing good_morning_report / orchestration lane where sensible
  • keep Nexus thin; do NOT turn the-nexus into a briefing UI project
  • respect the anti-falsework / anti-builder posture

Acceptance criteria:

  • one official automation path exists and is documented
  • report saved under a stable local path (for example ~/.timmy/briefings/good-morning/)
  • browser auto-opens the latest HTML report on schedule
  • Telegram receives a readable markdown version on the same run
  • content includes overnight local state + pertinent research + Gitea pulse
  • evidence snippets or links are included for every major claim
  • if a source is unavailable, the report says so honestly instead of faking coverage

Nice-to-have:

  • latest report can be linked from a thin Nexus status/pointer surface later, without growing a heavy UI inside the-nexus
Goal: Make Alexander's morning report an official, durable Timmy automation that matters in practice, not as a one-off Gitea issue. What the report must do: - open a beautiful morning report in the browser automatically on the Mac - cover the most interesting overnight local activity (system, repos, agent work, local model/runtime state) - include relevant research/frontier updates that matter to Alexander's actual priorities - send rich markdown to Telegram group "Timmy Time" - save durable local artifacts (markdown + HTML) - include evidence excerpts / links, not unsupported claims Architecture constraints: - prefer existing integrated channels over bespoke new systems - reuse the existing `good_morning_report` / orchestration lane where sensible - keep Nexus thin; do NOT turn `the-nexus` into a briefing UI project - respect the anti-falsework / anti-builder posture Acceptance criteria: - one official automation path exists and is documented - report saved under a stable local path (for example `~/.timmy/briefings/good-morning/`) - browser auto-opens the latest HTML report on schedule - Telegram receives a readable markdown version on the same run - content includes overnight local state + pertinent research + Gitea pulse - evidence snippets or links are included for every major claim - if a source is unavailable, the report says so honestly instead of faking coverage Nice-to-have: - latest report can be linked from a thin Nexus status/pointer surface later, without growing a heavy UI inside `the-nexus`
Timmy self-assigned this 2026-03-29 00:19:29 +00:00
Author
Owner

Automation triage update:

Official scheduled job established:

  • Cron job: 4dd2432bded0
  • Name: Official Good Morning Report
  • Schedule: 0 7 * * *
  • Delivery: Telegram group Timmy Time (-1003664764329)

Current job contract:

  • gather overnight local pulse + pertinent research/frontier movement
  • save markdown + beautiful HTML under ~/.timmy/briefings/good-morning/
  • open latest.html in the browser on the Mac
  • deliver the polished markdown report to Telegram

This job is the live operational lane now; this issue remains the durable system-tracking front for hardening / integrating it cleanly into timmy-config.

Automation triage update: Official scheduled job established: - Cron job: `4dd2432bded0` - Name: `Official Good Morning Report` - Schedule: `0 7 * * *` - Delivery: Telegram group `Timmy Time` (`-1003664764329`) Current job contract: - gather overnight local pulse + pertinent research/frontier movement - save markdown + beautiful HTML under `~/.timmy/briefings/good-morning/` - open `latest.html` in the browser on the Mac - deliver the polished markdown report to Telegram This job is the live operational lane now; this issue remains the durable system-tracking front for hardening / integrating it cleanly into timmy-config.
Author
Owner

Done. Ezra morning report cron is live (job a74d3cb199f5, daily 4am EST). Posts to Gitea automatically.

Done. Ezra morning report cron is live (job a74d3cb199f5, daily 4am EST). Posts to Gitea automatically.
Timmy closed this issue 2026-03-30 16:49:48 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#87