DMS records what entered. Titus records what touched the binary. Accelerate records what was answered. Provenance records what was claimed. Media records what was captured. Audit aggregates all of them into one signed, tamper-evident chain-of-custody view — for compliance, regulators, and incident response.
Per event written, the chain is already there. Per query, the proof comes with it.
Three statements, no jargon.
A read-only aggregator that subscribes to the signed event streams from every Validiti product you run. It does not generate evidence; it gathers and correlates evidence the products already produce.
One question, one answer. "What happened around this customer / case / file / claim?" returns a unified timeline pulling from DMS, Titus, Accelerate, Provenance, Media, and PCI — with signature verification on every step.
Built for the conversation that already shows up: SOC 2, HIPAA, FedRAMP, internal audit, regulator request, breach disclosure. The right answer is to hand them a verifiable trail, not a screenshot of a dashboard.
Each Validiti SKU emits its own signed evidence stream. Audit subscribes to whatever you run; missing products simply don't appear in the timeline.
Every document ingested through Verus emits a link-hash chain entry. Audit pulls these as the inbound provenance for every customer / case / matter touchpoint.
Titus emits a signed event for every file modification, integrity scan, and runtime defense action. Audit aggregates these as the operational integrity record.
Accelerate emits a signed record for every answered query: brain version, cache tier hit, evidence used, response sent. Audit pulls this as the AI-output trail.
Provenance emits per-claim VERIFIED / PARTIAL / NO_SOURCE labels. Audit aggregates these to show which claims in which output had what evidence behind them.
Media emits per-asset origin and tamper-verdict events. Audit ties these to the documents and outputs they support, so the chain runs from camera to claim.
Penates reports loaded brain versions, persona files, and local query state. Audit uses this to reconstruct the runtime context any answer was produced under.
Audit's job is to aggregate signed event streams from every Validiti product you run. The cross-product aggregator is in development; the Titus stream below is live production data from this server — one of the six feeds that will land in the unified timeline.
Where a unified, verifiable trail across Validiti products earns its keep.
Reproduce the full evidence chain for any inbound document, AI output, or media artifact: source → processing → runtime → response. Each step independently verifiable.
Auditor picks any case ID. Audit returns the trail. Findings are about the state of evidence, not the state of your record-keeping.
Pull every signed event in a time window. Cross-product. Tamper-evident. The forensic question stops being "do we have the logs" and becomes "what do they show".
Mapping from each control to the underlying signed events. Auditors verify the chain instead of trusting written attestations.
Audit is sold as a per-tenant aggregator. Every Validiti SKU you run feeds it free; you pay for the aggregator itself.
Single-company deployments. Every SKU's signed events land in one aggregator the auditor can read end-to-end.
MSPs, managed-stack vendors, regulated platforms serving multiple customers from one Audit deployment.
Banks, healthcare networks, defense primes — anywhere the auditor shows up with a clipboard. contact@validiti.com
Every Validiti SKU inherits the same Safe · Fast · Smart guarantees from the shared language — encryption, tamper-evident history, runtime defense, predictable performance. Same code, same proof, same floor on every install.
