Ingestion and Deterministic Matching

Ingestion and Deterministic Matching An architecture diagram generated by Archify. Source systems · usage, billing, rate card · Architecture component · fixture-backed today Source systems usage, billing, rate card fixture-backed today Connectors · typed source reads · Architecture component · MCP boundary Connectors typed source reads MCP boundary Fact store · immutable versions · Architecture component · Postgres Fact store immutable versions Postgres Matcher · rate + tolerance · Architecture component · deterministic Matcher rate + tolerance deterministic Outcome · settlement or case · Architecture component · residue only Outcome settlement or case residue only source records normalised facts current evidence settle or triage Legend Backend Database External

Fact first

  • • Source-native records become immutable, provenance-stamped facts
  • • Current matching uses the latest fact version

Clear cases exit

  • • Within-tolerance correspondences settle without review
  • • Only disagreement or ambiguity becomes a case

No model decides the match

  • • Rates, usage, and tolerance produce deterministic outcomes
  • • Model-assisted workflows begin after matching leaves residue