Use the narrow enforcement API during authorized integration work.
This page is intentionally limited. Authorized integrators receive endpoint, interface, verifier, and sandbox material through the appropriate review channel. Integrations connect existing automation and event systems to the enforcement boundary. They do not replace the systems that schedule, route, or stream work.
Integration contract
Review channel
Gateway hostnames, request formats, response fields, sandbox credentials, and verifier material are provided through authorized integration review.
TaskHawk integration work is scoped to permission, release-token verification, and evidence output. Workflow orchestration, event streaming, and model execution remain in the customer's existing environment.
Public documentation intentionally describes the integration boundary without publishing field-level request or response examples.
Reference
| Primary surface | REST verification request with signed release-token response. |
|---|---|
| Additional protocols | Reviewed through controlled integration channels. Use only the live gateway material issued for your account. |
| Protocol 427 | Budget-attestation work remains gated. Datatracker status and controlled integration notes are authoritative. |
| Decision classes | ALLOW · CONSTRAIN · DENY |
| Authentication | X-API-Key header unless your account documentation states otherwise. |
| Formal verification | Public repository: taskhawk-systems/kevros-formal-verification |
| Support | governance@taskhawktech.com |