Audit Trail — selfdriven.consulting

Evidence, not logs

Most consulting engagements end with a deliverable and a handshake. If a dispute arises six months later about what was recommended, what was approved, or who made a decision — the record is whatever email or Word document you can find.

Every selfdriven engagement produces a cryptographic audit trail anchored in KERI. Not a log file that can be edited. Not a database that can be queried and modified. A tamper-evident Key Event Log that is independently verifiable by any party.

Regulatory-grade by design

The selfdriven audit trail is designed to meet the evidentiary standards required by ASIC, APRA, AUSTRAC, and equivalent regulators in other jurisdictions. Every significant engagement event — brief receipt, conductor assignment, agent delegation, deliverable approval — is anchored as a KERI interaction event.

The trail is a cryptographic chain of custody for the entire engagement. You can present it to an auditor, a regulator, or a court — and they can verify it without asking selfdriven for anything.

What gets recorded

Every event that matters

The audit trail captures engagement lifecycle events as KERI interaction events, anchored to the engagement Key Event Log. The chain is append-only — nothing can be removed or altered.

PHASE 01

Initiation

The engagement begins with an inception event (icp) — establishing the engagement AID and anchoring the brief. The brief content hash is embedded in the inception event, making the starting point tamper-evident.

icp — engagement inceptionbrief hash anchoredclient AID registered

PHASE 02

Assignment

Conductor assignment is recorded as an interaction event — linking the conductor's verified AID and their vLEI credential to the engagement. From this point, accountability is cryptographically bound.

ixn — conductor assignedconductor AID verifiedvLEI credential linked

PHASE 03

Execution

Each agent delegation, research completion, draft production, and review cycle generates an interaction event. The chain of work is visible, ordered, and attributed — every action linked to the agent or conductor that performed it.

dip — agent delegatedixn — research completedixn — draft producedixn — review approved

PHASE 04

Delivery

Final deliverable approval is an interaction event with the deliverable content hash embedded. Any post-delivery modification to the document produces a different hash — making tampering immediately detectable.

ixn — deliverable approvedcontent hash anchoredACDC credential issued

PHASE 05

Closure

Agent credentials are revoked via rotation events. The engagement KEL is finalised. The complete record — from brief to delivery — is yours to export, archive, and present to auditors. selfdriven retains no privileged access to the trail.

drt — agent credentials revokedKEL exported to clientengagement closed

Properties

What makes this trail different

Tamper-evident

Each event in the KEL includes a cryptographic digest of the previous event. Any modification to a past event breaks the chain — making tampering immediately detectable by anyone who verifies the log.

Independently verifiable

Verification doesn't require selfdriven's cooperation. Anyone with the engagement AID and access to the witness network can resolve and verify the full KEL — with no central authority to trust.

Attributed to real people

Every event is attributed to a specific AID — conductor or agent — with a verifiable credential chain. You know exactly who approved what, and you can prove it without relying on selfdriven's records.

Deliverable integrity

Every approved deliverable has its content hash anchored in the KEL. If a document is modified after delivery — even a single character — the hash won't match. The original approved version is cryptographically preserved.

Regulatory Context

Meeting the standard auditors require

The selfdriven audit trail is designed with Australian and international regulatory requirements in mind.

Regulator / Standard	Requirement	How the audit trail meets it
ASIC	Record-keeping for advice and recommendations	Every recommendation is a signed KERI event with content hash — immutable and attributable
APRA	Governance and accountability documentation	Conductor vLEI credentials and delegation chains provide verifiable accountability structures
AUSTRAC	Transaction and decision audit trails	Append-only KEL provides ordered, timestamped, tamper-evident record of all engagement decisions
ISO 27001	Access control and audit logging	Agent scope credentials and KEL-anchored access events provide cryptographic access control evidence
Evidence Act	Authenticity of electronic records	KERI self-certifying identifiers and cryptographic signatures provide strong authenticity evidence

Export & Portability

Your audit trail belongs to you

At engagement close, the full KEL is exported to you in a standard KERI-compatible format. You own it. selfdriven retains no privileged access after handover.

What you receive

The complete Key Event Log for the engagement AID
All agent delegation events and their associated ACDC credentials
Content hashes for every approved deliverable
Conductor and agent AIDs for independent verification
Witness receipts from the 3-of-3 distributed witness network

What you can do with it

Present to regulators as primary evidence of engagement conduct
Verify independently using any KERI-compatible resolver
Anchor to your own KERI infrastructure as a foundation identity
Use as the basis for your own delegated agent credentials
Archive in your document management system as a tamper-evident record

The selfdrivenAudit Trail