Give your agent the judgment your codebase can't.

The decisions, the precedents, the lines your team doesn't cross.

Distilled from your Slack, runbooks, PRs, wiki, served via MCP before the diff is written.

$

// onboarding design‑partner teams before GA

—Every codebase has a second document. It lives in a senior engineer's mind.

Those rules need to ship before the diff.

slack#eng-help11:42 am
nd
newdev11:42 am

hey maya, im about to modify update-profile. anything i should know before i touch it?

m
maya12:14 pm· 32 min later

yeah, three things —

  • ·do not raise the retry cap. budget is 2, hard. (PR #4812)
  • ·do not add jitter — breaks the downstream cache key.
  • ·do ping @platform-auth before you ship.

// three why-nots Maya carries in her head.

// none of them are in the code.

mcpcursor → ardelio.context198ms · 3 sources
{
  "finding":  "update-profile: retry cap hard-set at 2; jitter breaks downstream cache key; ping @platform-auth before shipping",
  "evidence": [
    { src: "pr:#4812 · review thread"},
    { src: "runbook/auth.md · §retry-budget"},
    { src: "slack:#eng-help · 3w ago"}
  ],
  "owner":  "@platform-auth",
  "cost":   0.14 // usd
}

// synthesised from 3 sources. attributed in the prompt.

// not memory. consequence.