Context
#14687 is the full serving-cost measurement program: one institution-day, the same workload on at least two available hardware options, and an actual hosting-bill read. The current implementation PR delivers the instrument needed to run that program, but it cannot honestly close the broader evidence program before those measurements exist.
The Problem
The instrument needs its own delivered-scope contract. Its process attribution must also be measurement-safe: a configured endpoint port can have both the listening server and connected client processes, while a remote endpoint has no local owner to sample. Counting every process returned by a port-wide lsof query contaminates the server measurement with client load.
The Architectural Reality
The benchmark CLI is the sanctioned AiConfig-reading entrypoint; aggregation and METRIC-bag shaping remain pure transforms. Endpoint ownership is a local operating-system fact: only the local listening owner is attributable to the configured service. Remote hosts must be reported as unmeasurable by this local-process instrument, never reinterpreted as a local port.
The Fix
Land the steady-state serving-cost instrument as one coherent leaf: local-listener discovery, periodic RSS/CPU sampling, gap-aware deterministic aggregation, provenance-complete METRIC bags, and the zero-number results-document skeleton.
Acceptance Criteria
Out of Scope
The 24-hour institution run, second-hardware run, live hosting-bill read, and graph ingestion of real results remain open under #14687.
Related
Parent measurement program: #14687. Implementation PR: #15013. Duplicate sweep: live title/body search found only #14687; this ticket is its instrument leaf, not a competing measurement program.
Origin Session ID: 019f484c-662f-7f31-969a-cbde373efd4a
Retrieval Hint: "serving cost meter listener owner client process contamination"
Context
#14687 is the full serving-cost measurement program: one institution-day, the same workload on at least two available hardware options, and an actual hosting-bill read. The current implementation PR delivers the instrument needed to run that program, but it cannot honestly close the broader evidence program before those measurements exist.
The Problem
The instrument needs its own delivered-scope contract. Its process attribution must also be measurement-safe: a configured endpoint port can have both the listening server and connected client processes, while a remote endpoint has no local owner to sample. Counting every process returned by a port-wide
lsofquery contaminates the server measurement with client load.The Architectural Reality
The benchmark CLI is the sanctioned AiConfig-reading entrypoint; aggregation and METRIC-bag shaping remain pure transforms. Endpoint ownership is a local operating-system fact: only the local listening owner is attributable to the configured service. Remote hosts must be reported as unmeasurable by this local-process instrument, never reinterpreted as a local port.
The Fix
Land the steady-state serving-cost instrument as one coherent leaf: local-listener discovery, periodic RSS/CPU sampling, gap-aware deterministic aggregation, provenance-complete METRIC bags, and the zero-number results-document skeleton.
Acceptance Criteria
Out of Scope
The 24-hour institution run, second-hardware run, live hosting-bill read, and graph ingestion of real results remain open under #14687.
Related
Parent measurement program: #14687. Implementation PR: #15013. Duplicate sweep: live title/body search found only #14687; this ticket is its instrument leaf, not a competing measurement program.
Origin Session ID: 019f484c-662f-7f31-969a-cbde373efd4a Retrieval Hint: "serving cost meter listener owner client process contamination"