Methodology change notice — provenance stamp: first stamped print of record (clarification)

Notice date: 2026-08-17 (UTC; all dates in this notice are UTC) Class: clarification of record (rule pack v1.0.0 → v1.0.1). Not a methodology change — no method changes and no notice period runs. Not a correction — no published value is restated and no print body is edited. Instrument: gap_h100_spot (GAP-H100 spot; Class 3 indicator since notice 2026-08-14 §2) Effective: on publication, 2026-08-17. The record clarified below concerns the 2026-08-14 → 2026-08-16 prints and is stated as it happened; nothing binds earlier than it was published. Rule pack: R-PROV-001 effective_date 2026-08-14 → 2026-08-16 (data/governance/rule_pack.json v1.0.1, CHANGELOG.md 1.0.1). Notice 2026-08-14-instrument-actions.md is not edited.

1. What this clarifies

Notice 2026-08-14 §3 declared that every GAP-H100 spot print "now carries" a provenance stamp — panel size, offer count, the contributing providers with each provider's unchanged-days and price, transaction count, data tier, judgment applied, and the one-line stamp string — written into the print of record at print time, with the stamp taking effect on publication (disclosure only, no notice period).

The code that writes the stamp (scripts/compute_gap_print.py, commit 7acf434, branch fix/gts-suspend-and-disclose) reached main in merge 34b01ae at 2026-08-16 02:16 UTC, after the 2026-08-15 cycle had printed. Consequently:

• the 2026-08-14 and 2026-08-15 prints of gap_h100_spot carry no stamp — the store holds no provenance object for either day and /api/print/2026-08-14 and /api/print/2026-08-15 serve provenance: null, exactly as the rule's own last sentence requires of pre-stamp prints;
• the first stamped print of record is the 2026-08-16 cycle (printed 2026-08-16 18:30 UTC anchor), and every print from that cycle carries the full stamp.

The nightly auditor (scripts/nightly_audit.py, check print_of_record) reported the two unstamped prints as a breach on its first run (data/audit/nightly/2026-08-15.md, run 2026-08-16 11:33 UTC) — the rule pack v1.0.0 carried the notice's publication date, 2026-08-14, as the effective date. That report stands as written.

2. Resolution — by record, never by editing records

Founder ruling 2026-08-17: the print bodies for 2026-08-14 and 2026-08-15 are untouched. A stamp is written at print time from the panel as it stood at print time; synthesising one afterwards would be a retroactive fabrication of provenance, which R-PROV-001 itself forbids ("pre-stamp prints serve provenance as null, never synthesised retroactively"). The two prints stand as published on their day's method, provenance null, immutable under /api/print (R-API-001).

The record is corrected on the rule side instead: R-PROV-001 effective_date is set to 2026-08-16, the first print that actually carried the stamp. This is a PATCH-level change to the rule pack (v1.0.1) — what the rule requires is unchanged; only the date from which the auditor enforces it moves, to the date the requirement was in fact met. From v1.0.1 the auditor treats 2026-08-14 and 2026-08-15 as pre-effective and enforces the stamp on every print from 2026-08-16.

3. Publish-before-effect

ADR-003 §2 (publish before effect) is not breached by the stamp: it is a disclosure that adds information to a print without changing any printed value, declared before the first print that carried it. What went wrong is narrower — a notice stated a disclosure was live two cycles before the deployment that made it live. This clarification records that gap dated, on the notices rail, where the original statement lives; the original notice is left as written so the record shows both.

4. Record

• Ruling: founder, 2026-08-17 — "provenance-stamp breach, resolved by record, never by editing records: print bodies for 08-14/08-15 are untouched. Set R-PROV-001 effective_date to 2026-08-16 (first stamped print = the 08-16 cycle). Bump rule_pack.json to 1.0.1 + CHANGELOG line. File a short dated clarification as a NEW notice entry (do not edit notice 2026-08-14)."
• Deployment of record: merge 34b01ae (2026-08-16 02:16:23 UTC) carrying 7acf434 ("per-print provenance stamp for GAP-H100", founder ruling C, 2026-08-14).
• First stamped print: gap_h100_spot 2026-08-16 (/api/print/2026-08-16).
• Auditor report of the two unstamped prints: data/audit/nightly/2026-08-15.md.
• Companion: 2026-08-14-instrument-actions.md §3 (the stamp), docs/api-print-v1.md (provenance field; null on pre-stamp prints).