Recaps & Reports

Recaps are a journal of what Trinity has accomplished on your project: each day states the events that landed on it — merges, documentation, decisions, gate outcomes — and once a day has passed, its recap stays exactly as recorded. Reports export this data as formatted PDFs.

Accessing Recaps

Click Recaps in the sidebar's Workspace section. The page has its own project picker at the top — pick which project's recaps you want to see. The picker defaults to your active project, but switching it here does not change the app-wide active project (other pages still see your original choice).

Recap Types

Trinity generates recaps at seven granularities:

Daily

What happened today — stories completed, gates resolved, issues encountered, docs written. These are the building blocks every higher-level recap aggregates.

Today's recap is updated by Trinity's post-merge hook — fire-and-forget after each story merges. The hook also handles roadmap progress updates and audit checklist re-checks in the same pass. A story can span more than one day — if it merges one day and its write-up finishes the next, each day's recap shows only what happened on that day, with a reference linking the two together.

Weekly

Aggregated from daily recaps. Shows the week's progress, patterns, and notable events.

Monthly

Aggregated from weekly recaps. Broader trends and milestone progress.

Quarterly

Aggregated from monthly recaps. Strategic-level progress and trajectory.

Yearly

Aggregated from quarterly recaps. Full-year overview.

Complete

The entire project history in one summary, built from all available recaps.

Release

Per-release summaries — what was planned, what was built, what's left across every PRD in the release. The picker lists every release for the selected project by name; pick one to see its merged stories, failed stories, checkpoints, and AI usage rolled up across all of its PRDs.

How Recaps Build

Recaps follow a hierarchical build model:

daily → weekly → monthly → quarterly → yearly → complete

Each level aggregates its children in parallel and caches the result. A story that shows up across several days (say, merged one day and documented the next) still collapses to a single entry once it's rolled up into a weekly or coarser recap.

Lazy Building

Recaps are built on demand — the first time you navigate to a period that hasn't been summarized yet, Trinity generates the recap. Subsequent visits read the cached copy instantly.

Past days are frozen once written

Once a day has closed, its recap is permanent — Trinity serves the same content every time you open it, and nothing that happens later changes it. That means resetting a story, changing your project's timezone, or a documentation write-up landing a day late never rewrites a day you've already seen. Only today's recap keeps updating live as new activity happens; a past day you're viewing for the first time is generated once, from whatever happened on it, and then stays as written.

Reading Recaps

Each recap includes:

  • Summary — narrative overview of the period
  • Stories — what was completed, failed, or is in progress. Each story line carries its difficulty badge, cycle time, a retry indicator when it took more than one attempt, and the AI spend attributed to that story (e.g. · $0.42) — the cost of every AI call the story made, rolled up from its execution events.
  • Gates — decisions made at execution gates
  • Issues — problems encountered and how they were handled
  • Docs Completed — write-ups that finished on a different day than the story they document, each pointing back to the day that story actually merged

Searching Recaps

Use the search feature to find specific information across all recaps:

  1. Navigate to Recaps
  2. Click the search icon
  3. Type your query (e.g., "authentication issues" or "what was the login bug")

Search is agentic — a micro-tier AI triages your query, reads the relevant recaps directly, and synthesizes an answer with citations back to the source recaps.

Recaps carry your story tags

A recap inherits the tags of the stories it covers, so the labels you already put on your work carry through to the summaries of it without you tagging anything twice. Agents can retrieve recaps by those tags — "pull up the recaps tagged auth", or any combination, matching all of them or any of them — which is how you ask for a period of work by subject instead of by date.

Smart Picker

The recap picker helps you find available recaps:

  • Shows which periods have recaps available
  • Filters by type (daily, weekly, monthly, etc.)
  • Navigate forward/backward through time periods

Reports

Reports export recap data as formatted PDF documents — and the same report can also be shared as a link, without exporting anything.

Accessing Reports

  1. Navigate to Recaps
  2. Click the Export Report button
  3. Choose your options
  4. Click Download — or click Share to publish the same report as a page instead

Report Types

Executive Report

High-level progress for managers and stakeholders:

  • Project status overview
  • Milestone progress
  • Key decisions and changes
  • Risk summary

Technical Report

Developer-focused with implementation details:

  • Story completion tables
  • Git activity summary
  • AI usage statistics
  • Pipeline performance metrics

Report Periods

You can generate reports for any recap period:

  • Daily, weekly, monthly, quarterly, yearly
  • The report pulls data from the corresponding recap

PDF Format

Reports are generated as A4 PDFs with:

  • Professional formatting
  • Charts and tables
  • Proper headers and footers
  • Print-ready layout

PDF rendering uses any Chromium-based browser you already have installed (Chrome, Edge, Brave, Chromium) — no setup needed for most users. If none is found, the Reports dialog shows an inline install panel that runs brew install --cask google-chrome on macOS or the right chromium package for your Linux distro. Click through the panel to stay in Trinity; once it succeeds, the Download button unlocks automatically.

Click Share in the same dialog to publish the report as a page anyone with the link can open — no download, and no Chromium install needed, since sharing never renders a PDF. Choose who the link works for (anyone with it, or only signed-in members of your workspace) and how long it stays live, then copy the link. The shared page carries the identical content the PDF does — same stats, same charts — laid out for a browser instead of a printed page, under Trinity's own header.

A share is revocable and can expire; a PDF export is neither. Unshare it, let it expire, or delete the underlying recap, and the link stops resolving immediately. Export still has its place alongside sharing: it hands whoever downloads it a permanent copy with no dependency on Trinity, while a share stays a live view you control.

Tips

  • Check daily recaps — they're the most actionable, showing exactly what happened each day
  • Use weekly for standup prep — weekly recaps are great for summarizing progress to the rest of the workspace
  • Export executive reports for stakeholders — they're designed for non-technical audiences
  • Share instead of exporting for a quick look — a link opens instantly in a browser, with no download and nothing for the recipient to install
  • Search across history — the search feature reads every day's journal directly, so it's often faster than paging through individual days