Daily Work Summary Workflow

End-of-day synthesis records what Kevin actually shipped, learned, reviewed, and left open across repos and agent sessions.

The daily-work-summary automation closes the loop on forward-deployed work at Dedalus Labs and related repos. It summarizes evidence, not vibes. Source: automations/daily-work-summary.md, 2026-05-31

Routing

Use this workflow for a personal daily closeout. Use Project Briefing Workflow when Kevin needs a project or repo briefing with broader team context. Use Code Bugfix Workflow when the output should include actual fixes.

Trigger

• End-of-day daily automation.
• Manual request such as "summarize today" or "what did I ship today?"
• Before weekly review, especially when several agent sessions touched the same repo.

Inputs

• Git: git log --author="Kevin" --since=midnight, team context log
• GitHub: PRs authored, reviews given (gh pr list)
• Agent transcripts from today's Cursor sessions
• Active branches and stash list
• User-visible artifacts: screenshots, docs, deployed URLs, incident notes, or PR links when present

Runbook

1. Establish the local day boundary in Kevin's timezone.
2. Gather commits, PRs, reviews, branches, and relevant transcript entries.
3. Group work by outcome rather than by command chronology.
4. Separate shipped work, reviewed work, debugging/learning, open loops, and follow-ups.
5. Promote only durable decisions, postmortems, or patterns to their topic pages.
6. Append a concise operation entry to wiki/log.md when the summary itself is user-visible or when durable wiki pages changed.

Output Shape

• What shipped today: concrete outputs, PR links, commits, docs, deploys, or fixes.
• What changed in the system: decisions, config changes, wiki updates, skills, automations, routing.
• What Kevin learned: bugs, root causes, durable patterns, risks.
• Open loops: branches, failed checks, pending reviews, follow-ups, user decisions.

Keep claims evidence-backed. If a source is unavailable, state the gap.

Wiki Promotion

Most daily summaries belong in the output artifact and log. Create or update topic pages only when the day produced durable knowledge: an incident, decision, new workflow, skill rule, architecture constraint, recurring pattern, or important career/content state.

Validation

A completed run names the repos and transcript sources inspected. If it appends to wiki/log.md, it must use the dated operation format from Index Logging Protocol. It should not fabricate productivity from empty git history. Some days are no-op days. History survives this indignity.

Run Contract

This workflow follows Workflow Run Contract: name the sources, write output or no-op proof, promote only durable facts, update state only when the run really completed, refresh generated surfaces when durable pages or skills change, and log user-visible work.

---

Timeline

• 2026-07-01 | Rebuilt as an evidence-backed daily closeout contract with routing, trigger, runbook, output shape, promotion rules, and log discipline. Source: User request, 2026-07-01
• 2026-05-31 | Workflow page created from daily-work-summary automation. Source: automations/daily-work-summary.md, 2026-05-31