Kiln Documentation

Serving benchmark launch schema

Define direct argv launch, working and log directories, readiness checks, startup and shutdown bounds, and accepted exits for an owned benchmark server.

Owned-server launch contract for a local serving benchmark. It records an argv vector, working and log directories, readiness cadence, bounded startup and shutdown, and acceptable exit statuses; hardware names in an instance ID are evidence labels, never runtime dispatch policy.

Schema identity

Property Value
Title Kiln Serving Benchmark Server Launch v1
$id https://ericflo.github.io/kiln/schemas/serving-benchmark-server-launch-v1.schema.json
Dialect https://json-schema.org/draft/2020-12/schema
Root type object
Root object closed

Root fields

Field Required Type Constraints and default Description
schema yes any const "kiln.serving-benchmark-server-launch.v1" Schema identifier for this launch contract.
id yes string pattern ^[a-z0-9][a-z0-9._-]{2,127}$ Stable, path-safe identifier for this launch recipe. It may name the evidence environment but does not control backend routing.
command yes array<string> minimum items 1; maximum items 256 Executable and arguments passed directly as an argv vector, without shell evaluation. The executable must resolve to an explicit absolute or relative path.
working_directory yes string minimum length 1 Directory from which the owned server process is launched. A relative path is resolved from the launch-contract directory.
log_directory yes string minimum length 1 Directory reserved for this owned server's captured logs. A relative path is resolved from the launch-contract directory.
readiness_poll_interval_ms yes integer minimum 1; maximum 60000 Delay in milliseconds between /v1/models readiness probes while the owned server is starting.
startup_timeout_seconds yes number exclusive minimum 0 Positive wall-clock deadline for the owned server to remain alive and answer the readiness probe.
shutdown_timeout_seconds yes number exclusive minimum 0 Positive wall-clock deadline for the owned process group to exit after graceful shutdown begins, before forced termination is considered a failure.
acceptable_exit_codes yes array<integer> minimum items 1; maximum items 16; unique items Sorted, unique process exit statuses accepted after a fully verified graceful shutdown. A listed status does not excuse forced termination or surviving child processes.