THE RECORDSEVEN SECTIONSSIX PAPERS16 SEP 2026 · REV 3
§ 01 · THESIS

No commitment the agreement did not allow.

Korrex stands where a commitment binds. A buyer in a portal, an agent in a tool call, a voice on a line: same rules, same verdict, written once.

FOUR VERDICTS · EVERY ONE WRITTEN TO THE LEDGER
ALLOW Inside cap, on panel, at the rate in force, by an actor with standing. Passes without a question.
ESCALATE The clauses cannot cleanly resolve it. A named human rules, under delegation.
DENY Outside the agreement. Stopped before it becomes a payable.
HELD The actor lacked standing. Held on the prior question, not judged on merit.
WE WILL NOT Do the work. The technician fixes the vehicle, the buyer negotiates, the clerk pays. Korrex witnesses and nothing else.
§ 02 · CLASSIFICATION

Every clause compiles, or is marked uncompiled.

A signed agreement reads into 9 predicates: 7 travel to any industry, 2 assume a fleet. What fits neither is marked CANNOT CLASSIFY, never proxied.

EVERY TEST RUNS AT THE RATE IN FORCE ON THE EVENT DATE
PREDICATECLASSWHAT IT TESTS
amount_vs_cap UNIVERSAL A transaction value against the ceiling a delegation sets.
counterparty_vs_list UNIVERSAL Whether the party sits on the approved list at the event date.
timing_vs_window UNIVERSAL Whether the event fell inside a stated window, and which loading applies.
evidence_present UNIVERSAL Whether the required artefacts were attached before settlement.
price_vs_rate_in_force UNIVERSAL A unit price against the rate in force on the event date.
standing_currency UNIVERSAL Whether the actor held a current mandate at the moment of asking.
duplicate_within_window UNIVERSAL Whether the same economic event has already settled once.
subject_class_eligible DOMAIN Whether the asset class is eligible for the service under the agreement.
boundary_from_telemetry DOMAIN Odometer and service-interval boundaries from telemetry exports.
WE WILL NOT Cite a bare clause number. A finding that cites a clause carries counterparty, agreement, amendment, clause, rule version and the quoted words.
§ 03 · THE MODEL

Authority through agreement, not authoritarian.

Korrex enforces only signed words, and asks first whether the actor was allowed to act. Standing is a known identity, a covering mandate, still in force.

FAIL ONE AND THE EVENT IS HELD · NOT JUDGED ON MERIT
THE LOOPSEVEN STEPS · 07 RETURNS TO 01
01
AGREEMENT
The signed words, in force at a date.
02
RULE
The clause compiled to a test, versioned.
03
JUDGEMENT
One event, one verdict, one trace.
04
ANOMALY
What the rules could not resolve. A finding, never a fault.
05
ADJUDICATION
A named human rules, under delegation.
06
EXCEPTION
Granted, adjudicated, bounded. Never implied.
07
AMENDMENT
The exception compiles forward into the agreement.
THE AMENDMENT COMPILES FORWARD · PROSPECTIVE ONLY
WE WILL NOT Let a human type on more than one tier. Agreements change by amendment; judgements and the ledger are permanently read-only.
§ 04 · HOW IT RUNS

Same rules, two tenses.

Korrex replays 90, 180 or 360 days against the agreements in force on each date. Recovery packs are yours to send, your AP posts the receivable, and the same rules then stand at the gate.

ONE COMPILED CORPUS · RETROSPECTIVE THEN PROSPECTIVE
01AGREEMENTS STANDING STATE Who you agreed with and what the words say. Changes by amendment.
02AUDIT RETROSPECTIVE Replay the past against the agreements in force. Findings, packs, receivable.
03ADVISE PROSPECTIVE Live judgement at the gate: ALLOW, ESCALATE, DENY.
04ACCOUNTS PAYABLE → RECEIVABLE What was stopped, what was recovered, what is contested.
05AUTONOMY TERMINAL STATE Every event judged, every judgement recorded, nobody asked a question.
WE WILL NOT Run the business. Automation does that. The healthy state of an account is an empty queue.
§ 05 · AGENTS

Earned on record, not granted on install.

Korrex brings 4 agents and admits anyone else’s, judged against the same agreements. An agent climbs one rung at a time and loses it on one breach.

AN AGENT HELD BELOW ITS RUNG IS HELD BY A CLAUSE, NOT A CAPABILITY
RUNGWHAT THE AGENT MAY DOWHO SITS HERE
OBSERVE Every act is written to the ledger. The agent proposes nothing. Any admitted agent
ADVISE It proposes; a named human rules every entry. Agent Schedule · Settlement
BOUNDED It may ALLOW inside stated bounds. ESCALATE at the edge. Agent Service · Source
STANDING A current mandate in its own name. Earned by record. None yet
CEILING Settlement, through the ledger at gate 4. Gate 4
WE WILL NOT Score an agent as a model. It is measured as an actor with standing: rulings upheld, escalation burden, dollars denied, bounds breached.
§ 06 · CONVERGENCE

Built to disappear from view.

Year one is the heaviest an account will carry. An anomaly is built to end in a fixed clause or a fixed rule, never in someone keeping an eye on it.

WHAT REMAINS IS THE ENTROPY OF THE BUSINESS · NEW SUPPLIERS, NEW RATES, NEW ACTORS
THE CONVERGENCE CURVEMODELLED · 8 QUARTERS
Q1Q8
ANOMALIES · 118 → 15 SPEND GOVERNED · 12% → 96% ENTROPY FLOOR
WE WILL NOT Charge per review, seat or hour. Korrex charges for standing held, events judged and spend governed — all of which grow as the queue empties.
§ 07 · WHITE PAPER

Authority at the Boundary

ABSTRACT

People, agents and voice lines commit money against signed contracts, and nothing checks the commitment against the contract at the moment it binds. Korrex places that check at the boundary: standing first, then the clause in force on the date.

CONTENTS
I · ENTRYTHE ARGUMENT

Recovery is the wedge.

Korrex enters by replaying a customer’s history against their own agreements and handing back what was lost. Recovery firms take 5 months; Korrex takes the time to compile the corpus.

THE RECOVERY IS WHAT THE CUSTOMER BUYS · THE CORPUS IS THE ASSET
AGREEMENT MATRIX Clauses, amendments, effective dates, rate cards, delegation of authority — each compiled rule traced to its page.
SCHEMA STACK FMS, ERP, card, telematics and document systems: what an event looks like in their world, and where it enters.

By the first recovered dollar, Korrex holds a compiled account of how that customer may spend money. Audit and Authority are the same rules in two tenses.

II · CONVERGENCETHE ARGUMENT

The queue drains by structure, not effort.

A 250-vehicle fleet produces roughly 8,000 judgements a year. At a 5% anomaly rate that is 8 items a week, and year one is the peak.

4 WORK ORDERS PER VEHICLE · 8 JUDGED EVENTS EACH

A ruling is built to resolve permanently: an amendment fixes a stale clause, or the automation is fixed. Nothing resolves into a human watching.

The terminal state is the agreement layer and the automation layer describing the same world. Authority stops interrupting anyone. It has not stopped working.

III · THE METERTHE ARGUMENT

Convergence reads as expansion on the invoice.

A system built to reduce supervision is never priced on supervision. Korrex meters what rises as the queue falls, and the ledger keeps the proof.

EVERY JUDGEMENT MADE · EVERY DOLLAR NOT LOST
METERED Actors holding standing. Events judged. Value of commitments governed.
NEVER METERED Anomalies reviewed. Seats. Hours of attention.
IV · THE PROBLEMTHE FOUNDATIONS

The contract and the behaviour are two artefacts.

A spend cap is a sentence in a PDF and a delegation matrix is a spreadsheet. Both are precise, negotiated, expensive — and silent at the moment they matter.

NOTHING READS THE CAP WHEN A WORK ORDER EXCEEDS IT

Agents close that window. A human exceeds a cap occasionally; an agent exceeds it at machine rate, consistently, with perfect confidence.

Korrex is responsible for making the contract and the behaviour one artefact.

V · PLACEMENTTHE FOUNDATIONS

Only the boundary sees every actor before the commitment binds.

A buyer in a portal, an agent in a tool call, a voice on a line: all three must cross the boundary to have effect, so all three are judged by the same words.

A TOOL-CALL PROTOCOL IS ONE DOOR · PORTALS, LINES AND ERP ENTRY ARE THE OTHERS
AGENT FRAMEWORK Governs only that framework’s agents, written by the team whose incentive is throughput.
ERP Catches the invoice weeks late, after the counterparty has performed.
POLICY DOCUMENT Governs nothing. Nobody reads it at the moment of commitment.
THE BOUNDARY Sees every actor, and sees them before the commitment binds.
VI · STANDINGTHE FOUNDATIONS

Was the actor allowed to act at all?

A work order priced correctly under a valid clause, approved by a role whose delegation lapsed, is still unauthorised. In replay that category can run larger than pricing.

ONE LAPSED DELEGATION · 40 APPROVALS RUN THROUGH IT

Standing is constitutional, not a permission flag: granted, bounded, suspended and revoked by a named human, checked at every event, lost by one breach.

VII · THE TIERSTHE FOUNDATIONS

Who may change what.

Three tiers, told apart by who may type there. An authority the governed party can edit is not an authority.

THE SAME RULE BINDS KORREX · IT RECORDS ACCESS, IT DOES NOT PERFORM THE WORK
AGREEMENT The compiled constitution: clauses, caps, mandates, effective dates, each linked to its source. READ ONLY
ASSURANCE The human tier: judge anomalies, grant and revoke standing, request amendments. INPUT PERMITTED
ADJUDICATION The machine’s judgement and its record. Verdicts are appended, never edited. READ ONLY · PERMANENT

Authority that must be exercised has already failed. The system works when the agreement and the machine describe the same world, and nobody is asked a question.

PAPERSTHE WORKING RECORD

Each paper is the full-depth version of one section above. Written for the reader who wants the mechanism.

NO. TITLESCOPECLASS
KX-01 The Interface Model Surfaces as projections of a private constitution. MODEL READ→ KX-02 The Lineage Model Counterparty → agreement → clause → rule → judgement → entry. MODEL READ→ KX-03 Compilation How a clause becomes a predicate, and what refuses to compile. CLASSIFICATION READ→ KX-04 The Closed Loop Agreement → rule → judgement → anomaly → exception → amendment. MECHANISM READ→ KX-05 The Ledger Appended in order, written once. Corrections cite the old. EVIDENCE READ→ KX-06 Architecture Where Korrex sits between FMS, ERP, suppliers and agents. SYSTEM READ→ — Authority Flow What the logged-in human sees. THE PRODUCT OPEN→
KORREX Publishes the model, never the instance. scan@korrex.ai