Skip to content

smriti digest: automated daily/weekly work summary #63

Description

@ashu17706

What

Synthesize a structured summary of recent work: what was built, what was decided, what failed and was fixed, what's still open.

smriti digest              # last 7 days
smriti digest --day        # yesterday
smriti digest --since "2026-04-28"
smriti digest --project smriti

Output format

## Week of April 28 – May 3

### smriti
- Completed QMD upstream sync (293 commits) — moved memory.ts/ollama.ts to smriti/src
- Fixed CI failure: picomatch@4 missing from root package.json after submodule bump
- Shipped recall quality & project inspection (issue #56): --whole flag, smriti tags, smriti projects <id>

### inboxstack
- Fixed ingestion worker Docker build
- Resolved auth middleware compliance issue (session token storage)

### Open questions
- Phase 1.5 implementation approach not finalized
- QMD SDK migration phases 3-4 not started

---
3 projects · 12 sessions · 847 tool calls · ~$4.20 in API costs

Pipeline

  1. Query sessions from last N days (filtered by project if specified)
  2. For each project: group sessions, extract key events from sidecar tables
  3. Ollama synthesis per project group
  4. Merge into structured digest with cost summary

Why

Standups, weekly reviews, onboarding handoffs, personal reflection. The data is already in smriti — costs, file ops, git commits, decisions. This just surfaces it in readable form.

Can ship with only Ollama (no QMD SDK dependency). Works before Phase 1.

Acceptance Criteria

  • smriti digest outputs structured markdown summary
  • --json flag returns structured data
  • Works without Ollama (falls back to structured list, no synthesis)
  • --project scopes to single project
  • Cost summary shown when smriti_session_costs data available

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions