Evaluator Contract
Evaluator contract published. Runtime access is by request.
The publishable artifact is the contract a third-party evaluator engages against. The runtime that implements the contract is gated behind counsel-vetted partner access. This page documents the public-contract surface only.
The runtime is by request.
No claim is made about endpoint availability on the public surface.
Contract scope
The evaluator contract specifies the interface a partner-tier evaluator engages against to verify governed-AI claims. The contract is versioned, hash-anchored, and disclosed at Tier 0. The interfaces it describes are not exposed on public-facing infrastructure; access is provisioned under partner agreement, scoped to the named technical evaluator listed in the access request.
This separation — public contract, partner runtime — is the discipline that distinguishes a published interface from a marketed service. A regulator or an auditor reading this page can verify the contract's shape without engaging the partner-tier surface. A partner-tier evaluator engages the contract under NDA, against a runtime they can attest.
Authentication and attestation at public-contract level
Two properties are part of the public contract.
Authentication. Evaluator identity is established at request time and bound to the named technical_evaluator in the access request. The mechanism is documented at the contract level; depth-level details are partner-tier.
Attestation. Responses include evidence of execution provenance. The shape of the attestation is public; the cryptographic depth is partner-tier. An evaluator receiving an attested response can verify the contract was honored without disclosure of the depth-level detail.
No technical depth appears on this page. Restricted runtime categories are governed by the disclosure-tier policy at /schemas/disclosure_tiers.yaml; enforcement is by the build-time disclosure linter.
Endpoint posture
No public-facing endpoint URL is advertised. No claim is made that runtime endpoints are operational. The contract surface published on this page is the public-tier specification only.
| Surface | Status | Access path |
|---|---|---|
| Evaluator contract (this page) | Specified | Public |
| OpenAPI specification | Pending | Pending separate API-contract receipt. Runtime access remains by request. |
| Partner runtime endpoints | By request | NDA-gated; provisioned per access request |
| Postman collection | Pending | Tier 1; released to named evaluators only |
How an evaluator engages
- Read this contract page and the schemas at /schemas/ to understand the contract shape.
- File an access request at /access/ with the eight required fields.
- Counsel reviews the request and proposes an NDA appropriate to the requested tier.
- Once NDA executes, the partner-runtime credentials and Postman collection are provisioned to the named technical evaluator.
- Engagement happens against the partner runtime, not against the public surface.
What this page does not claim
- No claim that any specific endpoint is operational at this time.
- No claim of compliance certification or standard endorsement.
- No claim about throughput, availability, or service-level guarantees on a public surface.
- No claim that the contract is final. The contract is versioned; version transitions are recorded in the receipts registry.
The public contract is on this page. The runtime is by request. Counsel routes the engagement.
Request evaluator access →