Skip to content

Research archive and recovery index

The execution plan is the sole active queue; the portfolio classifies branches. This archive retains scoped evidence and byte-level recovery records. Historical instructions, milestone labels and reported successes are not current authority.

Historical campaign and measurement records

The following narrative records moved out of live research reading routes. Their original entry pages retain scope summaries and section aliases; the archived bodies preserve conditional results, source identities, negative outcomes and unresolved limitations. Relative links were rebased. Frozen protocols, source archives, data, responses and recorded byte hashes were not changed or regenerated.

Archived record Maintained boundary
C6 response and rounding, carried flow, pressure excursions, relational regions, history exclusions, remaining obligations Cycle-winding owner: reusable cycle transport is separate from parked global C6 certification
Forced-support regional observations Forced-support balance: current balance and geometry proofs retain their own chapters
Eleven-node receiver bounds, transfer and capture Memory collection: preparation-specific exclusions and the unresolved transfer range remain valid scoped evidence; no receiver campaign is active
C6 B71-B75 mechanism audit C6 scope: 41/56 labels excluded, 15 open; no global stability proof
Transport source reviews and Volts comparison Transport contract: reusable fixed-reference/equal-capacity models and uncertainty admission; no admitted physical test
TCLab exploratory comparison TCLab scope: completed evaluated comparison with mixed errors and unadmitted physical premises

Source-review exclusions concern the inspected model and observation contract, not the impossibility of every physical TNFR realization. Archived next-step language does not reopen a campaign; the sole execution plan owns scheduling.

Recovery records

Do not duplicate a superseded file in another archive when its complete content is recoverable from a verified immutable Git revision. Current uncommitted proofs and frozen evidence require preservation before any retirement.

Record Contents and recovery scope
Deep cleanup Retired historical PDF, obsolete planning captures, notebook and other reviewed duplicates; original path, reason, replacement, immutable revision, blob and byte hashes
Second deep cleanup Consolidated equivariance scope and retired engine no-ops; source identities, uncommitted recovery edits and retained owners
Third deep cleanup Retired duplicate math/grammar/catalog helpers and unsupported arithmetic inferences; verified source recovery, retained owners and corrected observation/clock scope
Validation configuration cleanup Five unconsumed global-policy fields retired; exact declarations, committed source identity and current admission owners
Physics helper cleanup Five unconsumed private helpers and duplicate alias/cache fallbacks retired; immutable source identities and retained implementation owners
Second physics cleanup Mandatory-dependency import fallbacks and unreachable guards retired; each removed source segment verified against its immutable recovery blob
Mathematics cleanup Unconsumed helpers/constants, obsolete dependency/cache branches and a duplicate exception declaration retired; immutable source identities and shared replacement owners
Benchmark retirement Unsupported or unused instruments; source bytes verified against their recorded revision, with checkout/Git newline differences retained
Foundation reassessment Retired external-model mappings, duplicate probes and obsolete historical text copies; retained owners and original source identities
First documentation capture Original working-tree capture hashes; these can differ from normalized committed blobs
Second documentation retirement Additional retired document identities and replacements
Tests and examples retirement Superseded tests/examples and the user-deleted manuscript

Recover a recorded blob with git cat-file blob <git_blob> and write its returned bytes using a binary-safe writer. Shell text redirection may change encoding or line endings. An immutable Git file URL is convenient for reading; blob identity and SHA-256 establish byte-level recovery. A manifest is a receipt, not evidence that its former claims are correct. The cleanup records include uncommitted edits for consolidated working copies; Git alone would not recover those bytes. Apply any declared newline conversion first, then the recorded edits in descending byte-offset order, and verify the working-copy hash. Useful content remains with the stated current owners.

Retained boundaries and replacements

  • The theory catalog owns definitions/proof routes; the documentation map owns usage and contract routes. Former navigation catalogs and per-turn delivery logs are recovered from the manifests, not maintained as additional authorities.
  • Retired particle/chemistry, Yang-Mills and Navier-Stokes mappings had supplied external assumptions, not a derived nodal bridge. Their useful limits remain in retired-programme boundaries. Shared graph, winding, symmetry and evidence kernels retain their explicit premises.
  • Removed APIs have no alias silently substituting a different model. Exact former names and implementation bytes remain in the foundation manifest. Current public interfaces belong to the API contracts.
  • Duplicate conservation comparisons do not replace the trajectory-balance owner. Arithmetic/spectral claims retain the Riemann scope.
  • Reported interface observations preserve their data/model limitations. Moving or retiring a narrative does not rerun the experiment or establish physical validation.
  • Benchmark and example catalogs identify maintained instruments. Frozen protocols, source archives, responses and verdicts remain unchanged at their recorded paths.

Superseded planning captures

Both September 20 and September 26 plan/portfolio captures were subsequently committed. Their duplicate working-tree copies are retired; they are not uncommitted history or additional task queues. The September 26 captures are recorded in the deep-cleanup manifest after exact byte verification against 6e1ffb8ffbadb667b11230c6af9f670d5f9d48b7. Their original capture base f27413a0a29dddc132e5aafea081b0caee0b0135 is a different provenance field.

The earlier September 20 recovery revision is 415aa4d05c2fe89132469ca981b1a7fca2bfc214; these identifiers describe committed blobs, not the original raw-capture line endings:

Retired capture Git blob Bytes Blob SHA-256
EXECUTION_PLAN_PRE_FOUNDATION_REASSESSMENT_2026-09-20.txt 17775016433ca9a13dbf6a638cea8c96ea966fec 54354 f26468ebe060da159ef5b853131498cc05c5e553b80d7355d3c128a37e411fd7
PORTFOLIO_PRE_FOUNDATION_REASSESSMENT_2026-09-20.txt 0cb05a80efc96dac7d12dcf8792fe1a0a010a9b6 38789 946c438fbff08ae35efa06eb6aa0a3a6c1497a6efe0cfd4047d18f26f38915a4

Closed-gate plan consolidation

The repeated closed-gate summaries and protocol inventories in theory/research/FIVE_STAGE_EXECUTION_PLAN.md are recoverable from immutable revision 62d3da86f071f6d65c0bf3afbe6d44fa10ee6701, Git blob 0ead938a6d43f88048244ae6a56217bd9d895c2e (81,767 bytes; SHA-256 e90802e051c62df639571d8df6d31121f816d2401e4e4dfc2ada627d14fd517b). These identities describe the committed blob, independently of routine checkout newline conversion. No duplicate historical plan was created.

The current plan retains the latest result, inactive resumption boundary, unresolved dependencies and admission rules. Its retained aliases route all prior explicit and heading anchors to their canonical result owners; the theory-to-execution map owns the full proof, implementation and test inventory. Conditional scope, negative results and the separately archived two-port probe export recovery remain explicit. The plan consolidation removes no proof and changes no frozen protocol, source archive, response or verdict. It admits no new campaign.

Historical source audit for the foundational stages

The retained audit supports state-adequacy tests, not every historical claim. The original PDF, printed/physical pages 212–219, mixes derivative, distance and response meanings; the dimensional correction owns the remedy. Earlier mandatory Banach/irreducibility assertions and entropy-based type selection are not foundation proofs. Signed-scalar, zero-form phase and same-observation/different-future controls supply usable counterexamples instead.

These are retained audit identifiers, not new runs.

Material Retained identifier
Original PDF, SHA-256 5ba0f4a2da2d01e550e7004c3c09c6927e6620826052df84cd28babbcbd34fc3
Foundation at c80c99ee; Git blob 4bac2484007fe3d1edc844ec92d3ea19cdf070c0
EPI instrument at 81e21f6d; Git blob 81cbccaaec5076129c57865401425d3856067531
Retired pressure and tetrad probe blobs ebb5dec0883e56892867fc6f103a906cd2b31902; 03048368d3cedd08d5238a0e1ccbcacf3792350f
Retired substrate examples be3a8d37:examples/08_emergent_geometry/125_node_is_the_emergent_substrate.py; 29c1596d:examples/08_emergent_geometry/128_base_substrate_coemergence.py
Retired pulse/edge examples 9f506c59:src/tnfr/sdk/simple.py; e6d5e731:benchmarks/emergent_rhythm.py; a8f49c036d00cd81d6a84a3db6049537bdf8852f:benchmarks/emergent_atom_dynamics.py
Capacity and phase probe blobs 6bbcc6de69e784ceb24cdf5998b785111f305767; fbcd99eefa153818941742f913af83c5a060d605
artifacts/research/capacity_feedback.json, SHA-256 ef270001e219934b8ee23038a584ac47571d7ac170e0436835119142bd284ba1
artifacts/research/capacity_localization.json, SHA-256 c98cf2907d6f70c38d26a1baa2fc178feb8a74a276fbf984f1ec7c38a5a11df8
artifacts/research/compatible_capacity_regions.json, SHA-256 0d26959ca0e87226bb8bbda2d2a3b9ca1c33d9a30adb60432096d984b2242057

The three artifacts recorded dirty source and were not reproduced on the current tree. A bin-dependent entropy threshold does not identify capacity's mathematical type. Unwrapped invocation samples without elapsed time and an intersample phase bound do not identify a primitive phase clock. Current foundation controls, representation controls and relational admission retain the relevant mathematical questions without reviving those instruments.

Earlier cleanup receipts are listed under recovery records. Historical source review does not restore retired execution or reopen a queue.