Deprecated —
naive tasks and /v1/tasks. It drives the legacy orchestration runtime, which is FROZEN — it accepts no new capabilities. The durable runtime enforces policy at the tool boundary, not only at the gateway, and it is the only runtime new work is built on.Use instead: naive teams submit <team> "<goal>" --tenant <tu>These routes keep answering. Nothing is removed and no response shape changes: the
deprecation is announced in headers only, which are purely additive. Every response
from this router carries Deprecation (RFC 9745 —
the value is a Structured Field Date, @ plus epoch seconds, not the boolean true
some pre-RFC clients look for),
Link rel="deprecation", Warning: 299 and X-Naive-Deprecation-Id: dep.primitive.tasks.
There is no Sunset header, because this is frozen with no sunset date — a
Sunset on a frozen row would be a date the platform has not promised.Announced 2026-07-29. Level frozen. The freeze ends when
company_containers with provider='hermes' and status='running' reaches zero — not on a date.Replacement surface: the durable runtime API.Block a Task
curl -X POST https://api.usenaive.ai/v1/tasks/task-def-456/block \
-H "Authorization: Bearer nv_sk_live_..." \
-H "Content-Type: application/json" \
-d '{ "reason": "Waiting for domain DNS propagation" }'
{
"id": "task-def-456",
"status": "blocked",
"block_reason": "Waiting for domain DNS propagation"
}
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
reason | string | Yes | Why the task is blocked |
Unblock a Task
curl -X POST https://api.usenaive.ai/v1/tasks/task-def-456/unblock \
-H "Authorization: Bearer nv_sk_live_..."
200
{
"id": "task-def-456",
"status": "in_progress"
}
in_progress status and makes it eligible for the dispatcher again.