DOCUMENTATION COMMAND CENTER
VERIFY THE LANE BEFORE THE CLAIM.
Docs keep source evidence, runtime trace, and benchmark caveats visible before any performance claim.
TRACE THE HOT PATH
Architecture
The fd-passing topology, compose resource split, runtime service boundaries, and why the LB does not score requests.VERIFY THE LANE
Verification
Local smoke, fd-pass keepalive, purity, optional vector oracle, compose validation, and CI lanes.CALIBRATE WITHOUT OVERCLAIMING
Official evaluation gate
Manual official-like k6 workflow defaults, inputs, artifacts, scoring facts, and black-box use constraints.KEEP RUNS REPRODUCIBLE
Benchmark hygiene
Image pinning, compose validation, artifact retention, release tags, and caveats before treating CI evidence as current.REFERENCE FAMILY
The C and .NET pages remain reference context; this repo keeps its own evidence lane.
LOCAL EVIDENCE
Use these links to inspect CI, deploy, and source state before treating a claim as current.