How Trinity keeps your company aligned
Trinity turns commitments into tasks, follows them up, keeps trackers in step, flags drift between teams and answers with evidence.
Nobody chases, re-reports or reconciles
Quiet commitments get a follow-up in their thread, and tasks stay in step with GitHub, Linear and Jira without anyone updating them by hand.
Trinity
Thu 9:00
@Richard, ENG-158 is due today. Still on track?
PR #482 is up, merging this morning.
Settled on merge · ENG-151 unblocked
Settled
Follow-ups in the thread
When a commitment goes quiet, Trinity asks about it where it was made, at the owner's next working hour, so nobody has to chase.
ENG-158 · Sandbox access
Moved by Richard
In progress
In review
PR #482 · Stripe sandbox client
Kept in step with ENG-158
Draft
In review
#eng-payments
Task linked in the thread
Quiet
Linked
Trackers kept in step
Each task stays in step with GitHub, Linear and Jira and links back to where it was said.
When a PR merges
Post the changelog to #releases
When a task is quiet for 3 days
Ask its owner in the thread
Ran 12 times this week
Your triggers
Custom automations
Your own rules, on your own triggers, scoped to the project they run in.
Drift between teams, caught early
Drift is hard to see from inside any one team. Trinity flags duplicate work, shows any team the context behind a feature and finds the person who knows.
ENG-204 · Public API rate limiter
Atlas · Started Mon
#311 · API throttling
Platform · Started Tue
Duplicate work
Overlap flagged
Duplicate work detection
When two teams start building the same thing, Trinity flags the overlap.
Why it shipped
Origin caching · Apr 3
Stale reads surfaced in checkout. The team chose origin caching with a 60s TTL over edge caching, decided in #eng-platform.
+11read it in Sales, CS and Support
Cross-team visibility
Any team can see why a feature shipped, not just the team that built it.
Gilfoyle
#eng-payments
Who knows the billing service? Webhook retries are failing.
Monica
Owns billing · Since Apr 3
Added to thread
Relevant person finder
Trinity finds the right person from the work they have done and the code they own.
Commitments, captured where they are made
Trinity reads the channels, meetings and issues each project selects, plus coding sessions on paired machines, so the record does not depend on anyone writing it down.
Product sync
Tue 10:00 · 2 commitments in the transcript
Monica "Let's cache at origin with a 60s TTL and retire the websocket spike."
ENG-161 · Origin caching
Updated
ENG-160 · Drop websockets
Created
Meetings become tasks
Commitments made in a meeting become tasks with an owner and a date, linked to the meeting notes they came from.
Claude Code
feat/billing-migration · 41 min
› 3 files changed in billing/
› Decided: keep custom JWT until Clerk
› Follow-up: rotate the sandbox keys
Summary attached to the task
Captured
Coding sessions link to tasks
Each Claude Code, Codex or Cursor session is linked to the task it served, with its summary attached to the task.
Agent work you can trace to the ask
Claude Code, Codex and Cursor start from their task's context, write back as the person they work for and show up in usage and cost.
Session start
Atlas · Tue 9:12
Claude Code
Loading
Context ready
Codex
Loading
Context ready
3 decisions · 2 open threads · Shipped since Mon
Context in, work traced back
Each agent reads its task's context from Trinity and reports progress, blockers and pull requests under the name of the person who paired its machine.
Today · Atlas
$124.02
+3.2%
Claude Code
$71.40
Codex
$52.62
Usage, cost and machines
Token usage, cost and sessions are visible across the project, and any paired machine can be revoked.
Answers that link to their sources
Every answer links to the message, pull request, issue, doc or meeting note behind it.
Why did we drop websockets?
They caused stale reads in checkout on Apr 3. The team moved to polling with ETags, decided in #eng-platform.
#eng-platform
RFC-12ENG-160Answers with evidence
Ask what is blocked or who owns what, and the answer shows where it came from.
Apr 3 · #eng-platform
Decided: polling + ETags
over websockets, after stale reads in checkout
Today
ENG-231 · Cache invalidation
Cites it
the reasoning travels with the ticket
Decisions you can trace
Ask why something was decided, and the answer links to the message, issue or meeting behind it.
Status is a by-product, not a job
The record comes from the work itself, so the pre-standup digest and the docs stay current without anyone writing an update.
Standup digest
Tue 8:45 · Before the 9:00
2
decisions since yesterday
1
blocker, owner pinged
4
shipped since Monday
Pre-standup digest
What changed since yesterday, ready before the meeting starts.
PR #484 · Origin caching
Merged by Gilfoyle · 2 min ago
Merged
CHANGELOG.md
+ v2.4 · Origin caching, 60s TTL
v2.3 · Sign-in moves to Clerk
v2.2 · Rate limiter for the public API
Docs updated · 2 pages in Notion
Current
Docs and changelogs kept current
After a release, the docs and the changelog catch up on their own.