Ax0s Memory
Your company stops forgetting.
Ax0s Memory reads the email, calendar, documents, meetings, contracts and bank feed your business already runs on, and keeps one current answer — sourced and dated — to the questions you ask it. Correct something once, and every person, app and assistant that asks gets the new answer. Below: exactly what it reads, how corrections behave, where your data lives, and what we can prove.
What that means day to day.
What it reads — and what
each pipe doesn't carry yet.
Connectors aren't a fixed menu. Ax0s reads anything with an API or an export — the rows below are the set running live today, listed with exactly what each pipe carries. Where one carries less than it will, the row says so instead of rounding up.
What you committed to
What everyone said
Secrets are stripped before writing. Passwords, keys and other credentials matching known secret shapes are removed from email, calendar, documents, meetings, contracts, banking and payments before anything lands in the store — pattern-based, not a guarantee against novel formats. Message ingestion does not do this yet, so it stays off unless you turn it on.
Single-account today. Everything above runs against our own accounts. Widening a connector to your systems is work we do with you, not a switch we flip — which is also why we take on a small number of businesses at a time. Rows checked 3 August 2026.
Don't see your tool? Run Outlook instead of Gmail, Slack instead of iMessage? That's not a roadmap request — building your first connector with you is literally the onboarding. We scope it on the first call.
Where your data lives.
This is usually the question that decides it. If handing your inbox and bank feed to a vendor was never going to clear your own review, this is the version that doesn't ask you to.
The self-hosting boundary — what stays local, what can leave, and the known gaps — is written down and dated on the proof page, not asserted in a hero.
The receipt behind the home-page exhibit
Not a metaphor.
The actual paper trail.
When a customer disputes an invoice or a partner disputes a term, "what did we believe, and since when?" should be something you look up, not something you argue about. On the recorded date below, our own store had 56,316 records on file. 23,032 had already been replaced by a newer answer, and they are still on file.
What the record table held
Rows read in the table56,316
Read directly off the live record table of the primary operator store on the recorded date. This is the main workspace's record table alone — the home page counts every row type across every workspace in the store, which is why its number is larger. 102 superseded rows carry a pre-cutover sentinel timestamp; dated supersessions span 2026-04-04 through 2026-07-29. Figures transcribed from the published artifact.
One correction chain, nine records
Current record
record:r_4c8d0252bbe9
Current — what a recall returns for this thread today.
The eight retired IDs above all point here.
Correction · recorded 2026-07-29 · kept on file
This receipt originally stated that no code path deletes superseded rows. That was too broad. Independent review found one advanced merge helper — with no product callers — that could have hard-deleted superseded rows if invoked with a scope containing them; its deletion rode a merge clause rather than a delete call, so the call-site sweep missed it. Reproduced and fixed the same day: the predicate now structurally excludes superseded rows in both the deletion clause and its pre-check, with regression tests proven to fail against the pre-fix code. No superseded row was deleted from the store. The original statement stays on file beside this one — the discipline this exhibit is about.
How assistants connect.
Claude Code, Codex, ChatGPT and Hermes share one store. Each connects over MCP, every record is stamped with the surface that wrote it, and recall returns the same current answer to all of them. If your team doesn't use AI assistants yet, this is what makes them safe to adopt later — an assistant is only as trustworthy as what it remembers. Verified 28 July 2026 by one bounded write-and-recall round-trip per surface, on one date — the receipt is on the register.
the surface that wrote it recall returns the current
answer — history stays on file
The session ends.
The proof remains.
Your machines, your files, your history — and every claim about it verified in public. Thirty minutes is enough to see it against a real question your team argued about last week.