Reference

Audit log

The append-only record of every significant event in your organisation: who did what, to which subject, and when. It is your tamper-evident source of truth for governance and compliance.

What it records

Each domain event is projected to a permanent audit entry as it happens. The log is append-only: entries are never edited or deleted, and the trail reads newest-first by default. Every row captures:

• When: the timestamp, shown as a relative label (hover for the absolute time in your organisation's timezone).
• Actor: who triggered the event. The actor type is one of User, Agent or System, resolved to a name where possible.
• Action: the verb that occurred, such as a configuration change, run, approval decision or membership change.
• Subject: the record the action acted on (its type and identifier), where applicable.
• Details: expand any row to see the recorded changes and context as JSON.

Filtering and search

Narrow the trail using any combination of controls. All of them live in the page URL, so a filtered view is shareable and survives paging:

• Search: matches against the action, the actor identifier, or the subject identifier.
• Actor: filter to User, Agent or System events.
• Action and Subject: the dropdowns only offer verbs and subject types that actually exist in your trail, so a chosen filter always returns something.
• From / To: restrict to a date range.

Use Clear filters to reset everything. You can also sort by When, Actor or Action from the column headers. Sorting is display-only and never changes the underlying records.

Integrity and signed export

Every entry is linked into a tamper-evident hash chain. On each page load SyftOS re-verifies the chain and shows the verdict at the top of the page:

• Verified: all chained entries match, confirming nothing has been altered.
• Check failed: the chain could not be verified (the banner names the first broken entry). This may indicate the record has been altered; contact your administrator.

Download signed export streams the full trail as JSON together with a signature over the chain. An external party can verify that signature to prove the export is the genuine, untampered record. The chain is checked before signing, so a tampered trail can never be exported as attested, and the signing key never appears in the download.

Who can view it

The audit log is gated by the audit.view permission and is read-only for everyone — there is no action that creates, changes or removes an entry by hand. Agents never write here directly; their effects are recorded as the underlying events occur, keeping the trail an impartial account of the approval gate, runs and configuration changes alike.

Next steps