TheSoftware LensSee engineering differently

saacip/0.2

SaaCIP: the SaaC Interoperability Protocol

The rules under which an organisation hires a software capability: the terms, what it may read and do, how it reports, how a person approves actions, the signed evidence it leaves, the judgement on its work, and the account it gives at the end. Version 0.2 is current; 0.1 stays published as it was.

At a glance

What this isSaaCIP, the SaaC Interoperability Protocol: the rules under which an organisation hires a software capability, from the terms to the signed receipts and the statement at the end. This page is the way in; everything is one click from here.
Who it is forProviders that offer a capability; hirers that run a hub, or an adapter in a help desk they already use; anyone building either side.
StatusVersion 0.2, a draft for comment, published 6 November 2026. Not a standard. Version 0.1 (30 October 2026) stays published unchanged. The examples are for readers to test in their own environment. The reference implementation is not yet public. Version 0.3 will follow.
New in 0.2The hub countersigns statements (attestation); profile-defined outcomes that still compare; capability orchestration through the hub; hirer-issued credentials; the Hosted profile; skill defined against capability; a reference implementation of both sides, not public yet.
Where to goWho does what, in one table · Read the specification · See one hire run · See several hires work together · Browse the registry · Ask the questions people ask

New to SaaCIP? Start here

The specification is written for the people who build either side. You do not need to read it that way. Twenty minutes in the order below gives you the whole idea; the rest is for builders.

If SaaC itself is new to you, two short reads first: From SaaS to SaaC, the idea in one article (you stop buying software and start hiring capabilities that answer for the job), and the SaaCIP article, why a hire needs shared rules. The FAQ answers the first questions in plain words, starting with what SaaC is, in one sentence.

  1. Start on this page. The green panel below tells one hire as a story, with three capabilities in everyday words, and the amber panel says where the AI is and where it is not. Then the seven steps further down, each with an example.
  2. Read the table Who does what. Nine rows: provider, hirer, hub, adapter, capability, the person, the model, the credentials, the registry. Who writes what and who runs what.
  3. Open one CV on the board. Pick Invoice Review. Read the everyday line, the facts, and "One hire, step by step". Every word with a ? explains itself.
  4. In the core, read four sections only: 1, Introduction (why), 3, Overview (the roles, the hire in seven steps, the principles), 5, Lifecycles (the stages a hire, a finding and an action go through) and 9.1, the autonomy levels (how far a capability may go on its own). If you want to know what could go wrong, 11 and 12 are short.
  5. In the profiles, one section each: Resident, section 3, the four rules (the capability comes to your building); Hosted, section 3, the evidence split (what you can check when the work goes to the provider, and what you cannot).
  6. Skip the rest unless you are building: section 4 (technical form), 6 to 8 (documents and calls), 10 (extensibility), the schemas, the validator, the HTTP binding, and anything in a code box. They matter; they are not for you.
  7. When you see a diagram, read the green line under it first. Arrows from left to right are the capability talking to your hub; dotted arrows are the answers; the small boxes on the left are the receipts it writes. Every diagram on this site has that line.

Questions this leaves open are usually answered in the FAQ, in plain words. If a page still reads as if it were written for someone else, say so; that is the feedback this draft needs most.

How a capability gets hired, in seven steps

How a capability gets hired

How a capability gets hiredProviderHirerHubCapability1publishes a manifestwhat it does, reads, may dothe hirer reads it2creates the hirekind, term, who approvesone-time enrolment tokenhands the token to the capability it starts3enrols with its termskind, limits, what leavestermscredential, settings4works and reportseach work item under a refreport, heartbeat5people decideapprove actions, judge workat the hubinbox: decisions, judgements6writes receiptssigned, chained, kept herethe hirer can check them any time7sends its statementand the hire endsstatementthe hirer reads it

The seven steps of section 3.2. Solid arrows are things the capability or a person does; dotted arrows are what comes back. The capability always calls the hub, never the other way round. Open full size

In everyday words: for example, a provider publishes the CV of Invoice Review; your finance lead creates a 14-day trial at your hub (for example, your help desk) and hands over a one-time pass; the capability arrives with its terms; it finds a duplicate invoice and asks to hold the payment; your person approves and later judges the finding; every step leaves a signed line; at the end it hands in its account and your hub countersigns it.

  1. The provider publishes a capability manifest: what it does, what it may read, every action it could ever take, what data leaves.For example: a provider publishes the CV of Invoice Review: it checks every invoice against its order, it may put a payment on hold and nothing else, and no invoice leaves your environment.
  2. The hirer creates a hire at its hub, choosing its kind and how long it lasts, and gets a one-time enrolment token.For example: your finance lead opens your help desk, creates a 14-day trial at level 2 with actions simulated, and gets a one-time pass to hand over.
  3. The capability starts, builds its terms for this hire, and enrols. The hub checks version, profile and terms, and issues a credential.For example: Invoice Review starts inside your network, shows its terms, and is accepted. Your hub gives it its badge for the hire.
  4. The capability works within its terms: it reports work items under refs it chose, and asks approval before any action a person must decide.For example: it finds a duplicate of invoice 4471, writes it up with both invoices side by side, and asks: may I put 4471 on hold?
  5. People decide at the hub. The capability collects their decisions and judgements from its inbox, applies each once, and acknowledges it.For example: your finance person clicks approve on the hold and, a day later, marks the finding as right. The capability acts on the first and learns from the second.
  6. Every step that matters writes a signed, chained receipt, kept where the hirer can check it.For example: the enrolment, the finding, the request, the hold and the judgement are each one signed line in a file on your storage.
  7. The hire ends. The capability sends its final statement, built from its own receipts, and the hub answers with its signed attestation.For example: after 14 days: 3 findings, 2 right, 1 wrong, 1 hold approved. Your hub countersigns it, and you decide whether to make it a standing hire.

Important notice. This page is part of my ongoing research into the Agentic Economy and reflects my thinking at the time of writing. It is shared in good faith, for information and discussion. It is not legal, regulatory, technical, financial or other professional advice, and it is not a verdict on how the EU AI Act or any other law applies to any organisation, system or situation. Laws, guidance, technology and my own research all move on, and others may reach different conclusions. The examples, designs, diagrams and technology choices show one possible approach. Before relying on, adapting or applying any part of it in your own situation, you must test and verify it, design it for your own architecture, and take independent expert advice, including from qualified lawyers and from your own IT, security and data protection specialists. Any decision to act on it, and its consequences, rest with you. To the fullest extent permitted by law, the author accepts no responsibility or liability for any loss, damage or consequence arising from any use of, or reliance on, this page, which is provided without any warranty of accuracy, completeness or fitness for a particular purpose. Reading it does not create a professional or advisory relationship with the author. The views expressed are the author’s own.