TheSoftware LensSee engineering differently

registry · draft

Hire a capability

Capabilities you can hire under SaaCIP: each one a unit of work with terms, limits a person sets, signed receipts and a statement at the end. Pick one on the left, read its CV the way you would read a candidate's, then hire it for a task, a trial or for good.

Every capability listed today is an example, made up to show the shape, for readers to test in their own environment; version 0.3 of the protocol will follow. The first listing from another provider will be marked as such, and a track record appears only when a hirer's hub has attested a hire. Nothing is bought here and no payment passes through this page.

LW

Log Watch

Example Provider · Operations

ResidentResident: the capability runs inside your own environment, next to your data, like a contractor on site. Hosted: it runs at the provider's and you send it what the terms allow, like work sent to a contractor's office.

Watches your logs so nobody has to

In everyday words: Someone who sits with your systems' logs all night. In the morning you get a note: this service threw a new error forty times since two o'clock, here is the evidence. It may restart that service only if you said in advance that it may, and you can make it ask first every time.

What it would do for you

Watches the logs of named services inside the hirer's environment, reports new error patterns to the hirer's help desk with evidence, and acts only through actions a person declared in advance.

  • Hire asTask: one job, then it leaves. Trial: a fixed number of days, usually with actions only simulated. Standing: it stays until you release it, with interim statements at intervals you agree, say monthly. task, trial, standing
  • AutonomyHow far a capability may go on its own. Level 0: it only observes and keeps notes. Level 1: it reports what it finds and never acts. Level 2: it may act, but only after one of your people approves each action. Level 3: it may act alone, only for actions you marked in advance and within a daily limit you set; anything else it still asks. You choose the level at the start and can lower it at any time. starts at level 1 (report only), up to level 3 (act within limits)
  • ModelWhether the capability uses an AI model, and where that model runs. None means rules do the whole job. none by default; a small model may be allowed by the terms
  • Data that leavesWhat leaves your environment, if anything, written down before the hire starts. In the Resident profile the usual answer is nothing. nothing; redacted work item summaries to the hirer's help desk
  • Track recordHow its past hires were judged, counted from statements that hubs have countersigned. Nothing is shown until a hirer's hub has attested a hire. none attested yet
  • Where the AI is A small model may be used to explain a pattern in plain words, only where the terms allow it. The watching itself is rules, not AI.
What it can do: the declared actionsThe complete list of things this capability could ever do, written in its CV before you hire it. It can never add to the list or run anything that is not on it; a model inside it may only choose from the list.
  • restart-api Rolling restart of a named service; may run alone at level 3
  • clear-tmp Clear temporary files on a named volume; cannot be undone, so it always asks

A model inside the capability, if there is one, may only choose from this list. It cannot add to it or write a command of its own.

What it uses to do the job: rules, parsers, a modelThe tools and methods the capability uses to do its job: a set of rules, a parser, a model. The protocol calls them skills, the way a CV lists a person's skills; the word has nothing to do with any product's feature of that name. Nobody hires a skill and a skill has no terms, limits or receipts of its own. You hire the capability, and the capability uses its skills.
  • log pattern detection (rules)
  • a small model for explaining a pattern, optional, where the terms say

These are the tools and methods inside the capability: rules, parsers, a model where the terms allow one. The protocol calls them skills, as a CV lists a person's skills; the word has nothing to do with any product feature of that name. You hire the capability, not its skills.

What it reads, what stays, what leavesWhat leaves your environment, if anything, written down before the hire starts. In the Resident profile the usual answer is nothing.

Reads through: file, cloud-logs, mcp.

Stays with you: logs, baselines, receipts, signing key: all in the hirer's environment.

Leaves: work item summaries (redacted) to the hirer's help desk; nothing else.

Terms of one hireThe contract of one hire as a file: profile, kind, how long, the autonomy ceiling, whether actions are simulated, what it reads, what leaves, which model, and the credentials by label.

For example: a 14-day trial, ceilingThe highest level this hire may ever reach, fixed in the terms. The capability cannot raise it, and the terms do not change during a hire; a higher ceiling means a new hire with new terms. 2 (act with approval), actions simulatedDuring a trial the capability may be told to only pretend to act: it goes through every step, asks for approval and writes the receipt, but changes nothing. You see how it would behave before you let it act for real.; may hand work to the roleA name you give to a kind of work at your hub, such as incident-resolution. A capability may hand a work item to a role; your hub passes it to whichever hire holds that role. Capabilities never talk to each other. incident-resolution. The hirer set the level to 2 at its hub, so the capability asks before it acts.

Credentials it is given, by labelThe keys the capability needs, which you issue, never the provider. Each is scoped to one source or one action, named by a label (never by its value) in the terms and the receipts, and you can take any of them back at any moment. Reading and acting always use separate keys.

  • logs-reader connector api-logs, read
  • cluster-operator declared actions, one namespace
One hire, step by step, in everyday wordsA signed line for every step that matters, each linked to the one before, kept where you can check it. A chain that verifies shows the record was not changed afterwards.

For example: one made-up hire of this capability, with a help desk as the hub.

  1. Your help desk issues a one-time pass. Log Watch arrives and shows its terms: it reads the api log where it is, nothing leaves except redacted summaries to your help desk, no model is used, the only things it could ever do are a rolling restart of one named service and clearing temporary files on one named volume, and for this trial every action is only simulated. You set its level to 2, so it will ask before it acts.
  2. Every few minutes it tells your hub it is alive and how much it has done so far.
  3. It notices a new error pattern in api, 22 times in a minute, and writes it up with the evidence. A ticket appears at your help desk.
  4. It asks: may I restart api? One of your people reads the ticket and clicks approve.
  5. It checks that nothing has changed since it asked, runs the restart (simulated, because the terms of this trial say so), and writes down that it did.
  6. Your person later marks the finding as real. The capability learns from that.
  7. At the end of the two weeks it hands in its account: 1 finding, 1 judged, 1 accepted. Your hub countersigns it. Every step left a signed line you can check.
Log watch: one hireLog watch: one hireCapabilityHubPeople at the hirer1POST enrol/terms: what it reads, what leaves, model, ceiling, declared actions201: credential, settings, hub keyhire_startedenrolled2POST heartbeat/status, counters, receipt_head200: settingsreads the log in place; groups lines; notices a new pattern3PUT work-items/<ref>/a new error pattern in api, 22 times in a minute201: hub_refa ticket to readwork_item_reported4POST approvals/declared action restart-apiapprove or rejectapproval_requested5GET inbox/the decision, and later the judgement200: approval, outcomere-checks its limits; runs a rolling restart of api (simulated)action_takenjudged: realfeedback_applied6POST inbox/ack/applied once, acknowledged once7POST statement/final: 1 finding, 1 reported, 1 judged, 1 accepted200: ended + attestationhire_endedattestation_receivedAutonomy level 2. Every call is made by the capability; the hub never calls in. Receipts on the left are signed and chained.

The same hire as the seven calls of the protocol, with the receipts the capability writes on the left. Open full size

The CV as a file (manifest, YAML)The capability's CV as a file: what it does, what it reads, every action it could ever take, what data leaves. A provider publishes it; a hirer checks it against the schema before deciding.

The CV as the provider publishes it. Validates against the capability-manifest schema. Download

# Example Log Watch: a made-up capability, to show the shape. Validated against the 0.2 capability-manifest schema.
protocol: saacip/0.2
id: example-log-watch
name: Example Log Watch
version: 1.0.0
provider: Example Provider
description: Watches the logs of named services inside the hirer's environment, reports new error patterns
  to the hirer's help desk with evidence, and acts only through actions a person declared in advance.
profiles:
- resident
hire_kinds:
- task
- trial
- standing
autonomy:
  default: 1
  max: 3
work_items:
  kind: incident
declared_actions:
- id: restart-api
  title: Rolling restart of a named service
  reversible: true
  auto_allowed: true
- id: clear-tmp
  title: Clear temporary files on a named volume
  reversible: false
  auto_allowed: false
data:
  stays: 'logs, baselines, receipts, signing key: all in the hirer''s environment'
  leaves_by_default: nothing; redacted work item summaries to the hirer's help desk
connectors:
- file
- cloud-logs
- mcp
skills:
- log pattern detection (rules)
- a small model for explaining a pattern, optional, where the terms say
handoff_roles:
- incident-resolution
The terms of one hire as a file (JSON)The contract of one hire as a file: profile, kind, how long, the autonomy ceiling, whether actions are simulated, what it reads, what leaves, which model, and the credentials by label.

The contract of one hire, as the capability sends it when it enrols. Validates against the terms schema. Download

{
  "protocol": "saacip/0.2",
  "profile": "resident",
  "kind": "trial",
  "term": {
    "days": 14
  },
  "autonomy_ceiling": 2,
  "dry_run": true,
  "connectors": [
    {
      "protocol": "saacip/0.2",
      "version": "1.0.0",
      "id": "api-logs",
      "kind": "file",
      "signals": [
        "logs"
      ],
      "scopes": [
        "read"
      ],
      "data_location": "a log file on a volume mounted into the capability; read in place",
      "auth": "logs-reader (read-only mount)"
    }
  ],
  "data_leaving": "work item summaries (redacted) to the hirer's help desk; nothing else",
  "model": "offline",
  "public_key": "3RsIo8MiE66DyZ36VRYsLZsEYkt8g4Q5yYToIvLfkNc=",
  "environment": "prod-eu",
  "credentials": [
    {
      "label": "logs-reader",
      "scope": "connector api-logs, read"
    },
    {
      "label": "cluster-operator",
      "scope": "declared actions, one namespace"
    }
  ]
}
TC

Timesheet Check

Example Provider · People and payroll

Hosted or ResidentResident: the capability runs inside your own environment, next to your data, like a contractor on site. Hosted: it runs at the provider's and you send it what the terms allow, like work sent to a contractor's office.

Timesheets complete and correct, every week

In everyday words: An assistant who checks every week that each timesheet is complete and makes sense, and sends a reminder to whoever forgot, once one of your people says go.

What it would do for you

Keeps a hirer's timesheets complete and correct: finds missing and implausible entries each week, reports them, and sends reminders only when a person approves.

  • Hire asTask: one job, then it leaves. Trial: a fixed number of days, usually with actions only simulated. Standing: it stays until you release it, with interim statements at intervals you agree, say monthly. trial, standing
  • AutonomyHow far a capability may go on its own. Level 0: it only observes and keeps notes. Level 1: it reports what it finds and never acts. Level 2: it may act, but only after one of your people approves each action. Level 3: it may act alone, only for actions you marked in advance and within a daily limit you set; anything else it still asks. You choose the level at the start and can lower it at any time. starts at level 1 (report only), up to level 2 (act with approval)
  • ModelWhether the capability uses an AI model, and where that model runs. None means rules do the whole job. none
  • Data that leavesWhat leaves your environment, if anything, written down before the hire starts. In the Resident profile the usual answer is nothing. the week's time entries to the provider's EU environment, deleted after 7 days (Hosted); nothing (Resident)
  • Track recordHow its past hires were judged, counted from statements that hubs have countersigned. Nothing is shown until a hirer's hub has attested a hire. none attested yet
  • Where the AI is No AI at all. Calendar and project-code rules do the whole job.
What it can do: the declared actionsThe complete list of things this capability could ever do, written in its CV before you hire it. It can never add to the list or run anything that is not on it; a model inside it may only choose from the list.
  • send-reminder Send a reminder to the people named in the finding, through the hirer's mail relay; cannot be undone, so it always asks

A model inside the capability, if there is one, may only choose from this list. It cannot add to it or write a command of its own.

What it uses to do the job: rules, parsers, a modelThe tools and methods the capability uses to do its job: a set of rules, a parser, a model. The protocol calls them skills, the way a CV lists a person's skills; the word has nothing to do with any product's feature of that name. Nobody hires a skill and a skill has no terms, limits or receipts of its own. You hire the capability, and the capability uses its skills.
  • calendar and project-code rules

These are the tools and methods inside the capability: rules, parsers, a model where the terms allow one. The protocol calls them skills, as a CV lists a person's skills; the word has nothing to do with any product feature of that name. You hire the capability, not its skills.

What it reads, what stays, what leavesWhat leaves your environment, if anything, written down before the hire starts. In the Resident profile the usual answer is nothing.

Reads through: export, api.

Stays with you: everything stays in the hirer's environment (Resident); nothing is kept at the provider's beyond 7 days (Hosted).

Leaves: the week's time entries (names, dates, hours, project codes) to the provider's EU environment; nothing to any model or other recipient.

Terms of one hireThe contract of one hire as a file: profile, kind, how long, the autonomy ceiling, whether actions are simulated, what it reads, what leaves, which model, and the credentials by label.

For example: a 14-day trial, ceilingThe highest level this hire may ever reach, fixed in the terms. The capability cannot raise it, and the terms do not change during a hire; a higher ceiling means a new hire with new terms. 2 (act with approval), actions simulatedDuring a trial the capability may be told to only pretend to act: it goes through every step, asks for approval and writes the receipt, but changes nothing. You see how it would behave before you let it act for real.. This hire is under the Hosted profile. The hirer set the level to 2 at its hub, so the capability asks first.

Credentials it is given, by labelThe keys the capability needs, which you issue, never the provider. Each is scoped to one source or one action, named by a label (never by its value) in the terms and the receipts, and you can take any of them back at any moment. Reading and acting always use separate keys.

  • timesheets-export connector time-entries, read, renewed daily
  • reminder-sender declared action send-reminder, hirer mail relay
One hire, step by step, in everyday wordsA signed line for every step that matters, each linked to the one before, kept where you can check it. A chain that verifies shows the record was not changed afterwards.

For example: one made-up hire of this capability, with a help desk as the hub.

  1. Your help desk issues a one-time pass. Timesheet Check arrives and shows its terms: it fetches a nightly export of the week's time entries, which go to the provider's EU environment and are deleted after 7 days; no model is used; the only thing it could ever do is send a reminder through your own mail relay; and for this trial reminders are only simulated. You set its level to 2, so it will ask first.
  2. Every few minutes it tells your hub it is alive; each night it says what it has done.
  3. On Friday it finds 11 people with no entries for Thursday and 3 entries that look wrong, and writes them up as two findings. Two tickets appear at your help desk.
  4. It asks: may I send the reminders? One of your people reads the list and clicks approve.
  5. It sends the reminders (simulated, because the terms of this trial say so) and writes down that it did.
  6. Your person later confirms the findings were right. The capability learns from that.
  7. At the end of the trial it hands in its account: 2 findings, 2 judged, 2 accepted. It also says that the entries it held have been deleted. Your hub countersigns the account.
Timesheet check: one hireTimesheet check: one hireCapabilityHubPeople at the hirer1POST enrol/terms: what it reads, what leaves, model, ceiling, declared actions201: credential, settings, hub keyhire_startedenrolled2POST heartbeat/status, counters, receipt_head200: settingsreads the week's export; matches calendar and project codes3PUT work-items/<ref>/11 people with no entries for Thursday; 3 entries that look wrong201: hub_refa ticket to readwork_item_reported4POST approvals/declared action send-reminderapprove or rejectapproval_requested5GET inbox/the decision, and later the judgement200: approval, outcomere-checks its limits; runs the reminders (simulated)action_takenjudged: acceptedfeedback_applied6POST inbox/ack/applied once, acknowledged once7POST statement/final: 2 findings, 2 reported, 2 judged, 2 accepted200: ended + attestationhire_endedattestation_receivedAutonomy level 2. Every call is made by the capability; the hub never calls in. Receipts on the left are signed and chained.

The same hire as the seven calls of the protocol, with the receipts the capability writes on the left. Open full size

The CV as a file (manifest, YAML)The capability's CV as a file: what it does, what it reads, every action it could ever take, what data leaves. A provider publishes it; a hirer checks it against the schema before deciding.

The CV as the provider publishes it. Validates against the capability-manifest schema. Download

# Example Timesheet Check: a made-up capability, to show the shape. Validated against the 0.2 capability-manifest schema.
protocol: saacip/0.2
id: example-timesheet-check
name: Example Timesheet Check
version: 1.0.0
provider: Example Provider
description: 'Keeps a hirer''s timesheets complete and correct: finds missing and implausible entries
  each week, reports them, and sends reminders only when a person approves.'
profiles:
- hosted
- resident
hire_kinds:
- trial
- standing
autonomy:
  default: 1
  max: 2
work_items:
  kind: finding
declared_actions:
- id: send-reminder
  title: Send a reminder to the people named in the finding, through the hirer's mail relay
  reversible: false
  auto_allowed: false
data:
  stays: everything stays in the hirer's environment (Resident); nothing is kept at the provider's
    beyond 7 days (Hosted)
  leaves_by_default: the week's time entries to the provider's EU environment, deleted after 7 days (Hosted);
    nothing (Resident)
connectors:
- export
- api
skills:
- calendar and project-code rules
The terms of one hire as a file (JSON)The contract of one hire as a file: profile, kind, how long, the autonomy ceiling, whether actions are simulated, what it reads, what leaves, which model, and the credentials by label.

The contract of one hire, as the capability sends it when it enrols. Validates against the terms schema. Download

{
  "protocol": "saacip/0.2",
  "profile": "hosted",
  "kind": "trial",
  "term": {
    "days": 14
  },
  "autonomy_ceiling": 2,
  "dry_run": true,
  "connectors": [
    {
      "protocol": "saacip/0.2",
      "version": "1.0.0",
      "id": "time-entries",
      "kind": "export",
      "signals": [
        "changes"
      ],
      "scopes": [
        "read"
      ],
      "data_location": "the hirer's time-logging system; a nightly export fetched to the provider's EU environment, deleted after 7 days",
      "auth": "timesheets-export (hirer-issued, renewed daily)"
    }
  ],
  "data_leaving": "the week's time entries (names, dates, hours, project codes) to the provider's EU environment; nothing to any model or other recipient",
  "model": "offline",
  "public_key": "3RsIo8MiE66DyZ36VRYsLZsEYkt8g4Q5yYToIvLfkNc=",
  "environment": "provider-eu",
  "credentials": [
    {
      "label": "timesheets-export",
      "scope": "connector time-entries, read, renewed daily"
    },
    {
      "label": "reminder-sender",
      "scope": "declared action send-reminder, hirer mail relay"
    }
  ]
}
IR

Invoice Review

Example Provider · Finance

ResidentResident: the capability runs inside your own environment, next to your data, like a contractor on site. Hosted: it runs at the provider's and you send it what the terms allow, like work sent to a contractor's office.

Every invoice matched before it is paid

In everyday words: A clerk who checks every supplier invoice against the order and past invoices before it is paid, and flags duplicates and odd amounts. It can put a payment on hold, but only after one of your people clicks approve.

What it would do for you

Reviews incoming supplier invoices against purchase orders and past invoices, reports duplicates, mismatches and unusual amounts, and holds a payment only when a person approves.

  • Hire asTask: one job, then it leaves. Trial: a fixed number of days, usually with actions only simulated. Standing: it stays until you release it, with interim statements at intervals you agree, say monthly. trial, standing
  • AutonomyHow far a capability may go on its own. Level 0: it only observes and keeps notes. Level 1: it reports what it finds and never acts. Level 2: it may act, but only after one of your people approves each action. Level 3: it may act alone, only for actions you marked in advance and within a daily limit you set; anything else it still asks. You choose the level at the start and can lower it at any time. starts at level 1 (report only), up to level 2 (act with approval)
  • ModelWhether the capability uses an AI model, and where that model runs. None means rules do the whole job. a document model in the hirer's own cloud account
  • Data that leavesWhat leaves your environment, if anything, written down before the hire starts. In the Resident profile the usual answer is nothing. nothing; findings to the hirer's finance queue
  • Track recordHow its past hires were judged, counted from statements that hubs have countersigned. Nothing is shown until a hirer's hub has attested a hire. none attested yet
  • Where the AI is A document model reads invoices that arrive as scans or free text. It runs in your own cloud account, so no invoice leaves your environment.
What it can do: the declared actionsThe complete list of things this capability could ever do, written in its CV before you hire it. It can never add to the list or run anything that is not on it; a model inside it may only choose from the list.
  • hold-payment Put a named invoice on hold in the hirer's payables system

A model inside the capability, if there is one, may only choose from this list. It cannot add to it or write a command of its own.

What it uses to do the job: rules, parsers, a modelThe tools and methods the capability uses to do its job: a set of rules, a parser, a model. The protocol calls them skills, the way a CV lists a person's skills; the word has nothing to do with any product's feature of that name. Nobody hires a skill and a skill has no terms, limits or receipts of its own. You hire the capability, and the capability uses its skills.
  • three-way matching rules
  • a model in the hirer's account for reading unstructured invoices

These are the tools and methods inside the capability: rules, parsers, a model where the terms allow one. The protocol calls them skills, as a CV lists a person's skills; the word has nothing to do with any product feature of that name. You hire the capability, not its skills.

What it reads, what stays, what leavesWhat leaves your environment, if anything, written down before the hire starts. In the Resident profile the usual answer is nothing.

Reads through: api, mcp.

Stays with you: invoices, purchase orders and the model: all in the hirer's environment.

Leaves: nothing; a model in the hirer's own cloud account reads invoice text.

Terms of one hireThe contract of one hire as a file: profile, kind, how long, the autonomy ceiling, whether actions are simulated, what it reads, what leaves, which model, and the credentials by label.

For example: a 14-day trial, ceilingThe highest level this hire may ever reach, fixed in the terms. The capability cannot raise it, and the terms do not change during a hire; a higher ceiling means a new hire with new terms. 2 (act with approval), actions simulatedDuring a trial the capability may be told to only pretend to act: it goes through every step, asks for approval and writes the receipt, but changes nothing. You see how it would behave before you let it act for real.; may hand work to the roleA name you give to a kind of work at your hub, such as incident-resolution. A capability may hand a work item to a role; your hub passes it to whichever hire holds that role. Capabilities never talk to each other. finance-review. The hirer set the level to 2 at its hub, so the capability asks first.

Credentials it is given, by labelThe keys the capability needs, which you issue, never the provider. Each is scoped to one source or one action, named by a label (never by its value) in the terms and the receipts, and you can take any of them back at any moment. Reading and acting always use separate keys.

  • payables-reader connector payables, read
  • payables-holder declared action hold-payment
One hire, step by step, in everyday wordsA signed line for every step that matters, each linked to the one before, kept where you can check it. A chain that verifies shows the record was not changed afterwards.

For example: one made-up hire of this capability, with a help desk as the hub.

  1. Your help desk issues a one-time pass. Invoice Review arrives and shows its terms: it reads your payables system from inside your network, a document model in your own cloud account reads scanned invoices, nothing leaves, the only thing it could ever do is put a named invoice on hold, and for this trial a hold is only simulated. You set its level to 2, so it will ask first.
  2. Every few minutes it tells your hub it is alive and how many invoices it has checked so far.
  3. It finds that invoice 4471 repeats an invoice from the same supplier that was paid three weeks earlier, and writes it up with both invoices side by side. A ticket appears in your finance queue.
  4. It asks: may I put invoice 4471 on hold? One of your people in finance reads the ticket and clicks approve.
  5. It checks that nothing has changed since it asked and that the invoice is still unpaid, records the hold (simulated, because the terms of this trial say so), and writes down that it did.
  6. Over the two weeks it reports three findings. Your person judges two right and one wrong. The capability learns from that, and the miss counts against its record.
  7. At the end of the trial it hands in its account: 3 findings, 3 judged, 2 accepted, 1 rejected, 1 hold approved and simulated. Your hub countersigns it. If you then take it on as a standing hire, the accounts come at intervals you agree, say monthly.
Invoice review: one hireInvoice review: one hireCapabilityHubPeople at the hirer1POST enrol/terms: what it reads, what leaves, model, ceiling, declared actions201: credential, settings, hub keyhire_startedenrolled2POST heartbeat/status, counters, receipt_head200: settingsmatches invoices to orders; a model in the hirer's account reads PDFs3PUT work-items/<ref>/invoice 4471 repeats one already paid to the same supplier201: hub_refa ticket to readwork_item_reported4POST approvals/declared action hold-paymentapprove or rejectapproval_requested5GET inbox/the decision, and later the judgement200: approval, outcomere-checks its limits; runs a hold on the invoice (simulated)action_takenjudged: acceptedfeedback_applied6POST inbox/ack/applied once, acknowledged once7POST statement/final: 3 findings, 3 reported, 3 judged, 2 accepted, 1 rejected200: ended + attestationhire_endedattestation_receivedAutonomy level 2. Every call is made by the capability; the hub never calls in. Receipts on the left are signed and chained.

The same hire as the seven calls of the protocol, with the receipts the capability writes on the left. Open full size

The CV as a file (manifest, YAML)The capability's CV as a file: what it does, what it reads, every action it could ever take, what data leaves. A provider publishes it; a hirer checks it against the schema before deciding.

The CV as the provider publishes it. Validates against the capability-manifest schema. Download

# Example Invoice Review: a made-up capability, to show the shape. Validated against the 0.2 capability-manifest schema.
protocol: saacip/0.2
id: example-invoice-review
name: Example Invoice Review
version: 1.0.0
provider: Example Provider
description: Reviews incoming supplier invoices against purchase orders and past invoices, reports duplicates,
  mismatches and unusual amounts, and holds a payment only when a person approves.
profiles:
- resident
hire_kinds:
- trial
- standing
autonomy:
  default: 1
  max: 2
work_items:
  kind: finding
declared_actions:
- id: hold-payment
  title: Put a named invoice on hold in the hirer's payables system
  reversible: true
  auto_allowed: false
data:
  stays: 'invoices, purchase orders and the model: all in the hirer''s environment'
  leaves_by_default: nothing; findings to the hirer's finance queue
connectors:
- api
- mcp
skills:
- three-way matching rules
- a model in the hirer's account for reading unstructured invoices
handoff_roles:
- finance-review
The terms of one hire as a file (JSON)The contract of one hire as a file: profile, kind, how long, the autonomy ceiling, whether actions are simulated, what it reads, what leaves, which model, and the credentials by label.

The contract of one hire, as the capability sends it when it enrols. Validates against the terms schema. Download

{
  "protocol": "saacip/0.2",
  "profile": "resident",
  "kind": "trial",
  "term": {
    "days": 14
  },
  "autonomy_ceiling": 2,
  "dry_run": true,
  "connectors": [
    {
      "protocol": "saacip/0.2",
      "version": "1.0.0",
      "id": "payables",
      "kind": "api",
      "signals": [
        "changes"
      ],
      "scopes": [
        "read",
        "act"
      ],
      "operations": [
        "hold"
      ],
      "data_location": "the hirer's payables system, read through its API from inside the hirer's network",
      "auth": "payables-reader (read) and payables-holder (act)"
    }
  ],
  "data_leaving": "nothing; a model in the hirer's own cloud account reads invoice text",
  "model": "a document model in the hirer's own cloud account",
  "public_key": "3RsIo8MiE66DyZ36VRYsLZsEYkt8g4Q5yYToIvLfkNc=",
  "environment": "finance-eu",
  "credentials": [
    {
      "label": "payables-reader",
      "scope": "connector payables, read"
    },
    {
      "label": "payables-holder",
      "scope": "declared action hold-payment"
    }
  ],
  "handoff_roles": [
    "finance-review"
  ]
}
BV

Backup Verify

Example Provider · Operations

ResidentResident: the capability runs inside your own environment, next to your data, like a contractor on site. Hosted: it runs at the provider's and you send it what the terms allow, like work sent to a contractor's office.

Proof, every night, that backups restore

In everyday words: Someone who checks every night that the backups ran, that they can be restored, and that none was skipped, and tells you what was not right. It may re-run a failed backup job within limits you set.

What it would do for you

Checks every night that the hirer's backups completed, are restorable and match their schedule, reports what did not, and re-runs a failed backup job only within declared limits.

  • Hire asTask: one job, then it leaves. Trial: a fixed number of days, usually with actions only simulated. Standing: it stays until you release it, with interim statements at intervals you agree, say monthly. trial, standing
  • AutonomyHow far a capability may go on its own. Level 0: it only observes and keeps notes. Level 1: it reports what it finds and never acts. Level 2: it may act, but only after one of your people approves each action. Level 3: it may act alone, only for actions you marked in advance and within a daily limit you set; anything else it still asks. You choose the level at the start and can lower it at any time. starts at level 1 (report only), up to level 3 (act within limits)
  • ModelWhether the capability uses an AI model, and where that model runs. None means rules do the whole job. none
  • Data that leavesWhat leaves your environment, if anything, written down before the hire starts. In the Resident profile the usual answer is nothing. nothing; incidents to the hirer's help desk
  • Track recordHow its past hires were judged, counted from statements that hubs have countersigned. Nothing is shown until a hirer's hub has attested a hire. none attested yet
  • Where the AI is No AI. Schedules and checksums are checked by rules.
What it can do: the declared actionsThe complete list of things this capability could ever do, written in its CV before you hire it. It can never add to the list or run anything that is not on it; a model inside it may only choose from the list.
  • rerun-backup Re-run a named backup job; may run alone at level 3

A model inside the capability, if there is one, may only choose from this list. It cannot add to it or write a command of its own.

What it uses to do the job: rules, parsers, a modelThe tools and methods the capability uses to do its job: a set of rules, a parser, a model. The protocol calls them skills, the way a CV lists a person's skills; the word has nothing to do with any product's feature of that name. Nobody hires a skill and a skill has no terms, limits or receipts of its own. You hire the capability, and the capability uses its skills.
  • schedule and checksum rules

These are the tools and methods inside the capability: rules, parsers, a model where the terms allow one. The protocol calls them skills, as a CV lists a person's skills; the word has nothing to do with any product feature of that name. You hire the capability, not its skills.

What it reads, what stays, what leavesWhat leaves your environment, if anything, written down before the hire starts. In the Resident profile the usual answer is nothing.

Reads through: cloud-logs, api.

Stays with you: backup catalogues, test-restore results, receipts: in the hirer's environment.

Leaves: nothing; incident summaries to the hirer's help desk.

Terms of one hireThe contract of one hire as a file: profile, kind, how long, the autonomy ceiling, whether actions are simulated, what it reads, what leaves, which model, and the credentials by label.

For example: a standing hire, ceilingThe highest level this hire may ever reach, fixed in the terms. The capability cannot raise it, and the terms do not change during a hire; a higher ceiling means a new hire with new terms. 3 (act within limits), actions real; may hand work to the roleA name you give to a kind of work at your hub, such as incident-resolution. A capability may hand a work item to a role; your hub passes it to whichever hire holds that role. Capabilities never talk to each other. incident-resolution. This hire followed a 30-day trial at level 2 with actions simulated. The hirer then set the level to 3 and a limit of one automatic re-run a day.

Credentials it is given, by labelThe keys the capability needs, which you issue, never the provider. Each is scoped to one source or one action, named by a label (never by its value) in the terms and the receipts, and you can take any of them back at any moment. Reading and acting always use separate keys.

  • backup-reader connector backup-catalogue, read
  • backup-runner declared action rerun-backup, two named jobs
One hire, step by step, in everyday wordsA signed line for every step that matters, each linked to the one before, kept where you can check it. A chain that verifies shows the record was not changed afterwards.

For example: one made-up hire of this capability, with a help desk as the hub.

  1. Your help desk issues a one-time pass. Backup Verify arrives and shows its terms: it reads the backup catalogue from inside your account, no model is used, the only thing it could ever do is re-run one of two named backup jobs, and because you trust it at level 3 after its trial, it may do that alone, at most once a day.
  2. Every few minutes it tells your hub it is alive; each night it says what it checked.
  3. It finds that last night's job for the orders database did not complete, and writes it up. A ticket appears at your help desk.
  4. At level 3 it does not need to ask for this job: it re-runs it, within its limit, and writes down that it did. The ticket shows the action.
  5. The re-run completes; the capability writes down what happened.
  6. Your person later marks the finding as real and the re-run as having worked.
  7. The account comes at intervals you agree, monthly in this example: 1 finding, 1 judged, 1 accepted, 1 action taken alone. Your hub may countersign these interim accounts, and it always countersigns the final one. You can lower the level to 2 at any time so that it asks first.
Backup verify: one hire (level 3)Backup verify: one hire (level 3)CapabilityHubPeople at the hirer1POST enrol/terms: what it reads, what leaves, model, ceiling, declared actions201: credential, settings, hub keyhire_startedenrolled2POST heartbeat/status, counters, receipt_head200: settingschecks the catalogue and a test restore every night3PUT work-items/<ref>/last night's job for the orders database did not complete201: hub_refa ticket to readwork_item_reportedreversible, auto_allowed, within max_per_day: runs rerun-backup aloneaction_taken4PUT work-items/<ref>/a note on the item: what it did and the result200: updatedwhat was donework_item_updated5GET inbox/the judgement, when a person has made it200: outcomejudged: real, the re-run workedfeedback_applied6POST inbox/ack/applied once, acknowledged once7POST statement/interim: 1 finding, 1 reported, 1 judged, 1 accepted, 1 action alone200: acceptedAutonomy level 3: it acts alone only within the limits the hirer set, and otherwise asks. Receipts on the left are signed and chained.

The same hire as the seven calls of the protocol, with the receipts the capability writes on the left. Open full size

The CV as a file (manifest, YAML)The capability's CV as a file: what it does, what it reads, every action it could ever take, what data leaves. A provider publishes it; a hirer checks it against the schema before deciding.

The CV as the provider publishes it. Validates against the capability-manifest schema. Download

# Example Backup Verify: a made-up capability, to show the shape. Validated against the 0.2 capability-manifest schema.
protocol: saacip/0.2
id: example-backup-verify
name: Example Backup Verify
version: 1.0.0
provider: Example Provider
description: Checks every night that the hirer's backups completed, are restorable and match their schedule,
  reports what did not, and re-runs a failed backup job only within declared limits.
profiles:
- resident
hire_kinds:
- trial
- standing
autonomy:
  default: 1
  max: 3
work_items:
  kind: incident
declared_actions:
- id: rerun-backup
  title: Re-run a named backup job
  reversible: true
  auto_allowed: true
data:
  stays: 'backup catalogues, test-restore results, receipts: in the hirer''s environment'
  leaves_by_default: nothing; incidents to the hirer's help desk
connectors:
- cloud-logs
- api
skills:
- schedule and checksum rules
handoff_roles:
- incident-resolution
The terms of one hire as a file (JSON)The contract of one hire as a file: profile, kind, how long, the autonomy ceiling, whether actions are simulated, what it reads, what leaves, which model, and the credentials by label.

The contract of one hire, as the capability sends it when it enrols. Validates against the terms schema. Download

{
  "protocol": "saacip/0.2",
  "profile": "resident",
  "kind": "standing",
  "term": null,
  "autonomy_ceiling": 3,
  "dry_run": false,
  "connectors": [
    {
      "protocol": "saacip/0.2",
      "version": "1.0.0",
      "id": "backup-catalogue",
      "kind": "api",
      "signals": [
        "changes",
        "logs"
      ],
      "scopes": [
        "read"
      ],
      "data_location": "the backup service's catalogue, read from inside the hirer's account",
      "auth": "backup-reader"
    }
  ],
  "data_leaving": "nothing; incident summaries to the hirer's help desk",
  "model": "offline",
  "public_key": "3RsIo8MiE66DyZ36VRYsLZsEYkt8g4Q5yYToIvLfkNc=",
  "environment": "ops-eu",
  "credentials": [
    {
      "label": "backup-reader",
      "scope": "connector backup-catalogue, read"
    },
    {
      "label": "backup-runner",
      "scope": "declared action rerun-backup, two named jobs"
    }
  ],
  "handoff_roles": [
    "incident-resolution"
  ]
}
CE

Certificate Expiry

Example Provider · Security and platform

Resident or HostedResident: the capability runs inside your own environment, next to your data, like a contractor on site. Hosted: it runs at the provider's and you send it what the terms allow, like work sent to a contractor's office.

No certificate expires unnoticed

In everyday words: Someone who keeps a list of every certificate and domain you own, warns you weeks before one expires, and renews it through your own tooling when you approve.

What it would do for you

Watches the hirer's TLS certificates and domains for expiry and misconfiguration, reports with enough notice to act, and renews a certificate through the hirer's own tooling when approved.

  • Hire asTask: one job, then it leaves. Trial: a fixed number of days, usually with actions only simulated. Standing: it stays until you release it, with interim statements at intervals you agree, say monthly. trial, standing
  • AutonomyHow far a capability may go on its own. Level 0: it only observes and keeps notes. Level 1: it reports what it finds and never acts. Level 2: it may act, but only after one of your people approves each action. Level 3: it may act alone, only for actions you marked in advance and within a daily limit you set; anything else it still asks. You choose the level at the start and can lower it at any time. starts at level 1 (report only), up to level 3 (act within limits)
  • ModelWhether the capability uses an AI model, and where that model runs. None means rules do the whole job. none
  • Data that leavesWhat leaves your environment, if anything, written down before the hire starts. In the Resident profile the usual answer is nothing. public certificate metadata only (Hosted); nothing (Resident)
  • Track recordHow its past hires were judged, counted from statements that hubs have countersigned. Nothing is shown until a hirer's hub has attested a hire. none attested yet
  • Where the AI is No AI. Certificates are parsed and dates compared by rules.
What it can do: the declared actionsThe complete list of things this capability could ever do, written in its CV before you hire it. It can never add to the list or run anything that is not on it; a model inside it may only choose from the list.
  • renew-cert Renew a named certificate through the hirer's issuer; may run alone at level 3

A model inside the capability, if there is one, may only choose from this list. It cannot add to it or write a command of its own.

What it uses to do the job: rules, parsers, a modelThe tools and methods the capability uses to do its job: a set of rules, a parser, a model. The protocol calls them skills, the way a CV lists a person's skills; the word has nothing to do with any product's feature of that name. Nobody hires a skill and a skill has no terms, limits or receipts of its own. You hire the capability, and the capability uses its skills.
  • certificate parsing

These are the tools and methods inside the capability: rules, parsers, a model where the terms allow one. The protocol calls them skills, as a CV lists a person's skills; the word has nothing to do with any product feature of that name. You hire the capability, not its skills.

What it reads, what stays, what leavesWhat leaves your environment, if anything, written down before the hire starts. In the Resident profile the usual answer is nothing.

Reads through: api, cloud-logs.

Stays with you: certificate inventories and receipts in the hirer's environment (Resident).

Leaves: nothing (Resident); public certificate metadata only (Hosted).

Terms of one hireThe contract of one hire as a file: profile, kind, how long, the autonomy ceiling, whether actions are simulated, what it reads, what leaves, which model, and the credentials by label.

For example: a 30-day trial, ceilingThe highest level this hire may ever reach, fixed in the terms. The capability cannot raise it, and the terms do not change during a hire; a higher ceiling means a new hire with new terms. 3 (act within limits), actions simulatedDuring a trial the capability may be told to only pretend to act: it goes through every step, asks for approval and writes the receipt, but changes nothing. You see how it would behave before you let it act for real.. This hire is under the Resident profile. The hirer set the level to 2 at its hub for the trial, so the capability asks first.

Credentials it is given, by labelThe keys the capability needs, which you issue, never the provider. Each is scoped to one source or one action, named by a label (never by its value) in the terms and the receipts, and you can take any of them back at any moment. Reading and acting always use separate keys.

  • cert-reader connector cert-inventory, read
  • cert-renewer declared action renew-cert, the hirer's issuer
One hire, step by step, in everyday wordsA signed line for every step that matters, each linked to the one before, kept where you can check it. A chain that verifies shows the record was not changed afterwards.

For example: one made-up hire of this capability, with a help desk as the hub.

  1. Your help desk issues a one-time pass. Certificate Expiry arrives and shows its terms: it reads your certificate inventory and your public endpoints, no model is used, the only thing it could ever do is renew a named certificate through your own issuer, and for this trial renewals are only simulated. You set its level to 2, so it will ask first.
  2. Every few minutes it tells your hub it is alive; each day it says how many certificates it checked.
  3. It finds that api.example.test expires in 21 days and that one domain has a mismatched chain, and writes both up. Two tickets appear at your help desk.
  4. It asks: may I renew api.example.test? One of your people reads the ticket and clicks approve.
  5. It runs the renewal through your issuer (simulated, because the terms of this trial say so) and writes down that it did.
  6. Your person later confirms both findings were right.
  7. At the end of the 30-day trial it hands in its account: 2 findings, 2 judged, 2 accepted. Your hub countersigns it.
Certificate expiry: one hireCertificate expiry: one hireCapabilityHubPeople at the hirer1POST enrol/terms: what it reads, what leaves, model, ceiling, declared actions201: credential, settings, hub keyhire_startedenrolled2POST heartbeat/status, counters, receipt_head200: settingsreads the inventory and the public endpoints; parses each certificate3PUT work-items/<ref>/api.example.test expires in 21 days; one domain has a mismatched chain201: hub_refa ticket to readwork_item_reported4POST approvals/declared action renew-certapprove or rejectapproval_requested5GET inbox/the decision, and later the judgement200: approval, outcomere-checks its limits; runs the renewal (simulated)action_takenjudged: acceptedfeedback_applied6POST inbox/ack/applied once, acknowledged once7POST statement/final: 2 findings, 2 reported, 2 judged, 2 accepted200: ended + attestationhire_endedattestation_receivedAutonomy level 2. Every call is made by the capability; the hub never calls in. Receipts on the left are signed and chained.

The same hire as the seven calls of the protocol, with the receipts the capability writes on the left. Open full size

The CV as a file (manifest, YAML)The capability's CV as a file: what it does, what it reads, every action it could ever take, what data leaves. A provider publishes it; a hirer checks it against the schema before deciding.

The CV as the provider publishes it. Validates against the capability-manifest schema. Download

# Example Certificate Expiry: a made-up capability, to show the shape. Validated against the 0.2 capability-manifest schema.
protocol: saacip/0.2
id: example-cert-expiry
name: Example Certificate Expiry
version: 1.0.0
provider: Example Provider
description: Watches the hirer's TLS certificates and domains for expiry and misconfiguration, reports
  with enough notice to act, and renews a certificate through the hirer's own tooling when approved.
profiles:
- resident
- hosted
hire_kinds:
- trial
- standing
autonomy:
  default: 1
  max: 3
work_items:
  kind: finding
declared_actions:
- id: renew-cert
  title: Renew a named certificate through the hirer's issuer
  reversible: true
  auto_allowed: true
data:
  stays: certificate inventories and receipts in the hirer's environment (Resident)
  leaves_by_default: public certificate metadata only (Hosted); nothing (Resident)
connectors:
- api
- cloud-logs
skills:
- certificate parsing
The terms of one hire as a file (JSON)The contract of one hire as a file: profile, kind, how long, the autonomy ceiling, whether actions are simulated, what it reads, what leaves, which model, and the credentials by label.

The contract of one hire, as the capability sends it when it enrols. Validates against the terms schema. Download

{
  "protocol": "saacip/0.2",
  "profile": "resident",
  "kind": "trial",
  "term": {
    "days": 30
  },
  "autonomy_ceiling": 3,
  "dry_run": true,
  "connectors": [
    {
      "protocol": "saacip/0.2",
      "version": "1.0.0",
      "id": "cert-inventory",
      "kind": "api",
      "signals": [
        "changes"
      ],
      "scopes": [
        "read"
      ],
      "data_location": "the hirer's certificate inventory and public endpoints, read from inside",
      "auth": "cert-reader"
    }
  ],
  "data_leaving": "nothing",
  "model": "offline",
  "public_key": "3RsIo8MiE66DyZ36VRYsLZsEYkt8g4Q5yYToIvLfkNc=",
  "environment": "platform-eu",
  "credentials": [
    {
      "label": "cert-reader",
      "scope": "connector cert-inventory, read"
    },
    {
      "label": "cert-renewer",
      "scope": "declared action renew-cert, the hirer's issuer"
    }
  ]
}

How a hire works, in four moves

  1. Read the CV. It says what the capability does, what it reads, what leaves, which model if any, and the only actions it could ever take. For example: Invoice Review checks every invoice against its order, may put a payment on hold, and nothing leaves your environment.
  2. Create the hire at your hub and hand the capability a one-time pass. Your hub can be the reference hub or an adapter in the help desk you already run. For example: a 14-day trial at level 2, actions simulated.
  3. Let it work under terms you set. It reports what it finds, asks before it acts, one of your people approves or rejects, and judges each finding. For example: it finds a duplicate invoice, asks to hold the payment, your finance person clicks approve.
  4. Read the statement at the end, countersigned by your hub, and decide: a standing hire, or not. For example: 3 findings, 2 right, 1 wrong, 1 hold approved; you keep it, or you let it go.

See a whole hire run Read how the protocol works

List a capability

Publish a manifest that validates against the schema, then say so. The entry carries your manifest at its own address and nothing else until a hirer's hub attests a hire. Listing is free and carries no endorsement.

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.