ZoikoLogia

Platform · Audit Evidence Ledger

Preserve the evidence behind every governed AI-assisted workflow.

See which sources, contexts, retrieval steps, limitations, reviews, and decisions shaped an AI-supported accounting outcome — with attributable records and professional controls.

Governed AI-assisted workflow

Evidence Continuity

The end-to-end lifecycle, from source admission to reviewed outcome

Continuity of evidence runs the whole way — every stage is recorded, so an AI-assisted outcome is never an unexplained jump.

  1. 01

    Source eligibility

    Only approved, in-scope sources may enter.

  2. 02

    Content resolution

    The relevant content is resolved and recorded.

  3. 03

    Retrieval bundle

    The exact bundle retrieved is captured.

  4. 04

    AI-supported output

    The generated response, kept separate from sources.

  5. 05

    Human review

    A qualified person confirms, revises, or overrides.

  6. 06

    Consequential action

    Any action taken on the reviewed outcome.

  7. 07

    Change & retention

    Versioning, freshness, and retention state.

Reviewing evidence at a desk

Ledger Structure

What the ledger records — and what it does not claim

Eight record families capture identity, presence, context, retrieval, output, review, action, and lifecycle change.

Identity
Actor, tenant, subject, and timestamp — who and what.
Source presence
Which sources were present and eligible at the time.
Context
Framework, jurisdiction, entity, and reporting period.
Retrieval
The retrieved bundle and its manifest.
Output
The generated response, held separate from its sources.
Review
The reviewer's confirmation, revision, or override.
Action
The consequential action taken, if any.
Lifecycle
Version, freshness, and retention state over time.
Team at a whiteboard

The ledger does not claim an answer is correct or an opinion is sound. It records what informed an outcome and who reviewed it — correctness remains a qualified human responsibility.

Demonstration · Synthetic Entry

Inspect a synthetic evidence entry

No customer data. A fictional entry to show how an evidence record is structured.

Overview

A synthetic entry showing how one governed interaction is recorded end to end.

Inspecting a synthetic evidence entry

Decision Rights

Seven roles, explicit permissions

Human review is the final decision. No role may silently rewrite historical evidence.

  • Contributor

    Creates and edits entries; cannot alter finalized records.

  • Specialist

    Adds domain review within a defined scope.

  • Auditor / assurance reviewer

    Read-only access to the full evidence trail.

  • System service

    Automated writes under policy, with no silent override.

  • Reviewer

    Confirms, revises, or overrides before an outcome is used.

  • Administrator

    Configures roles, sources, and retention.

  • Observer

    Limited, time-boxed read access.

Reviewer presenting to a team

Append, Never Overwrite

Change, version and freshness

Corrections and revisions create a durable new event. Each change is disclosed to the user.

Source update

A source version changes upstream.

Disclosure to user

The user is shown that a newer source version now applies.

Content revision

An entry is revised after review.

Disclosure to user

The prior version is preserved and marked superseded.

Version change

A concept or standard is re-versioned.

Disclosure to user

The user sees which version informed the answer.

Retention window

An entry reaches its retention boundary.

Disclosure to user

Retention state is disclosed, never silently purged.

Freshness check

A source is re-checked for currency.

Disclosure to user

Stale sources are flagged rather than used quietly.

Correction

A recorded error is corrected.

Disclosure to user

A correction is appended; history is never overwritten.

Privacy & Access

Evidence continuity coexists with field-level protection

Tenant isolation

Each organization's evidence is separated at the boundary.

Redaction

Sensitive fields can be redacted without breaking the trail.

Field-level protection

Field-level access

Access is bound per field, per role, per policy.

Purpose limitation

Records are used only for the purpose they were governed for — never repurposed silently.

Integrity Architecture

Integrity and export boundaries

Integrity architecture
  1. 1

    Entries are append-only; nothing is edited in place.

  2. 2

    Each record is chained so tampering is detectable.

  3. 3

    Exports carry their integrity signature with them.

  4. 4

    Redaction preserves the record's structure and lineage.

  5. 5

    Retention and deletion follow governed, disclosed policy.

Platform Continuity

Connected platform layers

The ledger sits under the whole platform chain, so every layer's evidence is captured.

Platform channels

Where professionals interact with Kriton™.

Source-Governed Intelligence

The reasoning layer over admitted sources.

Accounting Ontology

Governed concepts and typed relationships.

RAG Source Bundles

The eligible, versioned sources per question.

Audit Evidence Ledger

The append-only record tying it all together.

Connected platform teams

Synthetic · Non-Advisory

Evidence journeys across accounting, audit, tax and payroll

Every scenario is fictional. None is a professional conclusion.

Accounting policy review

Record which governed sources informed a treatment question.

route to Accounting Firms

Audit evidence planning

Tie assertions to the evidence that substantiates them.

route to Assurance Teams

Tax update review

Trace a versioned change to what now applies, and when.

route to Tax Teams
Practitioner presenting

Payroll compliance check

Bind an answer to the correct jurisdiction and period.

route to Payroll & Compliance

Learning mode

Prerequisite-aware practice; commentary supports, not decides.

route to Learning & Practice

Enterprise Administration

Configuration, roles and operations

Administrator at work
Approved source domains
Curate which source families may be recorded.
Roles & permissions
Bind who can read, write, or export the ledger.
Retention policy
Set retention windows and disclosure rules.
Source & context options
Govern the context that must be captured.
Integrations
Connect existing evidence and identity systems.
Notifications
Alert on freshness, retention, and review events.
Analytics
Report on evidence continuity and review coverage.

Direct Answers

Frequently asked questions

An append-only record of every governed AI-assisted interaction — the sources present, the context, the generated output, the human review, and any action — preserved so the basis of an outcome can always be reconstructed.