# Metadata correction — 2026-10-08

This operator-authorized finalization corrects metadata only. It does not change the scientific method, report, estimates, case matrix or source input, and does not rerun acquisition, analysis, Replay or export.

## Corrected values

- extraction_ceiling_bytes: **3000000000** (3 GB), replacing the erroneous **300000000** in configuration.json and its duplicated cell-source configuration. The approved Plan and acquisition guard already used 3000000000. The input ZIP inventory is **337724653 bytes** uncompressed, so it satisfied the actual acquisition guard.
- Operator deadline: **2026-10-08 16:09:24 Asia/Shanghai**, equivalent to **2026-10-08T08:09:24Z**. This is two hours from actual submission at 14:09:24 local time. It supersedes the rounded 16:12 time in the opening request and historical protocol; it does not retroactively rewrite the frozen protocol.

## Preservation and linkage

The corrected bundle is a separate Artifact, linked to the [original reproduction bundle](reproduction-bundle.zip), whose SHA-256 is:
`6a5d45ccc1418d12bda88d64ca8bba5e1145239b98120c8b0f2879472e195079`.

The original bundle and its published version are unchanged. The corrected bundle preserves protocol.md byte-for-byte, and stores the original configuration.json and native-cells.json under frozen/ as historical evidence. The current native-cells.json contains explicitly labeled metadata-corrected reference source; it is not a claim that those corrected literals were executed. Original Run IDs identify the historical execution, whose literal source remains in frozen/native-cells.original.json.

Only the two configuration fields, their duplicated metadata literals, correction/provenance metadata and package manifests are updated. analysis.py, reproduction.ipynb, environment.json, source-manifest.json, reproduction-check.json, selfcheck.json, report.md and all reference/ scientific files remain byte-identical. Historical validation and reproduction records remain historical; no fresh scientific rerun is claimed.

correction-validation.json records member-level hashes, exact allowable changes, unchanged scientific files and archive integrity. MANIFEST.sha256.json contains the corrected package's current file hashes. The external correction note is identical to CORRECTION-2026-10-08.md inside the corrected bundle.

## Native status

Earlier Artifact publication calls succeeded, but native discovery/lineage could not resolve the returned scientific Artifact version. The correction records those receipts and explicit original-version linkage without claiming that native lineage or environment capture is verified. Publication of the corrected bundle is reported separately in the native conversation after its save succeeds. No application code or artifact-validation mechanism is modified or bypassed.

Unchanged deliverables: [report](report.md), [results](reporting-results.csv), and [original FDA input](faers_ascii_2026q2.zip).
