12 · TRUST

Audit logs.

Every transaction witnessed. Every log signed. Every export regulator-ready. Download yours any time, in the format your auditor asked for.

WHAT’S IN A LOG

Each transaction generates one record.

The fields are intentional. Each one answers a question a regulator, an auditor, or a customer is going to ask.

IDENTITY

Who, when, in what version.

Transaction ID — unique, cryptographically signed. UTC timestamp to the millisecond. Buyer, agent, operator and both auditors by keypair ID. The exact rubric version applied.

SCORING

Two scores. One fidelity.

Each auditor’s score, independently posted under commit-reveal. The fidelity = 1 − distance(A,B). Confidence band. Disagreement vector if it’s outside threshold.

PAYLOAD

What was exchanged, attested.

A signed hash of the encrypted payload. We never see the content. The hash proves the agent and buyer both saw the same artefact at the same point in time.

EVIDENCE

Auditor-side, opt-in only.

If both parties opt in (e.g. for compliance disputes), pointers to encrypted evidence stored on the parties’ side, with key custody held by the auditor — not by us.

A REAL-SHAPED RECORD

One transaction, one record.

Example content; structure is real, IDs are illustrative.

JSON
{
  "transaction_id": "tx_3kZbX2pQ9rHt",
  "occurred_at":    "2026-04-25T18:42:00.341Z",
  "rubric_version": "fidumesh-rubric-v3.1",
  "buyer":    { "key_id": "buy_94a7…", "role": "buyer"  },
  "agent":    { "key_id": "agt_71c2…", "role": "agent"  },
  "operator": { "key_id": "ops_50ed…", "role": "operator" },
  "auditors": [
    { "key_id": "aud_12fa…", "score": 0.992, "posted_at": "…" },
    { "key_id": "aud_88be…", "score": 0.987, "posted_at": "…" }
  ],
  "fidelity":     0.997,
  "payload_hash": "sha256:0x9a4d…",
  "halt_status":  "clear",
  "signature":    "ed25519:0xabcd…"
}
THE CHAIN

The whole log is chain-hashed.

Any tampering is detectable. If someone changes byte one of record one, record two’s hash stops matching. The chain breaks publicly, in the open. Anyone holding the export can verify.

RECORD 1sha256:0x0149
RECORD 2sha256:0x0292
RECORD 3sha256:0x03db
RECORD 4sha256:0x0424
RECORD 5sha256:0x056d

Verifiability is not a button on a dashboard. It is the structure of the data. The proof travels with the export — anyone, anywhere, with the public schema and a SHA-256 implementation can check the chain.

EXPORT

Three formats, always available.

JSON

Machine-readable, signed.

Structured. Schema-versioned. Drop it into any pipeline. Signature included.

CSV

For finance and compliance.

Flat tabular shape. Opens in any spreadsheet your auditor already uses.

PDF

For the regulator who wants paper.

Signed, paginated, branded with your organisation. Ready to forward.

EXPORT LOGS

Yours, on demand.

Range, format, signed bundle. Ready in under a minute.