ZoikoLogia

Platform · RAG Source Bundles

Build every answer on a governed source bundle.

ZoikoLogia™ assembles approved, context-specific source material for Kriton™ and governs retrieval — screening authority, applicability, permissions, versions, conflicts, and evidence continuity — so a source-backed answer preserves professional judgement.

Team reviewing a governed source bundle

Source eligibility

Eligibility model

Context and permissions

Context controls

Versioned manifest

Manifest model

Conflict visibility

Conflict handling

Human review / escalation

Escalation limits

Design Principle

Why generic RAG is not enough

Do not mistake retrieval for intelligence by itself. Retrieval becomes useful only when source authority, accounting meaning, context, permissions, evidence continuity, and human judgement work together.

  • Generic retrieval

    Answers a query without professional context or authority.

  • Generic retrieval

    Retrieves text that merely matches, regardless of standing.

  • Generic retrieval

    Returns a citation after generation, without showing the decision.

  • Generic retrieval

    Treats aliases and synonyms as freely interchangeable.

  • Generic retrieval

    Leaves restricted content reachable outside its permitted scope.

Advisors reviewing documents

Bundle Manifest

What is inside, and what is recorded

Bundle ID, extract, assembly time, context summary, and selected sources — each recorded, versioned, and inspectable. Not one authoritative dump. All identifiers are fictional.

Bundle-MFT-4471Synthetic
SourceAuthorityVersionStatus
Recognition standard — syntheticPrimary standardv4.2Admitted
Interpretive guidance — syntheticGuidancev2.1Admitted
Internal policy note — syntheticFirm policyv1.0Conditional
Jurisdictional guidance — syntheticRegulatoryv3.4Admitted
Conflicting interpretation — syntheticCommentaryv1.7Flagged
Reviewing the bundle manifest

Retrieval Scope Controls

Authority precedes relevance

Eligibility is decided before similarity is ever considered. Six controls bound what may enter a bundle.

Accounting framework

IFRS, US GAAP, or a local basis narrows which sources are even eligible.

Jurisdiction

The territory in play selects which sources may answer.

Entity type & attributes

Entity shape changes what applies before relevance is considered.

Reporting / tax period

Effective dates decide which version of a source is live.

User role

Role governs what a given user is permitted to retrieve.

Tenant / workspace

Tenant isolation bounds the source set to the organization.

Team applying retrieval scope controls

Conflict, Uncertainty & Missing Evidence

These states are first-class, not edge cases

The table result may be uncertainty, refusal, or escalation — the system will not silently choose one, and issue is visibly built into a confident answer.

Conflicting sources

Surfaced, not silently resolved — the qualified position is stated and the gap is named.

Missing evidence

Named as missing; the answer is bounded rather than smoothed over with a guess.

Insufficient scope

When scope is too narrow to answer safely, retrieval pauses instead of overreaching.

Team working through conflicting sources

Evidence Continuity

Four artifacts that must remain distinguishable

The bundle, the generated explanation, the human review, and the ledger record are never collapsed into one. The human review record captures what a person decided.

1

Bundle

The exact set of sources retrieved for a question.

2

Generated explanation

The drafted response — always separable from its sources.

3

Human review

The reviewer's confirmation, revision, or override.

4

Ledger record

The append-only trail tying bundle, answer, and review together.

Evidence review
Evidence review

Synthetic · Non-Advisory

How this behaves in realistic work

Every scenario uses fictional entities, periods, and figures. None is a professional conclusion suitable for filing, opinion, or submission.

Accounting policy research

Assemble governed sources for a treatment question, with the reasoning shown.

route to Accounting Firms

Audit evidence planning

Relate assertions to the evidence and procedures that substantiate them.

route to Assurance Teams

Tax update review

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

route to Tax Teams
Practitioner at work

Management reporting

Pin a metric to its definition, inputs, and reporting boundary.

route to Finance Teams

Learning mode

Prerequisite-aware paths; commentary supports understanding, it does not decide.

route to Learning & Practice

Enterprise Administration

How an organization can govern or connect it

Administered fully via console

  • Approved source domains

    Curate which source families may enter a bundle at all.

  • Retrieval policy profiles

    Define scope and authority rules per team or task.

  • Contract requirements

    Set the evidence a bundle must carry before use.

  • Field-level rules

    Restrict retrieval down to specific fields and attributes.

  • Role-based access

    Bind what each role can retrieve to policy.

Connected to existing sources

  1. 1

    Connect approved internal document and policy stores.

  2. 2

    Map external standards and regulatory sources to the ontology.

  3. 3

    Sync versions and effective dates on a governed schedule.

  4. 4

    Keep tenant isolation intact across every connected source.

Governance console

Evaluation and Proofs

How bundle quality is assessed

No unsupported accuracy coverage or raw-recall from a bare, un-permissioned index — quality is assessed with proofs and defined scope.

Bundle eligibility proofsContext complianceLineage integrityConflict-detection recallFreshness enforcementPermission enforcementBundle reproducibility
Proof artifactSignal
Bundle assembly evaluation summaryEnd-to-end assembly correctness
Source-selection regression reportSelection stability over time
Conflict-detection recallConflicts surfaced, not missed
Freshness & permission checksRestricted or stale sources excluded
Assessing bundle quality

Audience Pathways

Choose the next step for your role

Accounting & finance professional

See source-backed answers with the basis shown.

Explore pathway →

Audit and assurance reviewer

Trace bundles to evidence that stands up to review.

Explore pathway →

Tax, payroll or compliance specialist

Scope sources to the right jurisdiction and period.

Explore pathway →

CTO / technical leader

Fit governed retrieval into your existing stack.

Explore pathway →

Data, AI or engineering leader

Ground models on governed, reproducible bundles.

Explore pathway →

Legal / procurement reviewer

Evaluate controls, rights, and evidence before buying.

Explore pathway →

Learner / educator

Prerequisite-aware learning with integrity safeguards.

Explore pathway →

See governed bundle assembly in a controlled walkthrough

Evaluate source eligibility, context controls, and human review with your team before committing to a pilot.

Direct Answers

Frequently asked questions

A governed, versioned set of sources assembled for a specific question — each one eligibility-checked, scoped to context, and recorded — rather than whatever text happened to match.

Related Routes

Related routes