TellParrotAsk most platforms for their audit trail and you get a table. Timestamp, user, action, sometimes a before and after. It is useful for debugging. It is close to useless as evidence, because the people who run the platform can edit the table, and everyone who reads it knows that.
Evidence is a different thing from a log. Evidence has to survive the suspicion that the people who hold it had a reason to change it.
A chain that proves itself
In Lens, every action is hash-linked to the one before it. The record is append-only and key-versioned. If anything in the chain is altered after the fact, verification breaks, visibly, at the point of alteration. There is no quiet edit, because the structure itself refuses one.
That property is what makes the trail usable outside the organisation. TellParrot produces evidence bundles that a third party can verify independently with an offline verifier. A regulator, an external assessor or the other side of a dispute does not need access to TellParrot, and does not need to take your word for anything, to confirm that the bundle is intact and in sequence. Chain checkpoints can also be anchored externally, and the anchoring status is shown in the product rather than asserted in a slide.
Who decided, in what role, on whose behalf
The action ledger records more than the fact that something happened. It records who proposed it, who approved it, in what role they were acting, and on whose behalf. Refusals are recorded too. A decision that was declined is part of the history, not an absence in it.
Where the stakes call for it, two-person control applies to the exact content being approved, not to a summary of it. Cases collect the full decision trail, and a decide queue at the top of the case list keeps the work visible rather than buried in notifications.
Delivery you can prove
The trail does not stop at the boundary of the platform. Governed exports carry receipts: the disclosure to a regulator, the response to a subject access request, the bundle sent to an auditor. Each one leaves through a governed gate with lineage attached, so the question "what exactly did you send them" has an answer that can be checked.
Why we built it this way
A governance platform that cannot prove its own history is asking to be trusted. We would rather be checked. Every merge, every policy attachment, every model registration and every export in TellParrot lands on the same chain, so proving what happened is not a project you run before the audit. It is the state the estate is always in.