A.6.B:8.4.3.2 - Atomize + Classify (L/A/D/E)

L-API-01 (Definition). p95_latency(window W, population P, unit U, method M) is defined as … (formal measurement definition). (Lives in Signature.Laws or a referenced measurement definition pack.)

L-API-02 (Interface signature). The API endpoints and parameters are as declared (including parameter passing discipline / units). (Signature-level structure.)

A-API-01 (Gate predicate: admissibility). The claim “p95 < 200ms” is admissible only under declared load profile + deployment region + sampling method + window: AdmissibleLatencyClaim := (region=US) ∧ (concurrency≤X) ∧ (payload≤Y) ∧ (W=5m) ∧ (M=HDRHistogram@v…) ∧ (P=requests that match filter F) (References L-API-01 for definition.)

D-API-01 (Commitment). Admitted service-maintaining system ServiceOperations-A is the actual duty bearer of separately obtaining LatencyCommitment-API-01 : U.Commitment; under that commitment it SHALL meet p95_latency < 200ms when A-API-01 holds, adjudicated per L-API-01 using the carriers and observation conditions in E-API-01. (References L-API-01 and A-API-01 by ID; does not restate them.)

D-API-02 (Operational duty). Admitted operations system SRE-A is the actual duty bearer of separately obtaining IncidentNoteCommitment-API-02 : U.Commitment; it SHALL publish incident notes when LatencyCommitment-API-01 is violated and SHALL avoid claiming compliance outside A-API-01. (References D-API-01 and A-API-01 by ID.)

E-API-01 (Evidence / carriers). For LatencyEvaluation-T1 over Γ_time=[t1..t2], actual carriers TraceBatch-T1, Histogram-H1, DashboardSnapshot-D1, and SamplingConfiguration-S1 were produced or observed under the operating and sampling conditions in A-API-01, using the metric and computation definition in L-API-01. An A.10 evidence-provenance path links those exact carriers to LatencyEvaluation-T1 and its LatencyResult-T1. (References A-API-01 and L-API-01 for the operating conditions and metric definition.)

D-API-03 (Duty-to-evidence linkage). Admitted telemetry-maintaining system TelemetryOperations-A is the actual duty bearer of separately obtaining TelemetryRetentionCommitment-API-03 : U.Commitment; it SHALL retain or expose the actual carriers referenced in E-API-01 for the audit window required by policy. (References E-API-01 by ID.)

E-API-02 (Observed value claim). For interval Γ_time = [t1..t2] under conditions pinned to A-API-01 and using carriers in E-API-01, LatencyEvaluation-T1 produced LatencyResult-T1 with observed p95_latency = 173ms (computed per L-API-01). (References A-API-01, L-API-01 and E-API-01.)