Skip to content

v1.3.0 — Routing Transparency in Access-Log

Latest
Latest

Choose a tag to compare

View all tags
@MehmetGoekce MehmetGoekce released this 08 Jun 15:12
v1.3.0
05d6117

Routing transparency. The Access-Log already recorded which pages a query pulled; now it records why each was picked. Loading becomes auditable — not just what loaded, but the index description or grep term that selected it.

Added

  • Routing reason in the Access-Log — every query log line now carries a matched: "<reason>" field: the matched hub ### Index routing description / #tag on index routing, or the grep term on the L3 fallback. Shows not just WHICH page loaded but WHY it was selected.
  • status cache profile now breaks down the most frequent matched: reasons per hot page, surfacing mis-routing.

Changed

  • openspec/specs/query.md — REQ-450 line format extended; new REQ-450b defines the matched: reason semantics.

Notes

  • Backward compatible: legacy Access-Log lines without matched: stay valid; the suffix never affects prune/status parsing.

Full diff: v1.2.0...v1.3.0

Assets 2
Loading