| Interface | Implemented contract |
|---|---|
| 01Interactive CLI | Create and inspect governed workspace state through the headless command-line interface. |
| 02Loopback REST | A local bearer-token service exposes the bounded application surface on the operator's machine. |
| 03OpenAPI 3.1 | The local REST contract is described by an implemented OpenAPI 3.1 document. |
| 04TypeScript SDK | Typed integration helpers support programmatic use of the local contract. |
| 05stdio MCP | A local MCP server exposes readiness tools over standard input/output. |
| 06Bundle verification | Verify machine-readable Readiness Bundle integrity independently of the Desktop UI. |
CIVITAS READINESS / DEVELOPERS
Developer surfaces for governed readiness.
Use Civitas Readiness locally through headless interfaces or expose a bounded HTTPS protected resource with externally issued OAuth access tokens.
LOCAL
Local and headless interfaces
REMOTE PROTECTED RESOURCE
A resource server, not a public SaaS platform
| Control | Technical boundary |
|---|---|
| 01HTTPS / TLS | The remote profile serves the protected-resource surface over HTTPS. |
| 02External OAuth issuer | Civitas validates access tokens; it does not ship a built-in authorization server. |
| 03RFC 9728 | Protected-resource metadata advertises the resource and its authorization-server relationship. |
| 04Bounded scopes | Remote operations are constrained by explicit resource scopes. |
| 05Remote MCP 2026-07-28 | The implemented protected-resource profile includes the dated remote MCP transport contract. |
AUTHORIZATION BOUNDARY
Human governance remains local and explicit
Integrate a bounded use case.
Confirm deployment mode, security boundaries and domain requirements before integration.