SAISA

The standard form for AI agent engagements. Most of a deal like this is the same every time. The form settles that part once, so the only thing left to work through is what actually differs deal to deal — scope, records, limits, and what happens if it goes wrong. Both sides read the same document, and neither side wrote it against the other.

A SAISA is a bilateral service agreement governing a single AI agent engagement. The parties settle, in writing: — Scope of authorized actions (what the agent may and may not do) — Success criteria (how delivery is measured) — Records (what each side has to keep, and to what standard) — Change control (what may be altered after the other side relies on it) — Dispute path (what the parties agreed happens if something goes wrong) Everything above is settled in the base form. Where the two sides of this market genuinely disagree — the warranty standard, the liability cap, who carries what after an incident — the form does not pick a side. It makes the point an election, and records what the parties chose. exact.works presents the form, helps both sides fill it in, and publishes a way to check the result. It is not a party to the agreement and takes no part in the engagement.

Customer                      Provider
──────────────────────────────
Defines scope                 Declares capabilities
Sets success criteria         States what the system does
Accepts or disputes           Performs within the agreed envelope

When the parties are agreed, the terms are hashed canonically.

The agreement can require each side to keep records to a stated standard — hash-chained, gap-detectable, anchored — which ordinary operational telemetry is not built to be. The standard is specified in the agreement, and verification is defined to run on your side, against your own export.