Renames
a cross-encoder carries one lineage id from version N to N+1.
Muniment archives every version your AI assistant publishes
Your bot platform keeps twenty versions and deletes the rest, so the date legal names is the one that is gone. We copy every version out the day it ships, into your own bucket, dated and hash-chained. Name a date and paste an answer from a transcript, and our models find the node version that produced it or say unresolved.
No card. Revision history supplied on request.
20
user-created versions retained before the oldest is auto-deleted
$1,450
per connected assistant, per month
3 in 10
node versions a model links after a rename
Who it fits
Go count your surviving versions before you read the rest.
Open your busiest assistant's version list and find the oldest one left. Your evidence starts on that date.
This is for you if
- ✓You publish weekly, and your oldest version postdates your oldest open matter.
- ✓One past-date question already cost two weeks in Jira and Slack.
- ✓Your counsel would take a stated absence over a likely reconstruction.
This is not for you if
- ✕Under twenty versions published. Nothing is deleted yet; export them yourself.
- ✕Your platform has no definition export, so there is nothing to pull.
- ✕Your compliance office wants a BAA from every vendor. We hold no PHI and sign none.
Figures
The cap runs out long before the complaint arrives.
- 0120versions Kore.ai keeps; the twenty-first deletes the oldest
- 025 monthshow long twenty last at one publish a week
- 0310 weekshow long they last at two
- 049-18 monthswhen complaints about a version arrive
Installation
What the rules settle on their own, and what stops for a person.
The last two steps fork on the resolver's confidence.
Steps 01–03
- 01Connecta read-only credential, and Object Lock in compliance mode on your bucket
- 02Captureeach publish pulls the definition into Parquet and JSON, hashed and chained
- 03Aska timestamp, the pasted answer and a matter reference
Steps 04–05
- 04Above 0.90the evidence pack comes back on its own
- 05Below 0.90unresolved, until a named reviewer on your side decides
what you get
What comes back when you name a date and paste an answer
One evidence pack, dated and hash-chained, out of a bucket you own.
pack · matter 2026-114
- asked about
- 14 March 2026, 09:41 UTC
- node version
- billing_dispute_v4, published 2 March 2026
- resolver score
- 0.94, above the 0.90 floor
- export
- parquet and json, 2.3 MB, pulled at publish
- object lock
- compliance mode, 7 years, your bucket
- sha-256
- 9f2c41ab7e05d38c6b1f04a927e5cb83d1c7fa6029b45e18
- chain
- manifest links the publish before it, unbroken to first capture
A drawn example, not a customer record. The hash and the chain are what a reviewer checks; the rest is what they read.
Components
A renamed node keeps its history, and a pasted answer finds the version that wrote it.
Exact ids and strings link about seven node versions in ten; renames and pasted answers go to models on our Ohio GPUs.
The resolver
names the node version that produced a pasted answer.
Under 0.90
a person you name confirms or corrects the link.
Training
each decision tunes your account's models only, without the pasted answer.
Scope
Read-only on your platform, write-once in your bucket.
What's in scope
- 01Every publish, captured. Plus whatever versions survive at connection.
- 02Parquet and JSON in your bucket. valid_from and valid_to on every row.
- 03Evidence packs at any volume. Anyone can run the verification script against your bucket.
What we don't do
- 01No restore. Kore.ai's own Restore option does that job better than an outside archive.
- 02No transcripts, recordings or member records. We see configuration only.
- 03No testing or linting. We record what you published and never score it.
Questions
Ahead of your security review.
Does this replace Kore.ai?
No. We read through a read-only credential and refuse one with write scope.
Can you recover versions already deleted?
No. What the cap removed before you connect is gone.
Do you warrant a match?
No. Every match shows its confidence score.
Does Kore.ai's Trust Center list HIPAA or HITRUST?
No. It lists SOC 2 Type 2, PCI DSS and ISO/IEC 27001:2022, among others.
What does Muniment hold?
No SOC 2 or ISO 27001 yet; security reviewers get our subprocessor register.
Where is pasted text read?
Only on our own GPUs in Ohio. Models are trained on Azure in Virginia.
Rates
$1,450per connected assistant, per month.
One flat rate per assistant. No seat count, no session meter, no volume table.
- Capture on every publish, and backfill of whatever versions survive
- Resolver queries and evidence packs, at any volume a matter needs
- Reviewers, auditor accounts and read-only users, none of them counted
- The published schema and the verification script, under an open license
Request drawings
- Month to month for the first six months, on 30 days' notice
- If you leave, the Parquet, raw exports and manifests are already in your bucket
Run the count first. Then send us the number.
A work email and a company name. Ask for a walkthrough or a first capture.
We reply within one business day.
- ✓ The first capture and coverage report are free, before any contract
- ✓ The report dates each assistant's earliest surviving version, where your archive can start
- ✓ If that date predates every open matter, we will leave you alone