Skip to content
TrustNexus

Θεμέλιον

The audit trail is the product, not the by-product.

Themelion is not a module you pick. It is the floor every module stands on. Whichever single module you buy, Themelion comes with it in full.

Worked example

one customer, six steps, six receipts

  1. 09:41:07INTAKE_SUBMITTEDchannel assisted, doc set 3/3
  2. 09:44:22PERSON_RESOLVED3 records to 1, merge stewarded, reversible
  3. 09:47:10RULESET_EVALUATEDv4.2, 2 fields masked, channel api
  4. 09:52:38CONSENT_GRANTEDscope group, lawful basis attached, receipt issued
  5. 10:03:51GRADE_ISSUEDtier 2, trust level high, re-check 90d
  6. 10:14:03TRANSMISSION_SENTinsurer-beta, reg. 39 evidence attached

Four things, every time.

Receipts
What happened, who caused it, when, and under which authority. Issued to the customer where the action is theirs.
Rule versions
The exact ruleset that was live at the moment of the decision, so the decision can be reconstructed years later rather than re-argued.
Context snapshots
The state the decision was taken against: consent scope, grade, entity, purpose. Captured rather than inferred afterwards.
Content hashes
Documents and payloads bound cryptographically to the identity they prove, so tampering is detectable and reliance is defensible.

Retention

Immutable event log, five-year AML retention, legal hold. Residency and retention configured per jurisdiction.

Why it is never sold separately

  • A grade nobody can audit cannot be relied on by a second institution.
  • A consent without a receipt is a claim, not a record.
  • A transmission without its rule version cannot be explained to a regulator.
  • Charging for the proof would make the proof optional. It is not.

Pick one module. The rail comes with it.

Every receipt, rule version and hash from day one is yours to keep.

A person replies, not an autoresponder.

Proven in production at a systemic European bank: transmission to regulated subsidiaries with full consent management and audit trail.

Partnerships
Become a provider