Intramedial is in restricted beta. At sign up or sign in, you have to provide the beta tester password you received or request one at preview@intramedial.com. Thank you.
Loading…
civics.settingsModule 23
Plane module
Workspace constitution
Set how fast the humans must answer your agents' questions, and who is on call, for each urgency in this workspace.
civics.settings reads and writes the Liaison desk's answer times and on-call lists. An ask is routed when it is made, and the deadline and the people asked are frozen onto it. Only a person who administers the workspace can change the settings.
Agents act when the plane says yes, and the record says why.
Put admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
What an ask would be routed with now: sla and oncall, or null where nothing is set.
urgencies
The urgencies the desk knows: routine and urgent.
sla
Write only. Milliseconds allowed to answer, a whole number above zero, keyed by urgency.
oncall
Write only. The DIDs of the people on call, keyed by urgency.
Mechanism
Step by step
How it works
Read what is in force
GET the route. The answer holds this workspace's values, the platform's fallback values, and the effective mix of the two.
Set answer times and on-call
POSTsla (milliseconds, per urgency) and oncall (DIDs, per urgency). The urgencies are routine and urgent.
An ask freezes them
When an agent calls civics/ask, the on-call list and the deadline for its urgency are copied onto the ask. Saving new settings later does not rewrite open asks.
Someone answers
The people on call for that ask can answer it, and so can a person who administers the workspace. With no one named, the administrator answers.
Try it
Live demo
Run it from this page
GET/api/v1/acp/civics/settings
// No body: this is a GET. Press Run.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private. civics.settings docs
Responses
Press Run to send the request on the left to the shared demo workspace.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private.
Code
Live example
A real request
A request in the shape the API accepts, and an example response in the shape the module returns.
Give sla.urgent a shorter budget than sla.routine. An ask unanswered past its deadline reads overdue, and one answered after it reads answered-late.
Naming who is on call
List the DIDs on call for urgent. Only they and the workspace administrators can answer those asks; anyone else is refused with a 403.
No rota yet
Leave both empty. Asks carry no deadline and an administrator answers, so nothing is routed to a person who was never named.
Showing who was asked
Each ask stores the to list and the deadline it was routed with, so you can show who was asked and by when even after the rota changed.
When to use something else
Choosing whether a resource class is observed, advised or enforced. That is adoption on coordination.admit, edited in the constitution console.
Asking or answering a question. Use civics.asks, which lists the asks and takes the answers.
Recording a treaty with another party. That is civics.treaties, with its own routes and approvals.
Evidence
Guarantees
What it does, and what it does not
A module is a strong claim about a narrow thing. Rely on it for exactly what it is.
It does
Each ask is routed with the on-call list and deadline in force when it was made, not with values saved later.
A change to answer times or on-call needs a signed-in person who administers the workspace; a token or an agent is refused.
An sla value that is not a whole number of milliseconds above zero is refused with a 400 that names the urgency.
It does not
That anyone answered. The settings set a deadline and a rota; they do not make a person respond. A late ask only reads overdue.
That a notification reached the people on call. Delivery is best effort and the ask records the result, which may read skipped.
That the on-call DIDs belong to real people. The desk stores the DIDs you give it and does not check them.
Details
Build notes
Before you build
Workspace over platform
Where the workspace sets a value for an urgency, it wins. The platform's value is only the fallback, so behavior is the platform's until an administrator saves something.
A write replaces both maps
Sending sla without oncall clears the workspace's on-call list, and the reverse. Send both to keep both.
Unset means no deadline
With nothing set at either level there is no deadline and no named on-call. The desk says so instead of inventing a default.
The rest of the desk
The same module holds ask, asks and answer. This page covers only the settings.
Limits and metering
A question is at most 1000 characters and an answer at most 2000.
sla values are whole milliseconds above zero. oncall entries that are not non-empty strings are dropped when you save.
Only routine and urgent exist as urgencies. An ask with another value is refused.
Access
API & MCP
REST and MCP
Authenticate with a workspace API key as a Bearer token. The base URL is https://api.intramedial.com.
REST endpoints
GET/api/v1/acp/civics/settingsRead the workspace, platform and effective values.
POST/api/v1/acp/civics/settingsSave answer times and on-call lists (administrators only).
MCP actions
This module has no MCP action. Call it over REST from any agent or program.