SAP
The write path into your ERP is the most dangerous place an agent can operate. Three rules make it survivable — and none of them are optional.
SAP is where your company's truth lives: payments, orders, inventory, postings. An agent that writes there casually is not an assistant — it is an unvetted intern with root access. Here is the full set of rules Kernos enforces between "the agent had an idea" and "SAP changed".
You send a BAPI call. The network says 200. Is the payment posted? You do not know yet. Kernos treats every write as staged until SAP's own authoritative event — the IDoc confirmation, the OData response from the real system of record — says otherwise. Anything less is optimistic fiction, and optimistic fiction in an ERP becomes someone's month-end reconciliation nightmare.
SAP goes down for maintenance. The queue grows. The pressure to "just write it through anyway" is enormous — and this is precisely the moment governance earns its keep. Kernos offers two degradation modes, chosen per control point: recoverable hold (queue and replay when SAP returns) or strict block (halt the process entirely). What it never does is route around the approval loop to keep throughput up.
Three-way reconciliation runs continuously: platform state versus SAP state versus field evidence. When they disagree, the discrepancy becomes a tracked item with an owner — not silent drift discovered at audit time. Retries are idempotent (no duplicate postings), failures land in dead-letter queues, and the entire chain is replayable from the bi-temporal audit trail.
This is not theoretical middleware. Kernos connects through the standard SAP interface families — OData, IDoc, BAPI, events, and CDC — with MDM external-ID mapping so your ontology objects and SAP master data stay the same thing. No custom ABAP in your core system, and full coverage of the read-and-write path. The long-form version lives on the SAP integration page.
Agent platforms are racing to add "SAP connectors" that move data. Moving data is the easy part — connectors are a solved problem. The unsolved part is authority: who approved this change, under which policy, with what evidence, and how do you undo it. That is the layer Kernos was built to be.