Task · GCI-0119.19

Share one label-name fetch between label_risk and label_inventory

Description

Parked until after K. Evaluate sharing one names fetch per stack and signal. label_risk privacy behaviour changes only under its own decision.

Acceptance Criteria

Definition of Done

Implementation Notes

2026-10-12 owner decision (Rob): do not share the fetch. Measured per-stack p95 26.65 s against the 3600 s T2 budget (GCI-0119.15 evidence) makes the saving negligible, while sharing would couple label_risk’s retention-governed raw-match path to label_inventory’s names-and-counts-only path and make one failure blank both.

Final Summary

Decision recorded: keep separate label-name fetches; budget impact of the duplicate is negligible at p95 26.65 s per stack vs 3600 s.

View the source file on GitHub