Back to 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
DecisionsRationaleInteractions
Token savings
58%

The 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.

See it work

Run it from

ClaudeCursorChatGPTAny agent · MCP

How it runs

  1. 01Copy the prompt into any agent connected to Sentra over MCP.
  2. 02The agent reads the company memory, scoped to what you are allowed to see.
  3. 03One grounded answer comes back, with every line traceable to its source.

Or automate it with Actions

The same prompt runs as a Sentra Action: on a schedule, or on a semantic trigger. Output lands in Slack or email, and every send waits for your approval.

Trigger idea: onboarding a new pm or engineer

Sentraover MCPEvery decision with its rationale, in order

Auth refactor · the decision trail

Mar 14 · token rotation over session pinning

design review · Mar 14

Chosen for the mobile SDK; pinning broke background refresh in testing.

Jun 2 · migration deferred to Q3

planning · Jun 2

Rationale: Atlas V3 launch takes precedence; running both migrations concurrently doubles rollback risk.

Aug 20 · revisited after the incident, upheld

incident review · Aug 20

The A17 regression raised the question again; the review concluded the plan stands, with the Singapore validation path added.

The prompt above becomes this. Fictional data, real mechanics: every line cites the meeting, thread, or record it came from.

Without Sentra

  1. 01Search GitHub for files in auth paths and PRs mentioning 'auth refactor'.
  2. 02Search docs (Notion, Confluence) for design docs and RFCs on the topic.
  3. 03Search Slack channels for threads tagged auth or matching the project name.
  4. 04Pull every meeting transcript that mentions auth — re-read each for decision moments.
  5. 05Manually extract each decision: statement, rationale, who led it, when it was made.
  6. 06Identify reversals by re-reading subsequent threads for changes of direction.
  7. 07Compose the chronological timeline.

~95,000 tokens

With Sentra

  1. 01Resolve 'auth refactor' as a `Value Object` — matches repo paths, doc titles, channel names, project aliases.
  2. 02Pull every `Decision` scoped to it, ordered by date.
  3. 03Each Decision returns: statement, `Rationale`, owning `Actor`, originating `Interaction` with quoted excerpts.
  4. 04Any subsequent Decision that revised or reversed it is linked via supersedes relation.
  5. 05Pull open questions Sentra detected in the last 30 days that no Decision has yet resolved.
  6. 06Compose the timeline.

~40,000 tokens

Book a DemoStart Free