Use cases
Product

What did we decide about the auth refactor?

Every Decision and the Rationale behind it, in chronological order, with citations.

Best for
Onboarding a new PM or engineer
Primitives
  • Decisions
  • Rationale
  • Interactions
Side by side

Token Usage, with and without Sentra

~55k tokens saved58% less work for the agent

Without Sentra
~95k tokens
With Sentra
~40k tokens
Claude (without Sentra)
  1. Search GitHub for files in auth paths and PRs mentioning 'auth refactor'.
  2. Search docs (Notion, Confluence) for design docs and RFCs on the topic.
  3. Search Slack channels for threads tagged auth or matching the project name.
  4. Pull every meeting transcript that mentions auth — re-read each for decision moments.
  5. Manually extract each decision: statement, rationale, who led it, when it was made.
  6. Identify reversals by re-reading subsequent threads for changes of direction.
  7. Compose the chronological timeline.
~95k tokens
Claude + Sentra
  1. Resolve 'auth refactor' as a Value Object — matches repo paths, doc titles, channel names, project aliases.
  2. Pull every Decision scoped to it, ordered by date.
  3. Each Decision returns: statement, Rationale, owning Actor, originating Interaction with quoted excerpts.
  4. Any subsequent Decision that revised or reversed it is linked via supersedes relation.
  5. Pull open questions Sentra detected in the last 30 days that no Decision has yet resolved.
  6. Compose the timeline.
~40k tokens
Agent prompt
You are reconstructing the decision history of the auth refactor.

Using Sentra:

1. Resolve "auth refactor" as a Value Object — match against project names, code paths, doc titles, and channel names Sentra has indexed.
2. Pull every Decision Sentra extracted that is scoped to this Value Object, ordered by date.
3. For each Decision, return: the Decision statement, the Rationale, the Actor who made or led it, the Interaction it was made in (with quoted excerpts), and any subsequent Decision that revised or reversed it.

Output:

- A chronological timeline, one row per Decision, with citations.
- A short "current state" paragraph: what is decided, what is open, what was reversed and why.
- Three named open questions Sentra detected in the last 30 days that no Decision has yet resolved.
More from Product
Quarterly roadmap reviews79% fewer tokens

Top customer pain themes this quarter

What customers complained about most, clustered and quoted — not your support ticket categories.

Cross-team architecture reviews75% fewer tokens

Where are two teams making conflicting decisions?

Two Decisions, overlapping scope, opposite polarity — caught before they ship.

Sentralize your company.

Remember what matters.

Book a demoSign up
Preferences

Subprocessors include Amazon Web Services, GitHub, Slack, Google Cloud Platform, and OpenAI.

© 2026 Dynamis Labs Inc. All rights reserved.