Get started

Logging · the evidence layer

Every log. One chain.

Quox keeps one story: every chat, run, decision and hand-off writes envelopes, layer records and evidence events tied together by a single correlation id, from the moment you ask to the receipt an auditor can verify.

Envelopes and layers: in QuoxCORELedger and receipt views are an add-on.
Activity views7Verification checks13Audit retention default365 days

Where to look

One place per question.

Most platforms scatter their story across log files you grep at midnight.

01What happened today?

The Activity page: seven server-scoped views: chats, objectives, workflows, governance, tools, rooms and system. Each tab is a real query, not a client-side filter.

/activity

02What exactly did that run do?

The trace: every AOCL layer with timings, policies passed, memories used, cost incurred. Export it as JSON, Markdown or CSV.

/traces

03Can you prove it?

VOLT: hash-chained events and evidence bundles, verified by thirteen named checks from parse to Merkle root.

/volt · /evidence

04Who witnessed it?

WARD: content-free hash receipts chaining every witnessed event, with a public verify surface.

/ward

05Will it satisfy the framework?

Compliance exports: JSON free, with SOC 2, HIPAA, GDPR, ISO 27001, EU AI Act, ISO 42001 and NIST AI RMF formats in the compliance suite.

/compliance · licence-gated formats
quoxcore · activity centre
The Activity page's seven server-scoped view tabs (chats, objectives, workflows, governance, tools, rooms and system), Chats active, with a header count of 1,543,350 envelopes and 70 conversations, a search box, a tagged and timestamped conversation list, pagination, and the SENTINEL audit panel open alongside with suggested prompts.
  1. 1Switch views with the tab railChats, objectives, workflows, governance, tools, rooms and system each run their own real query, not a client-side filter.
  2. 2Read the scale up front1,543,350 envelopes and 70 conversations sit as plain counts in the header, not marketing copy.
  3. 3Search and see the countA search box sits beside a live count of what is currently loaded, 30 of 30 here.
  4. 4Every row carries its own tagsWORKFLOWS/EVENT and CHATS/TASK labels sit on each row alongside its message count and timestamp.
  5. 5Page through the full historySeventy conversations paginate thirty at a time, with previous and next controls.
  6. 6Ask SENTINEL about the audit trailSuggested prompts such as "Audit trail for the last objective run" sit ready beside the queue.

Captured from the real Activity page, not a mockup.

Try it

Seven views, one id each.

A mock of the Activity page, wired to nothing. Switch views with the tabs (or the left and right arrow keys), then click a row to watch its correlation id flow through an envelope, its AOCL layers, a VOLT event and a WARD receipt.

This is a mock of the Activity page, wired to nothing. Use the tabs, or the left and right arrow keys, to switch views; click a row to see its correlation chain.

Demo data, wired to nothing · click a row for the corr chain · ← → to switch views

How it chains

One id, end to end.

Ask a question and a correlation id is born. The envelopes that carry the work inherit it, the eleven AOCL layers stamp their records with it, the tool executions land in VOLT under it, and the witness receipts chain it. Click any conversation in Activity and follow the whole thread: the id is the story.

corr bornAEE envelopes inheritAOCL layers stampVOLT events landWARD receipts chain
An AOCL trace: every layer with timings, policies passed, memories used and cost incurred

Why it works

Four protocols, one spine.

AEE

Every message is an envelope: sender, intent, conversation, payload: nothing travels naked.

AOCL

Eleven layers from ingress to audit, each emitting observable records.

VOLT

The verifiable operations ledger: hash-chained events, evidence bundles, import and verify without trusting us.

WARD

Write-once receipts witnessing the chains themselves.

VOLT, the verifiable operations ledger: hash-chained events and evidence bundles verified by named checks

The payoff

Proof that travels.

Traces export with their control mappings. Evidence bundles drop into the verifier and come back green or they do not. Auditors get a read-only role scoped to exactly these surfaces, and retention is policy: ninety days by default for operational logs, a year for audit events, deletion requests honoured.

auditor role · read-only · retention by policy

The compliance suite's live monitor: framework exports and evidence status

also in the suite

The auditor portal, honestly empty until an auditor is invited: no fabricated rows
Auditor portal
The compliance centre: framework dashboards for SOC 2, HIPAA, GDPR, ISO 27001, EU AI Act, ISO 42001 and NIST AI RMF
Compliance centre
The policy centre: governance policies and their enforcement status
Policy centre

Straight answers: witness coverage is per-surface and the UI says so when a receipt is unavailable rather than pretending; several layer emissions are still marked beta in our own status docs. The chain never claims more than it holds.

Ready when you are

Stop grepping. Start proving.

AEE envelopes and the AOCL layer audit ship with QuoxCORE. The dedicated VOLT ledger and WARD receipt views are the Decision Evidence plugin, an enterprise add-on.