Skip to content

History / README

Revisions

  • Boundary split: strip private references, publish the runner programs and corpora The code repository is private; this wiki is public. Studies published here had been citing the private tree, and two published yesterday went further than any page before them. WHAT CROSSED, measured before this commit: private paths (cells/xcode/*) 12 files, longstanding ~/.gaiaftcl and home paths 7 files .swift:NNN line citations 2 files — both added yesterday verbatim substrate source 1 file — added yesterday, the first ever here internal constants 1 file — added yesterday Before yesterday this wiki carried ZERO Swift code blocks and ZERO file:line citations. WHY THE LINE CITATIONS WERE THE WORST OF IT. "Cite file and line" is an internal verification standard. Applied to a public page it maps a private tree AND buys the reader nothing, because they cannot open the file to check it. Worst of both directions. That exposed a second defect the leak was hiding: the "reproduce every number" sections told public readers to run programs that lived in a private repository. Unfollowable. SO THE FIX IS NOT ONLY REDACTION. The ten runner programs are self-contained — zero imports but Foundation in the two that read a file, zero private references, verified before publication — and they exist precisely so a stranger re-runs them. They are now public, with the corpora they read: reproduce/ 10 programs + README, each naming its control arm corpus/study-29/ GCAT satcat.tsv, 19,293,257 B, sha256 090ce077… corpus/flood-lead-time/ four USGS gauge series + the propagation cases Both corpora verify against their SHA256SUMS after the move, and the GCAT digest matches the pin taken when it was fetched. REDACTED EVERYWHERE ON THIS WIKI: cells/* paths, ~/.gaiaftcl and home paths, file:line citations, the one verbatim source line, and the internal constants. Claims were rewritten to cite BEHAVIOUR and the live public catalogue rather than source locations — Study 30 now says outright that the substrate source is not public and that a citation a reader cannot open is not evidence. NOT redacted, and flagged rather than decided unilaterally: bare private module filenames (QCCourtLaw.swift, LatticeDomainIntegration.swift, the Eclipse commands) appear in ten pre-existing pages. They are none of the five categories in the instruction, and several name laws that are themselves publicly served. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

    @rg78803 rg78803 committed Sep 1, 2026