InferCrane can add control-plane evidence around an existing OpenAI-compatible workload without
replacing it. Adoption is incremental and does not silently transfer lifecycle ownership.
Adopt an existing workload
observe-only records health and evidence but never publishes a route. traffic-managed may route
through the existing target after its qualified runtime health check succeeds. Neither mode creates,
scales, updates, or deletes the imported workload. lifecycle-managed is available only through an
InferCrane Deployment binding.
The URL, source, logical model and physical upstream model form an immutable adoption identity. A
safe retry returns the same adoption; changing immutable identity fails with a conflict.
Promote ownership explicitly after reviewing health evidence:
Inspect one request
The result identifies routing identity, timings, tokens, retries, fallback reason, status and error
class. content_recorded is always false: prompts, outputs and authorization values are not part
of request evidence.
Deterministic Doctor
Doctor persists reproducible Evidence → Rule → Finding results. Current rules cover unavailable
endpoint routes, statistically bounded elevated error rate, and queue-dominant latency. A healthy
result explicitly reports that no deterministic issue is active; it does not guess a cause.
Signed alerts
Deliveries include InferCrane-Delivery, InferCrane-Timestamp, and
InferCrane-Signature: v1=<HMAC-SHA256>. The signed input is
<timestamp>.<exact request body>. Delivery is idempotent per policy/finding, retries are bounded,
and public-network validation rejects private, loopback, link-local and unspecified destinations by
default. Resolved signing secrets are never persisted or returned.
Adoption does not import provider credentials or guarantee ownership of the workload. Keep the
existing workload available until traffic-managed health and request evidence have been verified.