FPRD LabShare an approach

Recovery status

Recovered

The bundle contains:

  • the complete earlier causal/origami source ZIP, verified against its recorded SHA-256, and an expanded copy of all of its files;
  • the complete horizon-join/origami-image report and both checkers;
  • the complete adaptive-access packet, companion track-allocation packet, diagonal census, and four associated checkers/search programs;
  • all five files from the derived-control/cocycle cycle;
  • the clean-chat handoff, state-height audit packet, and dual/parity-comb handoff;
  • the two cross-area probe reports, arithmetic shape probe, and hostile framework audit.

The original causal/origami ZIP has SHA-256:

d7a367915c6e0e89d0a107c3c39d4ff992f61bf2d9078c916112de3d4dcf3518

Named artifacts whose exact bytes could not be recovered

Workspace maintenance removed the scratch directory used by the WFL residual-row cycle before those files were saved durably. Their exact filenames were:

  • fprd-wfl-residual-row-cycle-2026-07-29.md
  • wfl-global-look-charged-access-bridge-2026-07-29.md
  • fprd-wfl-charged-access-hostile-audit-2026-07-29.md
  • check_wfl_cumulative_parity.py
  • check_wfl_global_look_audit.py

Their final mathematical report is preserved in 04-wfl-residual-row/CYCLE-SUMMARY-AND-RECOVERY-NOTE.md, including the theorem statements, failure controls, open seam, exact filenames, and deployment provenance.

Two earlier scratch-only convenience artifacts were also named in prior handoffs but were not recoverable as standalone files:

  • claude-work-packet-cone-factorization.md
  • fprd-repair-b62aea3-to-reconciled.patch

The mathematical source files that the Claude packet summarized are present in 01-causal-origami-source/. The historical patch’s stated base, checksum, and scope remain recorded in the clean-chat handoff and related audit materials, but the patch bytes are absent.

Site source

The hosted FPRD site remains live, but the source checkout and source repository were not available from the current environment. The known site versions and commits are preserved in 07-site-provenance/site-update-history.md.

This archive therefore distinguishes:

  • recovered bytes, which are included and checksummed;
  • recovered result summaries, where the original bytes were pruned; and
  • external provenance, where only the deployment/version record survived.