What the agent did, under whose authority, provable in ten years.

The gap it fills

A generation of tooling now watches what agents do. Kernel-level harnesses observe syscalls, policy engines block disallowed actions, frameworks emit traces. That layer is real, it is well funded, and it is not what we are building.

Every one of those is a sensor. None of them is a system of record. They produce a stream, and a stream you cannot verify without the vendor still existing is telemetry, not evidence. The question an auditor asks in 2031 is not "what does your dashboard say" — it is "prove this record has not been altered since it was written."

What it is, precisely

What it is not

• Not a blockchain. No consensus, no peers, no token, no mining. A blockchain solves agreement between mutually distrusting parties, which is expensive and almost never the enterprise requirement. Roobee solves tamper-evidence for a single writer who may later be questioned. It is the same mathematics that already secures every HTTPS connection you make — Certificate Transparency, not cryptocurrency.
• Not a database. No updates, no deletes, no transactions, no query language. It sits beside your Postgres, not in place of it. Postgres holds the balance; Roobee holds the record that agent X moved it, under warrant Y, delegated from human Z.
• Not a sensor. It does not watch your agents. It is what the watchers write into.
• Not a replacement for your warehouse. See below.

How it lives beside Snowflake and Databricks

Roobee is small, append-only and optimised for proving one record authentic. It is deliberately bad at analytics. So sealed epochs stream into your lakehouse as a derived table — Iceberg, with the content hash as a column — and you get SQL over billions of agent actions: attribution, anomaly detection, cost, coverage.

The warehouse copy is not the evidence, and being clear about that is the point. It is a mutable table in a system where a privileged user can run an UPDATE. When a record is challenged you do not hand anyone a warehouse query — you produce the inclusion proof from the log. Ask questions in the lakehouse; answer challenges from the ledger.

What happens as it grows

• Epochs, chained. A log seals at a set size, publishes a signed checkpoint, and the next epoch's genesis references the previous root. Sealed epochs move to cold storage; the checkpoint chain stays small enough to keep forever and is all you need to verify the whole history.
• Delete content, keep proof. Because the structure is a Merkle tree, record bodies can be discarded past a retention window while their leaf hashes remain — inclusion proofs still verify. You can prove a record existed, and that it was deleted, without retaining what it said.
• Which is also the erasure answer. Most immutable-log proposals die on the collision with data-deletion law. This one does not: the payload goes, the integrity stays.

How the data gets in

There is a genuine tradeoff here and we would rather state it than paper over it: the sources you can trust most see the least meaning, and the sources richest in meaning are the easiest to lie to.

The interesting output is not either channel alone — it is where they disagree. An action claimed but never observed means an agent reporting work it did not do. An action observed but never claimed means an agent doing work it did not declare. Activity under no warrant at all means unauthorised action. A sensor with nothing to check itself against can only report; it can never contradict.

Why the format is open

Your requirement is that this outlives us. That requirement is unsatisfiable if we are the only ones who can read the artifact — so the record format, the Merkle construction and the verifier are open and will stay that way. Run the verifier on a bare interpreter in ten years, with no licence, no service and no vendor.

What we sell is the operational layer above it: retention and epoch management at scale, lineage query, the regulator-facing exports, the collectors, and the integration with Engine and Garrison so that runtime execution and agent governance write into the same log as everything else.

How you buy it

Priced per governed agent rather than per record, deliberately. Charging by volume would penalise exactly the behaviour the product exists to encourage: recording everything, including the boring actions that turn out to matter.

Transacted through AWS Marketplace like the rest of the line, so it lands on the AWS bill you already have and draws down committed spend. Container listing for the deployable parts; private offer for multi-year terms.

The witness, and why it matters

A tamper-evident log proves nobody edited it without you noticing. It does not, on its own, prove that you did not rewrite it, because you hold the log. That is a real limitation and the honest answer to it is not cryptography — it is a second party.

A witness periodically counter-signs your checkpoint roots. Afterwards, rewriting history requires forging an attestation held by someone else, which is precisely the property a regulator is looking for. Certificate Transparency works this way and it is why CT is credible: independent monitors, not a trusted operator. Handeware can act as witness; so can your auditor, your regulator, or a notary you already retain. The protocol does not care, which is the point.

How you mount it

Entirely inside your boundary. There is no Roobee cloud, no tenancy, and nothing of yours on our side — the same posture as the rest of the product line.

What adoption actually looks like

Note what step two is for: you should try to break it before you trust it. Corrupt a record and confirm the verifier refuses. A guard that passes both ways is worse than no guard, and that applies to ours as much as anyone's.

Where it sits in the line

Roobee is the substrate the rest of the product line already implied. Prove emits evidence bundles. Engine event-sources every run. Garrison will evidence every agent action. Roobee is that shared model made explicit, standalone, and adoptable on its own — including by people who use none of the rest.