SaaCIP 0.2: JSON Schemas
The 24 JSON Schemas of SaaCIP 0.2 (draft 2020-12). Each schema's $id is its address here. The files page shows each one in place, with the examples and the validator.
ack-response.schema.json200 response to POST <base>/inbox/ack/: how many of each were marked delivered.ack.schema.jsonPOST <base>/inbox/ack/: what the capability has applied, so the hub stops sending it.approval-request.schema.jsonPOST <base>/approvals/ (autonomy level 2 or above).approval.schema.jsonA declared action waiting for, or given, a person's decision. Returned by POST <base>/approvals/ and listed inattestation.schema.jsonThe hub's signed record of a statement it accepted and of the outcomes it recorded for the hire (section 7.7).capability-manifest.schema.jsonWhat a hirer can read about a capability before hiring it (section 7.1). Usually written as YAML by people andcommon.schema.jsonTypes shared by every SaaCIP document and message.connector-manifest.schema.jsonWhat a connector reads, what it may do, where the data stays and how it signs in (Resident profile, section 4;declared-actions.schema.jsonThe only actions a capability may ever take, written and approved by a person before the hire (section 7.6). Tenrol-request.schema.jsonPOST <base>/enrol/ (HTTP binding, Resident profile section 6, shared with the Hosted profile). Sent once, withenrol-response.schema.json201 response to POST <base>/enrol/.heartbeat-response.schema.json200 response to POST <base>/heartbeat/.heartbeat.schema.jsonPOST <base>/heartbeat/.inbox.schema.json200 response to GET <base>/inbox/: decisions and judgements not yet acknowledged, and whether the hirer askedoutcome.schema.jsonA person's judgement of one work item, delivered back to the capability (section 7.4).problem.schema.jsonEvery error, as RFC 9457 problem details (section 8.7). The type is a URI under https://thesoftwarelens.com/sareceipt.schema.jsonOne signed, chained record of a step the capability took (section 7.3). Stored one per line as canonical JSONrecord.schema.jsonOne record read from a source (Resident profile, section 4).report-response.schema.json201 (created) or 200 (updated or unchanged) response to PUT <base>/work-items/<ref>/.report.schema.jsonPUT <base>/work-items/<ref>/ (HTTP binding, Resident profile section 6, shared with the Hosted profile). The fstatement-request.schema.jsonPOST <base>/statement/. With final true the hire ends; the same final statement may be sent again and changesstatement-response.schema.json200 response to POST <base>/statement/.statement.schema.jsonThe capability's account of a hire, built from its own receipts (section 7.5).terms.schema.jsonThe scope the hirer agrees to for one hire (section 7.2). The terms are the authoritative statement of the hir
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.