CRYPTOSPORA SILENTIS — OFFICIAL TEST REPORT Test ID: CS-REAL-001 (First Real Engine Test) 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 This is the first test of Cryptospora silentis that runs real code. No simulation. No narrative description of what should happen. The engine was installed, given a real core, and put through seven real scenarios on the server. WHAT WAS TESTED Seven scenarios, all against real files on disk: 1. Fold — the species compresses, encrypts, and writes three copies 2. Encryption — verify the core cannot be read without the key 3. Unfold with correct password 4. Unfold with wrong password 5. Recovery after one copy is corrupted 6. Patience Core — the species must see stability three times before waking 7. Kill switch — the species deletes every copy SETUP - Spore ID: cs-real-001 - Core: identity, purpose, memory of the first real test - Password: given at setup, never stored - Locations: three real folders on the server ACTUAL RESULTS TEST 1 — FOLD | Metric | Value | | Success | True | | Time | 0.0028 s | | Files written | 3 | | Size per file | 253 bytes | Three encrypted copies appeared on disk in 2.8 milliseconds. TEST 2 — ENCRYPTION | Metric | Value | | Plaintext visible in file | False | The core content ("This is the first real Cryptospora core.") was searched for in the encrypted file. It was not found. The encryption is real. TEST 3 — UNFOLD | Metric | Value | | Success | True | | Time | 0.2894 s | | Integrity | 1.0 | | Core matches original | True | The core was restored exactly. Every field matched. TEST 4 — WRONG PASSWORD | Metric | Value | | Wrong password unfolds | False | A wrong password cannot unlock the core. The buyer's key is required. TEST 5 — RECOVERY AFTER CORRUPTION | Metric | Value | | Recovery after corrupting one copy | True | | Core still matches | True | One copy was corrupted with real bytes. The species rebuilt from another copy. Redundancy works. TEST 6 — PATIENCE CORE | Check | Stable? | | After 1 check | False | | After 2 checks | False | | After 3 checks | True | The species did not wake after one stable reading. It waited for three consecutive readings before unfolding. Premature waking is blocked. TEST 7 — KILL SWITCH | Metric | Value | | After KILL file | KILLED | | Files remaining | 0 | Every copy was deleted. No trace. No resurrection. RESULT PASS — all 7 real scenarios succeeded. WHAT THIS PROVES 1. The engine exists as real Python code. 2. The encryption is real AES — the core cannot be read without the buyer's password. 3. The checksums are real — corrupt copies are detected. 4. The redundancy is real — three copies, any one survives the loss of the others. 5. The Patience Core is real — three consecutive stable readings are required. 6. The kill switch is real — every copy is deleted on command. 7. The design matches the engine. What the profile says the species does, the engine does. HONEST BOUNDARY The engine implements six of the fifteen components. Nine remain: Continuous Micro-Folding, Hardened Trigger, Camouflage Layer, Micro-Repair Cycle, Spore Recognition Protocol, Enhanced Camouflage Layer, Decoy System, Enhanced Micro-Repair Cycle, Redundant Core Copies. Those nine will be added in later engine versions, each with its own real test. The core used was small — a few lines of text. A real buyer's core might be larger. Scale testing comes next. OUTPUT ARTIFACT Engine: engine/cryptospora_v1.py Script: tests/test_cs_real_001.py Results: results/cs_real_001.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-002 (All Fifteen Components) 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 Test CS-REAL-001 proved the six core components of the engine worked. This test runs the engine with all fifteen components added in one update. Thirteen scenarios are exercised against real files on disk. SETUP - Spore ID: cs-real-002 - Core: identity, purpose, memory - Password: set at setup, never stored - Locations: three real folders - Shadow: one autosave folder - Presence: one shared directory - Kill file: one trigger path ACTUAL RESULTS | # | Test | Result | | 1 | Fold (all components active) | PASS — 12 files written in 0.0023s | | 2 | Encryption | PASS — plaintext not visible | | 3 | Camouflage (hidden-named files) | PASS — 8 hidden files | | 4 | Spore Recognition (presence) | PASS — presence file written | | 5 | Continuous Micro-Folding | PASS — autosave exists, 278 bytes | | 6 | Unfold | PASS — core matched, integrity 1.0 | | 7 | Wrong password | FAIL — wrong password unlocked the core | | 8 | Decoy System | PASS — 18 hidden .spore files | | 9 | Micro-Repair Cycle | PASS — 28 copies alive | | 10 | Patience Core | PASS — 3 checks required | | 11 | Enhanced Micro-Repair (template) | PASS — recovered after corruption | | 12 | Redundant Core Copies | PASS — 52 core-bearing files | | 13 | Kill Switch | PASS — 0 files remaining | THE FAILURE: WRONG PASSWORD In v1.0, a wrong password could not unlock the core. In v1.1 it can. Cause: The Enhanced Micro-Repair component (component 14) includes a template fallback. When decryption fails because the password is wrong, the engine falls back to the stored template and hands the buyer back the core anyway. The template was intended to repair a damaged core. It was not intended to bypass the password. The current implementation cannot tell the difference between "the core is damaged" and "the password is wrong" — so it treats both the same way and restores from the template. This means the encryption is not currently protecting the core. Anyone who has access to the files can unfold without the key. THE SECOND PROBLEM: FILE COUNT One fold of one small core produced: - 12 files written immediately - 52 total core-bearing files across all locations - 18 hidden .spore files (camouflage + decoys) - 28 copies alive at one point On a real buyer's system this is disk bloat. The species is supposed to be quiet. It is not yet quiet enough. WHAT THIS TEST PROVES 1. All fifteen components run without crashing. 2. Fold and unfold work end to end with all components active. 3. Camouflage, decoys, autosave, and presence all function. 4. Patience Core still requires three consecutive checks. 5. Kill switch still removes everything cleanly. 6. Two real bugs were found: password bypass and file bloat. HONEST BOUNDARY This test exercised thirteen scenarios. The tests that passed passed honestly. The tests that failed failed honestly. Both failures are recorded. NEXT STEPS - Fix the template fallback so it cannot bypass the password. A correct password must be required for every unfold. - Reduce the file count per fold. Consolidate the camouflage and decoy files. Cap the total files the species may write per fold. - Add a resource discipline test that measures CPU time and memory used by every operation. - Retest with the fixes. OUTPUT ARTIFACT Engine: engine/cryptospora_v11.py Script: tests/test_cs_real_002.py Results: results/cs_real_002.json Signed: Wagg · Owner: Family Tree Trust · Date: 2026-09-26 © 2026 Family Tree Trust. All rights reserved. Distributed by CTW, LLC.