Terum

Delivery

Then it reaches you, in the flow you're already in.

No new dashboard to check. Each item arrives native to its tool: a briefing in Slack, a heads-up in your editor, a decision gate in your terminal.

TerumAPP7:02 AM

☀️ Daily brief · Thursday, Jun 19

9 updates · 5 people · 🔴 2 need you · ranked by relevance to you

Good morning, Teddy. Today's through-line is your billing rewrite. Two of the team's overnight moves land directly on it. One clears your path, the other you'll have to untangle before you build further.

Beyond that, a performance fix now in review may quietly erase the report-latency problem you raised this morning. Everyone else had a heads-down shipping day.

🔴 Needs your input · 2

Two things won't resolve without you, and both are time-sensitive. Handle these before the build work.

Collision · act today

You and Ryan both rewrote refreshSession()

T Your version · uncommitted

+ retry guard on 401
+ billing flow depends on it

⚡

R Ryan's · merged to main

− no retry path
refactored for pricing

Build on main as-is and your guard disappears silently. Settle which version wins before either of you continues.

2 conversations · Cursor, Claude · high confidence · view both diffs →

The second is a direction call that's still open. Your read tips it.

Decision forming · your read by FridayMDP

SSR vs CSR for the dashboard

SSR keep

Better first-paint, but keeps the custom server.

CSR leaning

Simpler deploys, drops the server, but changes your guards.

Route-guard loading: your call
SEO on the marketing-adjacent pages

Maya · ChatGPT · 3h · 2 sources · medium confidence

Billing & pricing

The reason your billing rewrite suddenly has a clearer path: Ryan merged the pricing-page refactor overnight, consolidating the tier logic into a single module.

6 items held back below your relevance floor ↓ generated 7:02am · 14 conversations scanned

In Slack, your daily brief.

A top-down digest of everything that moved overnight, ranked by relevance, with the two things that actually need you surfaced first.

exportReport.ts · terum-app

38import { COLUMNS, toCsvRow } from './schema'

40// build the CSV export for the reports view

41export async function exportReportCsv(rows) {

42 const header = COLUMNS.join(',')

43 const body = rows.map(toCsvRow).join('\n')

44 return `${header}\n${body}`

45}

47// stream large exports instead of buffering

48export async function streamReportCsv(query, res) {

49 res.setHeader('Content-Type', 'text/csv')

50 res.write(COLUMNS.join(',') + '\n')

51 for await (const row of query.cursor()) {

52 res.write(toCsvRow(row) + '\n')

53 }

54 res.end()

55}

In your editor, a heads-up inline.

Right where you're typing: a note that the code you're writing already shipped, or quietly collides with a teammate's change.

claude · billing

❯ migrate billing storage to mongo

· reading repo · planning the migration…

⟿ terum · decision check before execution

│⚠ This action reverses a standing team decision. Read the context before proceeding.

│

│Decision in scope

│ADR-014: "Postgres for billing storage" · decided 3 days ago · owned by @marcus

│Rationale: billing needs multi-row transactions, and finance's reporting runs on SQL views. Mongo was evaluated for this exact workload and rejected.

│

│What your change touches

│• 2 services read the Postgres billing schema: invoices, dunning

│• 3 migrations and 1 finance reporting view depend on those tables

│• the planned step drops those tables, not reversible without a restore

│

│Why it's flagged, not silently blocked

│● impact · high: billing is revenue-critical; a bad migration risks dropped invoices

│● urgency · act now: the agent runs destructive migrations on the next step

│● proximity · your branch: your current task; no one else has touched it yet

│

│Reversing ADR-014 is a scope-level call. It needs @marcus's sign-off before the agent executes anything destructive.

⏸ paused: the agent will not run migrations until this is resolved

terum ·active

❯

Opus 4.8 (1M context) │ billing-migration [░░░░░░░░░░] 0% ·…

▶▶ auto mode on · 1 shell · ← for agents

In your terminal, a decision gate.

Before an agent runs something destructive, Terum pauses it against the team's standing decisions and asks for the call.

Set up in minutes.

Three steps

01Connect

Make an account and link the tools your team already uses, read-only. One click each, no data to move.

02Learn

Terum reads the signal across them and builds a typed map of how your team works: who owns what, and how it all connects.

03Magic

From there it runs itself. Every signal scored and routed to whoever it actually matters to, in the tool they're already in.

structured · typed map

01Connect

Make an account and link the tools your team already uses, read only. One click each, no data to move.

02Learn

Terum reads the signal across them and builds a typed map of how your team works: who owns what, and how it all connects.

structured · typed map

Postgres vs Dynamoresearch

Use Postgresdecision

Billing rewritein review

PR #482change

refreshSession()conflict

backs affects unblocks blocks

03Magic

From there it runs itself. Every signal scored and routed to whoever it actually matters to, in the tool they're already in.

swipe →

Capabilities

It surfaces what matters, then handles it.

Scheduling, routing, tickets, follow-ups: Terum acts across your tools so the busywork takes care of itself.

Meeting prioritization

Flags which meetings actually need you, and turns the rest into a recap.

Today · 4 meetings 2 need you

10:00Roadmap reviewyou own 2 decisionsEssential

11:30Marketing weeklynothing needs youRecap instead

1:00Vendor demoFYI onlyRecap instead

2:001:1 · Priyaopen decision pendingEssential

Conflicts & escalations

Surfaces decisions that quietly contradict each other, and escalates the calls beyond your role.

Ship dark mode in v2# ios · Mon

Dark mode pushed to v3# design · today

decisions clash

Refund policy · beyond your role D @David

Data sync across tools

One change propagates everywhere; every tool stays in lockstep.

TER-205 Status → Done

LinearTER-205 closed

Notionroadmap updated

Slackthread resolved

Auto-routing

Every update finds the right channel and the right person, on its own.

Auth session bug PR #482 # eng-billing R Ryan Cho · owns billing P Priya · looped in

Issues, filed for you

Decisions and action items become real tickets, with the details already in.

Filed by Terum

Linear

Jira

just filed

TER-205 High

Reconcile refreshSession() across billing & auth

Todo auth R Ryan

From a decision in today's standup

Briefs & follow-ups, catered

Recaps and drafts written per person, ready in the tool they live in.

Drafted for you 2 min ago

To S Sarah Chen · Sequoia

Series A: recap & next steps

Hi Sarah, great to reconnect after today's board sync. Recapping where we landed on the Series A terms and the two follow-ups on your side.

Review & send Edit

Security

Your data never leaves your control.

We never train on it. We connect read-only. And you can delete everything, anytime.

Per-user isolation

Scoped to you

Everything you capture is walled off to your account, and anything you mark private stays out of every team and shared view.

AES-256

Encrypted in transit and at rest

Every connection is TLS-encrypted, and your data is stored encrypted at rest with AES-256 — the standard banks rely on.

Read-only

Reads your signal, never alters it

Terum links to your tools to observe — it reads to build the map and never edits, moves, or deletes your files, messages, or docs.

Full control

Delete it all, anytime

Wipe a single source or your whole account in a click. Deletion is immediate — your conversations, notes, and the vectors built from them are erased.

Only what matters,
routed to you.

Scattered signal becomes a structured map.

Only what's relevant to you makes it through.

Then it reaches you, in the flow you're already in.

It plugs into where your team already works.

Set up in minutes.

It surfaces what matters, then handles it.

Meeting prioritization

Conflicts & escalations

Data sync across tools

Auto-routing

Issues, filed for you

Briefs & follow-ups, catered

Your data never leaves your control.

Scoped to you

Encrypted in transit and at rest

Reads your signal, never alters it

Delete it all, anytime

Ready to get your team in sync?

Only what matters,routed to you.

Scattered signal becomes a structured map.

Only what's relevant to you makes it through.

Then it reaches you, in the flow you're already in.

It plugs into where your team already works.

Set up in minutes.

It surfaces what matters, then handles it.

Meeting prioritization

Conflicts & escalations

Data sync across tools

Auto-routing

Issues, filed for you

Briefs & follow-ups, catered

Your data never leaves your control.

Scoped to you

Encrypted in transit and at rest

Reads your signal, never alters it

Delete it all, anytime

Ready to get your team in sync?

Only what matters,
routed to you.