Unify forward-pass iteration measurements
Define one canonical synchronized forward-pass iteration with nested rank measurements. Both physical source forms normalize to this shape; their grouping provenance differs.
Canonical shape
Required fields are version, source_kind, iteration_id, producer, grouping, expected_dp_ranks, complete, max_rank_wall_time, and rank_measurements. collector is optional globally and required for listener receive-time-window grouping.
rank_measurementsis the authoritative per-rank evidence, ordered by ascendingdp_rank.max_rank_wall_timeis the cached default scoring latency. Consumers may derive another policy fromrank_measurementsand record that choice in their result provenance.- A complete iteration contains exactly one measurement for every rank in
expected_dp_ranksand requiresmax_rank_wall_time == max(rank_measurements[*].wall_time). - An incomplete iteration retains available ranks with
max_rank_wall_time: null.
Source and grouping forms
self_benchmarkusesgrouping.method: benchmark_id. The producer supplies the sharedbenchmark_id, point, expected ranks, and one FPM per rank. The physical sourceiteration_groups[].wall_timenormalizes to canonicalmax_rank_wall_timeafter validation.- A one-rank event stream uses
grouping.method: single_rank. - A multi-rank listener stream uses
grouping.method: listener_receive_time_window.
Listener timestamps are assigned independently for each received event, so exact _recv_ts equality is not a join rule. The canonical grouping instead records:
- engine role and raw
_recv_tsunit; - the clock-correction method, reference clock, rank-to-clock groups, and signed offsets;
- the corrected window start, size, half-open boundary, and distinct-
dp_rankrule; and - the component that performed the derived grouping.
Every contributing rank retains its raw _recv_ts. File order and rank-local counter_id are not cross-rank identities. The GLM DEP16 campaign is represented by four corrected node clocks followed by an 8 ms window of distinct ranks.
Physical representations
- Rank observation streams remain one rank record per JSONL line.
- Self-benchmark files retain their producer
iteration_groupsrepresentation. - Importers may materialize canonical synchronized iterations as one JSONL record per iteration.
Standalone rank records are directly evaluable only when attention_dp_size == 1; multi-rank truth requires a complete synchronized iteration.
Validation passes for JSON Schema Draft 2020-12 meta-validation, canonical self-benchmark and listener-window cases, physical self-benchmark groups, rejection of the former exact-timestamp method, and the full current dataset (15 configurations, 22 measurement bundles, and 163 source measurement files).
Validation passes: JSON Schema Draft 2020-12 meta-validation; canonical self-benchmark and listener-stream positive and negative cases; and full dataset validation across 15 configurations, 22 measurement bundles, and 163 source measurement files.
Updated the DP contract in 5306df8 after checking the GLM DEP16 listener and scorer implementation.
rank_measurementsremains the authoritative evidence.- Canonical records now cache
max_rank_wall_timeas the default score; the redundantlatency_aggregationand generic aggregatewall_timefields are removed. - Listener grouping is now
listener_receive_time_window, with raw_recv_ts, explicit clock-group offsets, corrected window start/size, and one-record-per-dp_ranksemantics. - Exact
_recv_tsequality is explicitly rejected. The GLM rule is representable as four corrected node clocks plus an 8 ms half-open window. - The physical self-benchmark
iteration_groups[].wall_timeremains supported and normalizes to canonicalmax_rank_wall_timeafter checking its nested ranks.
Validation passed: Draft 2020-12 schema meta-validation; canonical rank, self-benchmark, listener-window, and physical benchmark cases; negative legacy-grouping and missing-max cases; current dataset validation (15 configurations, 22 measurement bundles, 163 source measurement files); and a conflict-free merge-tree with PR #2.
This resolves the schema shape, not the PR #2 consumer path. PR #2 still needs canonical synchronized iterations (or equivalent reproducible grouping metadata) and FPM Gym still needs a forward-pass-measurement-v1 adapter that consumes them.