Extraction v2 on BonsAI Documentation

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Extraction v2 Overview #

Classification: Internal-Only

Extraction v2 is a Rust extraction pipeline that runs beside the current hinoki pipeline, not instead of it. A router worker sits in front of 100% of extractions and assigns each one to an arm; the v1 arm is the pipeline that runs today, unchanged. Only AP bill is in scope.

The PoC (ENG-7054, ENG-7095, ENG-7100, ENG-7101) established the approach offline. Nothing from it reached the monorepo except two client libraries — one for Extend, one for the Bedrock models. This is a greenfield build informed by the PoC findings, not a port of PoC code.

Stages

Mon, 01 Jan 0001 00:00:00 +0000

Stages #

Classification: Internal-Only

What each stage does, what it may assume, what it costs, and how it behaves when something goes wrong. The flow and the cost split are in Overview.

Types, signatures and schemas live in the implementation and in the Linear issues that track it. This page describes behaviour, which changes far less often than either.

How a stage works #

A stage is one async step over inputs it is handed. Three rules hold for all of them:

Routing & A/B

Mon, 01 Jan 0001 00:00:00 +0000

Routing & A/B Assignment #

Classification: Internal-Only

How an extraction gets assigned to an arm, why the assignment is per extraction rather than per entity, and what makes the resulting comparison readable.

The pipeline itself is in Overview; what each stage does is in Stages.

Topology #

                      ┌──────────────────────────┐
   bonsapi ──────────▶│        route queue       │
                      └──────────────────────────┘
                                   │
                             router worker
                                   │
                 ┌─────────────────┴─────────────────┐
                 ▼                                   ▼
            v1 arm queue                        v2 arm queue
      (unchanged — bonsai-invoice          (the Rust extraction
       and hinoki)                          worker)

Three queues. The route queue is new; the v1 arm keeps the queue and consumer that exist today, unchanged.

Measurement

Mon, 01 Jan 0001 00:00:00 +0000

Measurement Definitions #

Classification: Restricted (describes database views, columns and measurement methodology).

INTERNAL - DO NOT FORWARD

One definition of accuracy, in one place, used by the accuracy harness and the A/B readout alike. Two definitions produce two numbers for the same thing, and then the argument is about the metric instead of about the pipeline.

Accuracy #

Field accuracy compares what the extractor produced against what the customer verified. The per-type data tables (invoice_data for AP bill) are append-only, one row per change, ordered by created_at, each row carrying is_ai_extracted and an action_type. Two rows matter: