How Prima Veritas works

Under the hood, the system organizes events into a consistent structure, links them in sequence, and produces a result that can be reproduced and rechecked.

Prima Veritas operates as a parallel layer alongside existing systems — it does not replace them.

This page explains how the system works at a technical level. You do not need to understand every detail to use Prima Veritas.

The system performs three core functions:

• → Structures events so they can be understood consistently
• → Links them in sequence so changes inside a sealed record are detectable
• → Exports a result that can be reproduced and rechecked without the original systems

Defines how each event is structured so it can be understood consistently over time.

Source events are normalized into a canonical envelope format. Each envelope contains timestamp, origin identifier, version metadata, payload schema reference, and ordering fields.

The envelope format is stable and versioned. Schema evolution does not invalidate historical events. Every record remains interpretable in context.

Makes changes to historical records detectable.

Each event is cryptographically hashed and linked to the next. The hash of the previous event is included in the next record, forming an append-only sequence.

Changing or reordering an event changes its hash and breaks the link to every later event.

The chain alone does not detect removal of events from the end of the sequence, or replacement of the whole record. Those are detectable only against a receipt kept separately.

Designed so the same input produces the same result.

At any point in time, the full chain can be exported as a sealed bundle. The bundle includes event history and reconstruction rules.

Given the same input, the export process produces identical output on the same machine. Cross-machine testing is pending.

The system does not infer or fill missing data. Outputs are derived strictly from the recorded event sequence.