Never re-decide something your team already settled.
AI Oracle surfaces past decisions, supporting context, conflicting calls, and the threads behind them — right where you're writing.
Free during early access. Sign in with email.
Q3 platform plan
Looking at how the platform has grown, we should standardize all new internal services on gRPC for service-to-service calls. REST gets retired for internal APIs after Q3.
Migration plan — drafting
Your draft contradicts Dana's Q2 decision — internal services were standardized on REST.
# D-142 scope: platform stance: required ## Decision Internal APIs use REST + JSON…
Maya's API guide explicitly backs uniform service-to-service protocol — same direction as your draft.
# D-203 scope: platform stance: recommend ## Style guide Pick one protocol and apply it…
Maya wrote a 4-min explainer in Sept covering exactly the tradeoffs your draft is weighing.
# N-018 author: maya category: business ## gRPC vs REST tradeoffs — when latency matters…
Your team discussed this in Q2 — see the prior conclusions before re-opening the question.
thread://platform-strategy/T1Q2-2025 12 messages · last reply 2025-06-14…
Your team already did the work. It just can't find it.
The decision was made. The note exists. The explainer was written. And six months later, in a different doc, a different person solves the same problem from scratch — because nothing connected them.
Four ways of knowing what you already know.
Every check classifies what it finds — so you act on what matters, not whatever was nearby.
Glean gives you ten links. AI Oracle tells you which one matters and why.
“Your draft contradicts a decision Dana ratified in Q2 2025.”
“Maya's style guide explicitly backs the approach you're proposing.”
“Maya already wrote a 4-minute explainer covering exactly this.”
“Your team discussed this in Q2 — see the prior conclusions.”
Three steps. You stay in your work.
Bring what you have
Decisions, notes, prior docs, ADRs, Slack snippets. Type, paste, import, or capture from the extension. Empty corpus is fine — it builds as you work.
- The product
Invoke the check
From the extension, the app, or the web. Conflict, support, education, history — typed so you know what to do. Never runs in the background.
You stay the one who decides
Nothing gets ratified on its own. Review what surfaced. Keep what helps; ignore what doesn't.
you invokewe don't watch
No passive monitoring. No typing-pause watcher. Nothing in your work surfaces unless you ask for it.
We meet you where you write.
Live in the surfaces your team already uses. Paste-in works for everything else.
Start free. Pay when it pays for itself.
Per-seat on Team and Business — no minimums. A team of one is a real team.
Free
Try it. See if it catches something useful.
- Up to 50 decisions + notes
- Pasted-text check
- Extension on Google Docs
- Activity log of your work
Pro
For the solo operator who wants the whole product.
- Unlimited decisions + notes
- All four surfacing modes
- Docs, Sheets, Slides
- Personal history + CSV export
Team
For 1+ people who share decisions.
- Everything in Pro, per seat
- Org-shared corpus
- Team memory tier
- Slack bot (when shipped)
- Team activity log
Business
For teams with a compliance hat to wear.
- Everything in Team
- Policy rule authoring
- Compliance audit trail
- CSV export, SSO (Google today, SAML next)
- Priority support
Regulated, on-prem, or 100+ seats — let's build it together.
No credit card to start. Cancel anytime. Existing $10/mo Pro subscribers grandfathered through 2027-05-24.
You're in control. Always.
Four concrete commitments — defensible, verifiable, and architectural, not aspirational.
Your draft text is evaluated against your corpus and discarded. We never persist it, and the LLMs we call have zero-retention contracts on our usage.
You invoke; we don't watch
Every check runs because you asked. No passive monitoring, no typing-pause watcher, no always-listening. Nothing in your work surfaces unless you call for it.
We don't store your prompts
The text you check is evaluated and the matches returned — your draft is not persisted server-side beyond the duration of the request.
Zero-retention LLM contracts
The LLMs we call have published zero-retention policies for our usage. Your decisions, notes, and drafts are not training data — ours or anyone's.
Nothing is promoted without you
AI Oracle proposes, surfaces, and flags. It never ratifies a decision or marks anything binding on its own. Every state change is an explicit human accept.
More detail at /security — data flow, vendor list, retention.