Preserve census evidence with qualified counter reporting #121
Loading…
Reference in a new issue
No description provided.
Delete branch "elsie/census-reporting-20261018"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Preserve four byte-identical PR75 source files in an isolated archive, with original commit/blob/SHA256 provenance and a corrected report. API calls and dependent ratios are explicitly single-source recorded counters. The aggregate 16,242 difference (21.8857%) does not identify individual call-free turns; cause remains unresolved. Produced ID bounds 201445 versus report/manifest 201437 remain explicitly inconsistent, without inventing a transcription or caching explanation. Repeated invocation signatures are not cache eligibility or inference savings; corpus fingerprint hashes summary metadata rather than row contents. No clean scientific validation is claimed. Independent review verified original hashes, saved arithmetic, interpretation and privacy; a prose rounding typo was corrected to 1.660951 actions per recorded call. Nine synthetic in-memory SQLite tests and ten publication hashes pass; 270 Markdown files pass; ledger 30 unchanged; only preservation index changes among existing files, with operational files unchanged. No private store, science, models, GPU, browser or deployment. Cassie approved publication and merge of ready corrections, then closure of superseded PR75 with its source branch retained. PR113 stays separate.