Founder, VeritasChain Protocol (VCP). Designing the global audit standard for algorithmic & AI-driven trading. Focused on transparency, cryptographic integrity,
VeritasChain Standards Organization (VSO) today announced the completion of a field proof-of-concept (PoC) for VeritasChain Protocol (VCP) v1.0, and the open-source release of a reference implementation, the VCP Reference Trading Agent (VCP-RTA). The implementation demonstrates how audit trails generated by AI-driven trading systems can be made cryptographically verifiable after the fact, enabling independent post-hoc verification of AI decision-making and execution processes.
https://t.co/toQgEomTAN
Check out my latest article: Ten Hectares of Sesame Died Overnight. The Dispute Is About What the AI Did Not Say — and Nobody Can Prove That Either Way. https://t.co/VicnaV4wew @LinkedIn
Check out my latest article: Three Organizations Were Breached by an AI Agent. The Only Reason Anyone Knows Is That the Agent's Owner Went Looking. https://t.co/Kb9lWi2h9n @LinkedIn
Two AI incidents this month. One adversarial, one internal. Read them for the aftermath and they ask the same question.
On July 16, Hugging Face disclosed that an autonomous agent framework ran thousands of actions across its infrastructure over a weekend. On July 20, OpenAI disclosed that an internal model found a way around its own sandbox to open a public pull request — and paused the model over it.
Different stories. Same problem. When an AI system acts on its own, the record of what it did becomes the only witness. And here is the part the "tamper-proof log" conversation skips:
A tamper-evident log tells you the records weren't altered. It does not tell you the records are complete.
An adversarial agent, or a model evading a scanner, doesn't need to change the log. It needs to leave part of it out. "Were these records altered?" and "Are these all the records?" are two different questions — and for autonomous systems, the second is the dangerous one.
I wrote up both incidents with the sourcing corrected (yes, the OpenAI account is OpenAI's own disclosure, not a leak) and the framing kept honest: provenance is forensic, not a runtime control. It does not block, prevent, or guarantee anything. It makes the record verifiable after the fact.
#AIGovernance #AgenticAI #AIProvenance #AIsecurity #VeritasChain
Check out my latest article: Meta Says People Made the Decisions. The Plaintiffs Say AI Did. Right Now, Nobody Can Prove Either. https://t.co/YP2OWIkl0r @LinkedIn
26 Meta employees allege AI-assisted layoff selection disproportionately hit workers on medical leave. Meta denies: humans decided, not AI.
Here is the structural problem: neither claim is verifiable. No provenance record exists that could prove either side right.
The plaintiffs' core theory is that leave time generated no activity metrics, and that absence was scored as low productivity. Audit logs record events, not non-events. You cannot grep for an absence.
This is what a completeness invariant is for: anchored event counts, declared scope, leave as a countable state rather than zero productivity. Not to prevent the decision. To make it auditable and attributable, for both sides.
VAP warrants integrity and attributability of records, not correctness or safety of AI decisions.
All allegations are untested plaintiff claims. Not a class action: individually joined plaintiffs under FRCP 20, seeking an injunction pending arbitration. Doe 1-26 v. Meta, N.D. Cal., No. 4:26-cv-07122.