The evaluation contract separates a proposed action from the authority decision and resulting evidence. Public documentation describes those responsibilities without publishing private implementation, security configuration, or production interfaces.
Status: FUNCTIONAL PROTOTYPE. Interfaces are builder-tested in an evaluation runtime. They are not a public production API, SLA, or certification claim.
| Method | Path | Responsibility | Status |
|---|---|---|---|
| Request | Action proposal | Bind the actor, resource, effect, parameters, context, and unique request identity. | Prototype |
| Decision | Authority check | Return a bounded permit or denial without allowing the model to approve itself. | Prototype |
| Control | Approval and stop | Support approved human escalation, revocation, and stop signals for the scoped evaluation. | Prototype |
| Evidence | Decision and outcome record | Preserve what was requested, decided, and observed under the evaluation contract. | Prototype |
| Area | Conceptual paths | Status |
|---|---|---|
| Production endpoints | Routes, schemas, authentication, tenancy, and service levels | Not released |
| Security controls | Trust anchors, key management, revocation internals, and deployment configuration | Private |
| Vendor adapters | Named compatibility and certified integration profiles | Not claimed |
A product roadmap is not a shipping date or production contract.