What Trinity does
Trinity turns decisions and commitments into tracked work, keeps it current as things change, and cites the source behind every answer.
Work is captured where it is said
Trinity reads the same channels, meetings and sessions the team does, so nothing depends on someone remembering.
Agreement brief
Before work starts
Agreed
Scope
ENG-151Cache reads at origin, 60s TTL
Changed decision
#eng-platformPolling + ETags, not websockets
Open question
To clarify
Answered
Are invoices cached too?
Scope agreed before work starts
Scope, what changed and what is still open, linked to where it was said, so nobody builds the wrong thing.
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-151 · Origin caching
Updated
ENG-160 · Drop websockets
Created
Meetings become tasks
Commitments made in a meeting become tickets, linked to the moment they were said.
Claude Code
feat/billing-migration · 41 min
› 3 files changed in billing/
› Decided: keep custom JWT until Clerk
› Follow-up: rotate the sandbox keys
Saved to project memory
Captured
Coding sessions become context
What happened in Claude Code, Codex or Cursor is on record before anyone writes it up.
Nothing waits on a status update
The plan stays in step with what actually happened, without anyone updating it.
Trinity
Thu 9:00
@Richard, ENG-158 is due today. Still on track?
Creds are in 1Password, closing it now.
Closed · ENG-151 unblocked
Resolved
Follow-ups in the thread
When a commitment goes quiet, Trinity asks about it where it was made.
ENG-158 · Stripe sandbox access
Moved by Richard
In progress
In review
PR #482 · sandbox creds
Label and reviewer set
Draft
In review
#eng-payments
Status posted in the thread
Quiet
Posted
Sync across Linear, Jira and GitHub
Change a ticket in one tool and it changes in the others.
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 #482 · 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.
Drift shows up while there is still time to steer
Noticing when work drifts is the lead's hardest job. Trinity watches for it and raises it early.
ENG-204 · Public API rate limiter
Atlas · started Mon
#311 · API throttling
Platform · started Tue
Duplicate work
Both teams told
Duplicate work detection
When two teams start the same thing, both of them hear about it.
Why it shipped
Origin caching · Apr 3
Stale reads surfaced in checkout. The team chose origin caching with a 60s TTL over the websocket spike, decided in #eng-platform.
+11read it in Sales, CS and Support
Cross-team visibility
Anyone 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
37 commits · 12 decisions in billing
Added to thread
Relevant person finder
Trinity knows who has worked on what, and brings them into the thread.
Every answer carries its receipts
Nothing Trinity says is a vibe. Every claim cites the event behind it.
why did we drop websockets?
Stale reads in checkout on Apr 3. The team chose origin caching with a 60s TTL instead, decided in #eng-platform.
#eng-platform
RFC-12TRIN-188Project memory that answers
Ask what was decided or what is blocked. The answer cites 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 that last
A decision from months ago still travels with the work it affects.
Agents start where the team left off
Agents get the project's current state before they write a line, and their usage stays visible.
Session start
Atlas · Tue 9:12
Claude Code
Loading
Context ready
Codex
Loading
Context ready
3 decisions · 2 open threads · what shipped since Mon
Agent context layer
Claude Code, Codex and Cursor start with the project's current state, not a blank slate.
Today · Atlas
$124.02
+3.2%
Claude Code
$71.40
Codex
$52.62
Usage metrics
Token usage, cost and sessions, visible across the project.
When a PR merges
Post the changelog to #releases
When a ticket 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, drawing on everything Trinity knows.
Agent Context Layer & Usage Metrics
Claude Code, Codex and Cursor start every session with the project's live context, the decisions, the open threads and what shipped, so what they build lines up with the direction. Token usage, cost and sessions stay visible across the project.