Functional standard / Foundation
Operations
Five operations on every resource, plus a short list of named operations. This is the REST surface, in the same role as FHIR's HTTP API.
| Operation | HTTP | Refuses when |
|---|---|---|
| create | POST /v1/{plural} | Validation fails, the actor's role cannot write, an agent targets a resource they may not draft, or a clinical create is attempted by anyone but a clinician |
| read | GET /v1/{plural}/{id} | Wrong site, or a patient actor outside the people they represent, or an agent without ai consent |
| list | GET /v1/{plural} | Same as read. Filters: patient_id, status, encounter_id, definition_key |
| update | PATCH /v1/{plural}/{id} | Frozen, immutable element, harness-owned element, or role |
| transition | POST /v1/{plural}/{id}/transition | The move is not listed. If the target state is gated, the result is 202 and an Approval, not the new state |
| delete | DELETE /v1/{plural}/{id}?reason= | The resource is not deletable, is frozen, or the reason is missing |
Named operations
Some behavior is not a fifth CRUD verb. Each resource page lists its named operations. The ones that apply across the server:
- POST /v1/proposals/{id}/accept and /reject.
- POST /v1/approvals/{id}/decide.
- POST /v1/routines/run and POST /v1/tick for schedules and expiries.
- GET and POST /v1/tools for an agent. Tools call the same operations. They do not skip invariants.
- POST /v1/calculators/{kernel} to score without writing an assessment.
Search is the list filters above. This standard does not define a general search language. A code in an observation is filtered by reading observations for the patient, not by a search parameter grammar.