Predictive Ledger

Governance loop1 · Discover_relate→2 · Review_search overrides→3 · Measure_evaluate per rule

Overrides
--

Patterns found

Rule candidates

Most-overridden field

—

corrections

Active correctors

Emerging patterns from overridesFrom _relate on overrides

No patterns found yet — patterns surface once 5+ overrides target the same value.

Overrides by field type

The Predictive DB

_relateOperation

LivePredictions

0Records

IndexedModel

_relate (override mining)

Two-pass _relate on the overrides table: pass 1 finds the most-corrected target values, pass 2 walks the schema link to invoices.vendor to discover which input drove the correction. Output rows have the same input → output shape as Rule Mining, so they can be promoted directly into the rules table.

Example query

{
  "pass2_input_to_output": {
    "from": "overrides",
    "where": {
      "field": "gl_code",
      "corrected_value": "5400"
    },
    "relate": "invoice_id.vendor"
  }
}

Verify yourself

Every claim on this page traces back to an Aito query. No separate model file — Aito predicts directly from its index.

View live schema (JSON) Query API reference

Note: GL codes (4100, 5300, 6200…) are illustrative — real Finnish Liikekirjuri uses different numbering. Chosen for demo readability.

Learn more

API reference: _relate

Start free trial →