meilynx

Capability

An audit trail your
examiner will accept.

From prompt to examiner, one audit chain. Each request, allowed or blocked, is sealed into a tamper-evident, hash-linked record built to hand to a regulator, an examiner, or a board.

Tamper-evident

Each request, sealed and hash-linked.

Each event is hashed and chained to the one before it. Change a single record after the fact and the chain breaks, which is what lets an examiner verify it.

  • Even blocked requests are recorded; the denial is evidence too.
  • The integrity claim is computed by the proxy in your environment, never delegated.
  • "Audit logs" become examination-ready evidence: control-mapped and immutable.

Tamper-evident audit chain

each request sealed & hash-linked, even blocked ones

  • allowedprev ⌀ → 9f3a1c
  • redactedprev 9f3a1c → 4b07e2
  • blockedprev 4b07e2 → 7e02b4

SHA-256 chain · examiner-verifiable

The examination package

What you hand to an examiner.

The audit trail renders into a package built around the artifacts a financial-services examiner actually asks for.

Model inventory

An inventory of every model in use, auto-populated from live traffic.

Control coverage

Which governance controls were active, in shadow or enforce, across the period.

Policy snapshot

The exact policy-as-code in force, versioned and attributable.

Integrity hash

A SHA-256 hash over the chain so an examiner can verify nothing was altered.
Where it lives

A WORM record, inside your environment.

The hash-chained record writes to a write-once, read-many store inside your environment: retention-locked object storage with a per-customer encryption key.

  • A local write-ahead buffer keeps capturing through downstream outages.
  • A 6-year retention floor on Fully Managed production, per FINRA 24-09.
  • Capture is proxy-side; no raw payload crosses the wire to a SaaS aggregator.

Examiner-verifiable

An Integrity Pack lets an examiner verify the chain independently: recompute the hashes, confirm the sequence, and check the record against the policy that produced it. The integrity primitive is the chain itself, so it holds across storage backends.

By the numbers

Designed for the long record.

Retention floor

6yr

Fully Managed production · FINRA 24-09

Chain integrity

SHA-256

Examiner-verifiable hash over the record

Storage

WORM

Retention-locked · per-customer encryption key

Outcomes recorded

100%

Allowed and blocked alike

Examination package

See exactly what an examiner receives

Model inventory, control coverage, a governance policy snapshot, and a SHA-256 integrity hash, delivered by email.

Regulatory updates

When a regulator changes what an AI examination asks for, hear about it first.

Short notes on SR 26-2, NYDFS 500, FINRA, the NAIC bulletin, the EU AI Act, and the employment-AI statutes, plus what we ship. A few emails a month.