Rendered from docs/obligations/0006-route-latency-at-a-harvesting-tier-is-unmeasured.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

Route latency at a harvesting tier is unmeasured

Context

Q9 rules that the tier above harvests pinned exports and that no merged graph exists. Harvest should keep a solution-tier route query inside the same 100 ms budget.

Obligation

Route latency at that tier is the instrument, and this corpus owes a reading of it.

Discharge

The route query exists now, and its latency at one corpus is measured. A release build over 36 documents answers the verb in 20 to 30 ms. Inside one session, where the walk is paid once, a call is about 3.5 ms. So the cost is the walk rather than the route, and the tier the instrument names does not exist. The claim stays open with a baseline on the record.