v2 publication contract
Content-derived collection snapshots · disclosure reconciliation 2026-09-23
Publication schema v2 is separate from methodology v0.7.1 and the engine's software version. This migration changes publication identity, not the index formulas or the dated evidence below. It does not establish that the production-compositor/engine reconciliation described in the September 6 record has been completed; that upstream publication hold is not cleared by this website change.
- Snapshot identity. Current exports carry `_schema_version: 2`, `snapshot_id`, `as_of`, `generated_at_utc`, and `indices`. The identifier is derived from the content-bearing payload and collection date, excluding generation time.
- Immutable URLs. Each snapshot is served at
/data/snapshots/{snapshot_id}.json; the current /data/indices.json pointer may move to a new snapshot. A conflicting immutable payload is an error, not an overwrite. - Source-aware disclosure. Per-index component records expose configured and effective weights where available, index-specific windows, source-specific observation counts, source tiers, and observed/quoted/proxy primitives.
- No fabricated totals. The current contract removes top-level scale, featured drilldown, bottleneck, and issue identity fields. A missing value remains missing; component counts are not universal transaction totals.
- Legacy routes. Previously exposed volume/issue URLs remain in an explicit registry as citation notices only. They do not display current values or imply that a numbered issue dataset was published.
v0.7.1 — 2026-09-06 (historical methodology disclosure)
Citation integrity + disclosure alignment — no index math change
The following dated record is preserved for the 2026-09-04 snapshot. Its issue-number crosswalk describes historical artifacts, not the identity of current v2 snapshots. Its statements about reconciliation describe the status recorded on September 6, not evidence of later completion.
No weight, tier map, trailing window, or Indicative threshold changed, and no published index level moves as a result of this entry.
Every item below is either a correctness fix to issue numbering or an alignment of published text to the behavior of the production compositor that generated the live print. A separate reconciliation is in progress between that production code and the engine repository, which currently differ; no further print will ship until that is resolved. Version note: this is the published methodology version. The engine repository tracks its own software changelog and records this same change as its v0.6.1 engine note; the two sequences are deliberately separate, and public citations should use the methodology version (v0.7.1).
- Issue-number epoch corrected. The exporter derived
issue_no from a 2026-01-05 epoch, which computes 35 for the 2026-09-04 print — a print published and cited as issue 14. The exporter could not reproduce its own live print, and re-running it would have silently re-minted every citation and /v/I/{n} permalink. Corrected to the 2026-06-01 relaunch epoch: issue_no = ((as_of − 2026-06-01) // 7) + 1, which reproduces both the live print (14) and the 2026-07 archive (6). Regression tests now pin the epoch against the published trail. - Issue-number crosswalk disclosed. The published trail is non-monotonic. 2026-05 (issue 21) was stamped under the retired epoch; 2026-06 and 2026-08 carry a literal issue 1 that is not derivable from any single weekly epoch; the artifacts establish those values but not why they were stamped that way, so their provenance is recorded as unknown. Frozen archives are not rewritten — they remain canonical as published, and this crosswalk is how a citation is reconciled against the current formula.
- Cadence clarified. The issue counter advances weekly from 2026-06-01 while issues ship on a monthly deep-dive rhythm. An issue number is a week index, not a count of published issues: issue 14 does not imply fourteen prior issues.
- Indicative gate text corrected. Published methodology described the gate as "≥30 comps per component per 7 days." That described the pre-RT-20 gate, which was real: until 2026-05-29 SWII went Indicative when its transceiver comps or FS SKU count fell below per-component minimums. RT-20 replaced that rule with a weight-adjusted total — SWCI 20, SWII 20, SWPI 10, SWFI 30 — and flipped published Indicative flags in that print. The published text was never updated to follow. This entry corrects the text, not the gate: no index's Indicative flag changes value now.
- "Equal-weight" claim corrected. Copy described the composites as equal-weighted. The engine composites on explicit unequal weights (SWCI weights frontier GPU 0.35 and HBM 0.25 against 0.04 for server DDR4 RDIMM). Copy now says weighted and points to the published
component_weights. - Component drop-out and renormalization disclosed. A component leaves the composite when it yields no value for the window, and surviving weights are renormalized. SWPI and SWFI publish the applied weights as
component_weights_used; SWCI and SWII do not yet carry that field. Yielding no value is distinct from reporting no comparables — a component can carry a value forward on zero new comps and keep its full weight, and can log comps yet yield no value. As of the 2026-09-04 print the renormalized share is SWCI 20%, SWII 30%, SWFI 30%. No reweight was performed — this is existing behavior, now stated plainly rather than silently applied. - MoM interpretation limits published. Where components are mechanically carried rather than re-measured each window — 80% of SWII by weight — a MoM figure can move without an underlying transaction. In the 2026-09-04 print SWII's series is eleven identical points followed by a single step, and both volume-varying components reported zero new comparables. That delta cannot be attributed to current transacted-price movement. Separately, SWII is Indicative because its weight-adjusted comp count is 2.75, below the threshold of 20.
Earlier records
Earlier methodology records and dated archives remain historical evidence. They may describe prior formulas, sources, or publication conventions and should not be read as the current v2 contract. See the open-data directory for the files currently served.