CRYPTOSPORA SILENTIS — OFFICIAL TEST REPORT Test ID: CS-REAL-003 (v1.2 — Two Bugs Fixed) Species: Cryptospora silentis (The Hidden Spore) Creator: Wagg · Owner: Family Tree Trust Date: 2026-09-26 System: Diamond Server (Python 3, real engine) Document Type: Full Technical Record PURPOSE OF TEST CS-REAL-002 found two bugs in the v1.1 engine: 1. A wrong password could unlock the core through a fallback in the Enhanced Micro-Repair component. 2. One fold wrote twelve files. File count grew with each fold. The v1.2 engine removes the fallback (no secondary path exists anywhere in the species) and replaces the file-writing logic with a fixed budget. Every fold overwrites. This test confirms both fixes and reruns the rest of the scenarios. THE TWO FIXES FIX 1 — NO FALLBACKS. The template fallback in Enhanced Micro-Repair was removed. The unfold now has one path: read every copy, verify every checksum, decrypt every copy with the buyer's password. Only copies that decrypt contribute. If none decrypt, nothing is restored. No secondary path. No bypass. FIX 2 — FIXED FILE BUDGET. The species writes exactly eleven files per fold: - 3 primary core copies - 3 camouflage files - 3 decoy files - 1 autosave snapshot - 1 presence file Every fold overwrites the fixed paths. File count is constant. ACTUAL RESULTS | Test | Result | | Wrong password refused | PASS | | Files after fold 1 | 11 | | Files after fold 2 | 11 | | Files after fold 3 | 11 | | File count stable across folds | PASS | | Correct password unfolds | PASS | | Core matches original | PASS | | Encryption (plaintext hidden) | PASS | | Patience Core (3 checks required) | PASS | | Kill switch (0 files remaining) | PASS | Result: 6 of 6 checks passed. WHAT THIS SHOWS 1. The password bypass is closed. A wrong password cannot unlock the core. The buyer's key is required. 2. The file bloat is gone. Eleven files per fold. Every fold. No growth, no drift. 3. Nothing regressed. Encryption, Patience Core, and the kill switch all work exactly as they did in v1.0 and v1.1. 4. The design rule holds. No fallbacks anywhere in the species. Every operation has one path. HONEST BOUNDARY This test used the same setup shortcut as the two tests before it. The engine was given the key and core directly through Python method calls (set_key, set_core). A real buyer does not do this. A real buyer opens the species and answers nine setup questions. That setup program does not exist yet. Every test from CS-REAL-004 onward will use the real setup program. The buyer will be a buyer, not a code line. NEXT STEPS - Build the setup program (the 9 steps from the profile). - Retest with the real setup flow. - Then submit to CODECHECK. OUTPUT ARTIFACT Engine: engine/cryptospora_v12.py Script: tests/test_cs_real_003.py Results: results/cs_real_003.json Signed: Wagg · Owner: Family Tree Trust · Date: 2026-09-26 © 2026 Family Tree Trust. All rights reserved. Distributed by CTW, LLC.

CRYPTOSPORA SILENTIS — OFFICIAL TEST REPORT Test ID: CS-REAL-004 (Engine Reads the Real Setup File) Species: Cryptospora silentis (The Hidden Spore) Creator: Wagg · Owner: Family Tree Trust Date: 2026-09-27 System: Diamond Server (Python 3, real engine, 2 GB RAM) Document Type: Full Technical Record PURPOSE OF TEST Every earlier test handed the engine the key and core through Python code. A real buyer never does that. A real buyer fills the setup page and hits Finish. This is the first test where the engine reads the buyer's real setup file — spore_setup.json — and protects whatever the buyer pointed it at. No code shortcut. No hand-typed answers. THE BUYER'S SETUP The buyer filled the setup page and sealed it. The file was written to disk with these contents: - spore_id: cryptospora-5f6506e3efaf - core: /root/diamond/logograms - locations: three folders under /root/diamond/_spore_test - kill_switch: /root/diamond/_spore_test/KILL ACTUAL RESULTS | Step | Result | | Engine reads setup file | PASS | | Core path read correctly | PASS — /root/diamond/logograms | | Locations read correctly | PASS | | Core files read | 56 logogram images | | Logograms on disk | 56 — all read | | Fold | KILLED — process ran out of memory | | Unfold | Not reached | THE FAILURE The process was killed by the operating system during the fold. Reason: the engine tried to read all 56 logogram images, convert each to base64, pack them into one JSON blob, compress it, and encrypt it — all at the same time, in memory. On a 2 GB server, that is too much for one pass. WHAT PASSED The engine successfully read the buyer's real setup file. It knew the core path. It knew the three locations. It knew the kill switch. It read all 56 logograms on disk. The connection between the setup page and the engine is real. That half of the test worked. THE REAL FINDING The engine was built to hold the entire core in memory at once. That works for small cores (the earlier tests used a few lines of text). It does not work for a real buyer with a real folder of real files. A buyer's core could be one file. It could be a thousand. It could be gigabytes. The engine cannot assume it fits in memory. This is the same class of problem as Memoria vivum MV-015: the species tried to do too much at once and was killed by the operating system. The fix is the same kind of fix — process the core in pieces, not all at once. WHAT THIS TEST PROVES 1. The setup page writes a real file. 2. The engine reads that file on startup. 3. The engine knows the buyer's core and locations. 4. The engine reads the buyer's actual files. 5. The engine dies when the core is too large for memory. NEXT STEPS - Change the fold so it processes the core one file at a time. Memory stays small no matter how large the core. - Retest with the same 56 logograms. - If the fix works, retest with a much larger core. OUTPUT ARTIFACT Engine: engine/cryptospora_v12.py Script: tests/test_cs_real_004.py Results: results/cs_real_004.json Signed: Wagg · Owner: Family Tree Trust · Date: 2026-09-27 © 2026 Family Tree Trust. All rights reserved. Distributed by CTW, LLC.