LumenpathRecord Assurance

Platform

A record that keeps its own proof

Lumenpath sits beside your existing systems and writes down what moves between them. Six modules, one record, one place a reviewer can go.

01Modules

What each module is responsible for

Who held the record

Custody Trail

Every handover is written down as it happens: who sent the document, who received it, on which system, at what time. The trail is append-only, so a correction shows up as a new entry rather than a quiet edit.

  • Append-only entries with the previous entry referenced by hash
  • Handover recorded on both sides, not only by the sender
  • Corrections logged as amendments with a reason field
02Assembly

How a document becomes a sealed record

Three steps, run every time a document enters the trail or changes hands.

  1. 01

    Assemble

    The document, its metadata, the signing state and the people involved are gathered into one record. Nothing is re-typed, everything is captured from the system where it happened.

  2. 02

    Seal

    A hash of the record is taken and timestamped. The seal is written into the trail and published so it can be checked later without our help.

  3. 03

    Hand over

    Counterparties receive a packet or a scoped window instead of a copy nobody can trace. Their access becomes part of the trail too.

03Standards

What we follow, and what we do not claim

We hold no certification yet. These are the practices the platform is built on, stated plainly so you can check them against your own requirements.

Where a jurisdiction requires something we do not yet support, we will say so during the first call rather than after the contract.

Bring one file that failed a review. We will walk it back to its origin.

Send a document that an auditor, a bank or a counterparty questioned. We will show what Lumenpath would have kept, and what nobody can reconstruct any more.