Validator & Evidence — at a glance.

We only show answers we can stand behind. A confidence gate decides show vs. hold. Each answer links to the records behind it. A tamper-evident log shows if anything changes later. This page is intentionally high-level.

Note: detailed internals are shared under NDA.

Confidence gate

We score each answer and only show it if it clears your chosen bar.

Cautious by default

If we’re not confident, we hold it back and ask for more supporting records.

Evidence you can click

Every answer includes links to the relevant invoices, bills, payroll, and entries.

Tamper-evident log

A compact fingerprint chain makes later edits visible at a glance.

How it works (high level)

  1. Gather the facts

    We select the records that actually matter for the claim (and ignore the rest).

  2. Check for agreement

    We verify the story lines up with the numbers and cross-check the supporting docs.

  3. Gate on confidence

    If the answer clears the bar, you see it with links and a short “why.” If not, we hold.

Validator — what we look for

  • Coverage: enough real documents behind the claim.
  • Consistency: totals and subtotals make sense.
  • Agreement: related sources tell the same story.
  • Sanity: dates, ranges, and trends are plausible.
We don’t publish scoring formulas or weights. Details are redacted by design.
When we hold back
  • • Missing or conflicting documents
  • • Arithmetic doesn’t reconcile
  • • Story and records don’t match
We’ll ask for the specific items needed and try again.

Evidence — what you’ll see

Relevant records only

Invoices, bills, payroll periods, and entries that matter for the answer.

Short summary

Plain-English ‘why’ with simple totals you can follow.

Clickable proof

Every item links back so you can confirm in seconds.

We don’t expose internal data models or field names here. For deeper integrations, request access.

Tamper-evident log (conceptual)

Each record includes a compact fingerprint linked to the previous one. If a past record is altered, the chain no longer lines up—making changes obvious.

[ Entry #1023 ]  →  [ Entry #1024 ]  →  [ Entry #1025 ]
     ⤷ fingerprint A      ⤷ fingerprint B      ⤷ fingerprint C
If any earlier entry changes, later fingerprints won't match.
We do not publish hashing methods or field-level composition here. Full specs available under NDA.

Privacy & control

  • Read-only QuickBooks. We never edit your books.
  • Encrypted. In transit and at rest.
  • Disconnect anytime. One click to revoke access.
  • Explainable. Every answer links to its sources.
Omnyra — Validator & Evidence (Overview)