TheSoftware LensSee engineering differently

SaaCIP: problem types

Every error in SaaCIP is RFC 9457 problem details. Its type is one of the URIs below, each of the form https://thesoftwarelens.com/saacip/0.1/errors/#<name>. Clients act on status and type, never on the wording of detail. Defined in section 8.7 of the specification; the 0.1 address is the permanent address of each type, and later versions keep it.

TypeHTTP statusMeaning
#invalid-request400The request does not match its schema; errors lists the members.
#unsupported-version400No offered protocol version is supported; supported lists the versions the hub accepts.
#unsupported-profile400The profile is not supported; supported lists the profiles the hub accepts.
#critical-extension400A critical extension is not understood; extensions lists them.
#unauthorised401The credential is missing, unknown or revoked.
#forbidden403This hire may not do that (for example ask for approval at level 1, or hand work to a role not in its terms).
#enrolment-refused403The hub will not accept this capability for a reason of its own.
#not-found404No such item for this hire.
#conflict409The request conflicts with the hub's record: terms that disagree with the hire, or a changed final statement.
#too-large413The request is too large.

Example:

{"type": "https://thesoftwarelens.com/saacip/0.1/errors/#unsupported-version",
 "title": "Unsupported version", "status": 400,
 "detail": "None of the offered protocol versions is supported.",
 "supported": ["saacip/0.2", "saacip/0.1"]}

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.