Skip to content

First Evaluation

This walkthrough runs a single evaluation using the kairos evaluate command. You need a built CLI binary and an activated license.

An evaluation requires three inputs:

  1. Calibration artifact — provided as part of your deployment package
  2. Deployment policy — provided by Ananke for your licensed environment
  3. Evaluation request — the actual metrics snapshot to evaluate

The artifact and policy are deployment-specific. Use the files from your starter kit or customer package; do not hand-edit signed policy files.

{
"envelopeVersion": 1,
"requestId": "first-eval-001",
"snapshot": {
"timestamp": "2026-03-21T12:00:00.000Z",
"metrics": {
"primaryRiskMetric": 450.0,
"primaryStabilityMetric": 72.0
}
}
}
Terminal window
kairos evaluate \
--config artifact.json \
--policy policy.json \
--request request.json

You can also pipe the request from stdin:

Terminal window
cat request.json | kairos evaluate \
--config artifact.json \
--policy policy.json

A passing evaluation returns:

{
"envelopeVersion": 1,
"requestId": "first-eval-001",
"decision": "PASS",
"reasonCode": "NONE",
"mode": "state_gate",
"policyVersion": 1,
"adapterVersion": 1,
"evaluation": {
"currentGamma": 0.68,
"gammaFloor": 0.20,
"currentLambda": 0.89,
"stability": 2.40,
"predictedGamma": null
},
"escalation": null,
"overrideOutcome": null,
"timestamp": "2026-03-21T12:00:00.500Z"
}

Key fields:

FieldMeaning
decisionPASS — the action is permitted
reasonCodeNONE — no adverse condition detected
evaluationNumeric evaluation details for the current request
timestampWhen the evaluation completed

If the request fails the configured state gate, the response shows:

{
"decision": "REJECT_STATE",
"reasonCode": "GAMMA_BELOW_FLOOR",
...
}
  • Learn about Fly-by-Wire for stateful evaluation with engine telemetry
  • Explore the full CLI reference for all available commands