Estampe

Truth
Maintenance
System

Connect Notion, Jira, Confluence, Slack and Drive. Estampe surfaces what contradicts, marks what is current, and shows the full lineage of every answer. For your team, and for your agents.

Your domain. Your sources. One truth.
truth maintenance system n.
A system that records the reasons behind each belief it holds, so that when something new contradicts an old assumption, the belief can be revised instead of quietly coexisting with its replacement.
Reads across
NotionJira ConfluenceSlack Google DriveGitHub LinearSharePoint + REST
The map

Point it at one domain.
Watch it disagree with itself.

Estampe reads everything inside a single domain, maps what is actually in there, and marks every place two sources say different things. You get the map before you change anything, and before anyone has to agree on a process.

Scope: one domain, one team. Not company wide, not on day one.
214
Facts extracted
17
Contradictions
4
Touching billing
6
Sources read
Activation steps Coverage & eSIM Support macros Plan changes Proration rules Billing cycle Refund policy Cancellation ! ! !
Stamped Unverified Contradicted domain · support operations

Every flag opens onto the sources that disagree, side by side, with dates and authors. Someone who knows the answer picks one. That is a stamp, and the map goes quiet there.

Then it keeps watching. Estampe re-reads the domain on a schedule. When a document gets edited, a policy quietly changes, or someone answers differently in Slack, the conflict resurfaces on the map by itself. You find out from the map, not from a customer.
The stamp

git blame for everything your company knows.

Version history tells you what changed. It never tells you which version to believe. A stamped fact carries its reasons with it: who stamped it, when, out of which sources, what it replaced, and who to go and ask.

support operations / proration rules
Stamped
?  what happens if a customer changes plan mid cycle
They are charged pro rata from the switch date. No refund is issued for the unused portion. The new plan starts immediately, not at the next cycle.
Lineage
Stamped by M. Okada · Head of Operations
12 Mar 2026 · reconciled from 3 sources · review due Sep 2026
Help centre · Changing your plan · refund for unused days
Supersededlast edited Aug 2024, still public
Notion · Billing SOP · new plan starts next cycle
Conflictedresolved 12 Mar 2026
Slack · #ops decision thread
08 Mar 2026 · where the current rule actually came from
01

Connect

Point Estampe at what you already run. Nothing migrates, nothing moves. Your documents stay exactly where they are.

02

Reconcile

Estampe reads across sources and surfaces the disagreements. The four pages that contradict each other, and the one nobody has opened since 2024.

03

Stamp

Someone who actually knows marks the current answer. It carries their name, the date, and everything it replaced.

Onboarding

Day one is correct.
Not week six.

Onboarding is where the mess stops being abstract. A new hire spends weeks working out which of five documents is real, and usually finds out by being wrong in front of someone.

Estampe builds their path out of stamped facts only. Nothing unverified reaches a new person, and every answer they get shows who stands behind it.

How it goes now
Day 1Handed six links. Four are out of date.
Day 4Follows a runbook replaced two years ago
Wk 2Asks in Slack, gets two different answers
Wk 5Learns the real rule by breaking something
Wk 8Finally useful
With Estampe
Day 1Path assembled from stamped facts only
Day 1Every answer shows its owner and its date
Day 3Questions resolve against the stamped layer
Wk 2Useful
afterThe gaps they hit become the next stamps
// agents query the stamped layer, // not the pile underneath it const res = await estampe.ask({ q: "deploy approval policy", scope: "engineering", requireStamped: true }); answer "Two. One from the owning team…" stampedBy m.okada@ stampedAt 2026-03-12 supersedes [ 3 sources ]
For agents

Your AI is confidently
quoting a document
from 2024.

Retrieval over raw documents inherits every problem those documents have. The model picks a version, sounds certain about it, and nobody downstream can tell where the answer came from.

Estampe exposes the stamped layer over MCP and REST. An agent can refuse to answer without a stamp, and every response traces back to a person who put their name on it.

Start here

Start with one domain.
We do the first one with you.

You do not connect your company. You pick one domain, we come in and map it, and someone on your side settles what it finds. After that your team runs it without us, and we add the next domain when you want it.

domain n.
One bounded area of operational knowledge, owned by one team. Billing. Support. Deploys. Vendor onboarding. Small enough that a handful of people can say who decides, and large enough that they already disagree.
The three phases

Map it. Settle it.
Keep it settled.

Each phase ends in something you own. You can stop after any of them, and plenty of companies should stop after the first.

Fixed price, quoted before anything starts. Stop at the end of any phase.
Phase 011 to 2 weeks

Map

We connect the sources for one domain. Notion, Confluence, Jira, Slack, Drive, whatever that team actually writes in. Estampe reads all of it and returns the map: what the domain contains, and every place two sources say different things, ranked by how much the disagreement is costing you.

Nothing changes in your tools. Nobody has to adopt anything. This phase is diagnosis.

You walk away with
  • The map of one domain, yours to keep whether or not you continue
  • Every contradiction found, ranked by operational risk
  • The list of facts that exist in nobody's documentation, only in someone's head
Phase 024 to 8 weeks, one domain

Settle

We work through the flags with the people who actually know the answer, one by one, until each has been decided by someone with the standing to decide it. Every stamp carries their name, the date, and everything it replaced.

The harder half is the knowledge that was never written anywhere. We sit with the people carrying it and get it out, in structured sessions, into the same stamped form as everything else.

You walk away with
  • A settled domain, with lineage on every fact
  • Undocumented judgment written down and attributed
  • Your team trained to stamp without us
  • Everything exportable, in a format you can read without our software
Phase 03Ongoing

Maintain

The domain is now your team's to run. What resurfaces on the map goes to whoever owns that area, and settling it takes minutes because the disagreement arrives already found. Nobody has to remember to audit anything.

We keep the connections working, and we add domains when you want them. Priced per domain. Never per seat, never per question, so anyone in the company can ask.

You walk away with
  • A domain that stays true instead of decaying quietly
  • New contradictions surfaced automatically as things change
  • An API and MCP endpoint, so your own tools and agents can require a stamp

The person who maps your domain is the person who built the system. No handover, no junior team, no account manager in between.

How we work

What we commit to before you sign anything.

Fixed price, quoted up front

You get the number before any work starts. It does not move because the work turned out harder than expected.

Never billed by the hour

No timesheets, no rate card, no incentive for us to take longer than necessary.

Priced per domain

Not per seat and not per question. Once a domain is live, everyone in the company can ask it anything.

NDA before we look at anything

Signed first, then we talk about your actual documentation.

Stop at the end of any phase

The map alone is a legitimate place to finish. There is no long contract to unwind.

Your knowledge stays portable

Everything stamped can be exported in a readable format. If you leave, you keep the work.

Questions

The ones people actually ask.

Do you need access to everything we have?
No, and you should not give it to us. We scope to one domain and connect only the sources that domain lives in. That is better for your security review and it is better for the output, because contradiction detection inside a bounded area is far more precise than across an entire company.
What if our documentation is genuinely terrible?
That is the normal case and it is the reason the map is worth having. A domain with very little written down produces a different result, not a worse one. You find out fast that the knowledge lives in three people rather than in your wiki, which is a more urgent problem than anything a document could have told you.
We already have Notion and a wiki. Is this not the same thing?
A wiki stores what someone wrote. It cannot tell you which of the five pages to believe. Estampe sits over the tools you already have and answers the question they cannot: which one is current, who decided, and what did it replace.
Can we really stop after the map?
Yes, and some companies should. The map is yours to keep. If it shows your domain is in better shape than you feared, we will tell you that and you should not spend the next phase.
How is our data handled?
NDA before we look at anything. We connect read only, we scope to the domain, and we do not train anything on your content. We will go through the full detail line by line with your team before you sign.
Do we have to change the tools we use?
No. Your team keeps writing where they already write, and Estampe reads across those tools without pulling anything out of them. There is nothing to migrate and no new place anyone has to remember to check.
On the name

One block. Same sheet, every time.

Estampe is French for a print pulled from an engraved block. The block gets cut once, carefully, and every sheet after it comes out identical. That is the entire idea. Cut the truth once, then let anyone print it as many times as they need.

Name the domain.
We will map it.

Most people know which one immediately. It is the one where the same question keeps coming back, and two people keep giving different answers to it.

contact@estampe.ai