Skip to content

Methodology

Trinity Audit Engine

The Trinity Audit Engine (TAE) is our automated audit pipeline. Every Trinity chart is continuously cross-checked against public industry reference sources. When a discrepancy exceeds the declared tolerance, the affected metric is suspended pending investigation and resolution.

Why a continuous audit

Many analytics platforms operate on a trust model : 'here are our numbers, trust us'. Trinity Insights refuses that posture. Every value the platform returns must be verifiable against a publicly accessible external source.

The TAE enforces this discipline by running automated checks at a cadence matched to the data's nature (intra-day for real-time flows, daily for macro, etc.) and raising an internal alert as soon as a discrepancy crosses the tolerance declared for that metric.

What the TAE checks

Reference sources

All reference sources the TAE uses are public and free of charge — central banks (Fed, ECB, BoJ, BIS), academic aggregators, public on-chain blockchain data, public registries. No commercial aggregator is part of the audit loop, to guarantee reproducibility and independence from competing analytics editors.

Tolerances and cryptographic properties

Each non-exclusive metric carries a declared tolerance — the maximum acceptable gap between the Trinity value and the public source value. Tolerances are defined at integration time and account for rounding, timestamp shifts, and per-source reconciliation conventions.

Audit results are stored append-only with cryptographic integrity : no past result can be retroactively modified. This property is essential for institutional traceability.

Trinity proprietary indicators

Trinity composites are proprietary models with no direct public industry equivalent. The TAE applies a specific protocol for them: verification of internal coherence (continuity, bounds, calibration vs an institutional reference cited in the documentation), instead of direct comparison.

When a discrepancy is detected

When a discrepancy crosses the declared tolerance, the TAE raises an internal alert, which triggers an investigation. The metric may be :

This policy is intentionally asymmetric : Trinity prefers to remove a metric rather than display unverifiable data.

Operational status

The platform's operational status — including the audit chain — is published in real time at trinityinsights.io/status.