Company knowledge
in every session.
Permission-aware. Measured.
Frazer Knowledge maps your code and your company: repositories, pull requests, issues, runbooks, incidents, docs and threads. Every answer cites its sources, follows each person’s permissions in the source, and is evaluated before any change ships.
frazer knowledge create --preset engineeringCreate the new endpoint secret at the payments provider, store it as PAYMENTS_WEBHOOK_SECRET in the payments secret store, and deploy with both secrets accepted for one hour1. Remove the old secret after the dashboard shows no failed deliveries2. Payments on-call approves the production step3.
- 1runbooks/payments-webhooks.md · acme-payments@mainGitHub
- 2Payments handbook › SecretsNotion
- 3Thread in #payments-oncallSlack
It reads code like an engineer.
And the company like a colleague.
Code is split by symbol, a pull request stays together with its review threads, a Slack thread is one document, tables are never cut in half. Runbooks and incidents come straight from the Frazer catalog.
Same question, different people,
the answer each of them may see.
Rotate at the payments provider, store as PAYMENTS_WEBHOOK_SECRET, accept both for an hour, remove the old one when deliveries are clean.
runbook · handbook · #payments-oncallThe public docs explain webhook signatures. The rotation steps are in documents you can’t open; ask the payments team.
public docs · no private sources usedAlready connected
when you open the box.
Admins tick a knowledge base in the provisioning profile. Every box in scope gets it in every tool, with a short-lived token for that person. Nothing to install, no keys to paste.
# provisioningProfiles/acme-baseline@v12
items:
- kind: knowledge
ref: knowledgeBases/acme-engineering
enforcement: locked
- kind: knowledge
ref: knowledgeBases/acme-company
enforcement: default
- kind: mcp
ref: frazer
enforcement: lockedHybrid search, reranking,
and the courage to say “I don’t know”.
Every change is tested
before anyone sees it.
Each base has a golden set drafted from its sources and reviewed by a person, a permissions set run as test identities, and graded feedback from real use. A new index is built next to the live one and switches only if the gate passes.
| Gate rule (default) | Threshold |
|---|---|
| No metric drops more than 2 points | −2 pts |
| Faithfulness | ≥ 0.85 |
| Citation validity | ≥ 0.95 |
| Decline correctness | ≥ 0.80 |
| Permission leaks | = 0 |
| p95 retrieval latency | +20 % max |
Thresholds are the defaults each base starts with. Every run reports the new index against the live one.
Your servers, your vectors.
Connectors, the query service and the vector engine run in your organization’s data cluster, on your servers or the Frazer fleet. One organization’s vectors never share an engine with another’s; text and vectors are encrypted at rest; query logs keep ids and scores, not text.