GOD v3300 BETA 3 - TRUE SEED EVOLUTION

RECOMMENDED START
1. Extract this ZIP to its own folder.
2. Double-click SELF_TEST_GOD_BETA.cmd.
3. If it passes, double-click START_GOD_BETA.cmd.
4. Start God normally.

WHAT WAS WRONG
- Use as Input recorded a selection, but the automatic evolution cycle did not reliably prioritise that selected image.
- The generator usually rotated through baseline/core-derived runtime images.
- Automatic seed activation accepted only sources it could trace directly to a protected core; generated parents often failed that test.
- One autonomous module changed the in-memory learned list without using the persistent registry write path.
- Unique IDs prevented exact identity collisions but there was no visual near-duplicate gate.

WHAT BETA 3 CHANGES
- Use as Next Seed now prioritises the exact selected image in the next evolution cycle.
- Persistent learned seeds and paired learned seeds are first-class future generation sources.
- Descendants retain parentId, coreSourceId, generation depth, and complete lineage.
- Automatic activation uses the persistent seed-registry API and IndexedDB rather than RAM-only mutation.
- Generated-parent source resolution follows generated, learned, active, and core source pools.
- A visual fingerprint gate holds near-duplicate evolved images instead of storing them repeatedly.
- Seed sources rotate away from recently used parents and favour underused learned seeds.
- Evolution uses a monotonic serial that does not reset when older images are pruned.
- Added Evolve Current Seed Now and a live True Seed Evolution audit.
- Learned seeds are not automatically forced into view during a background restore unless selection was explicitly requested.

PRESERVATION
- The protected 21 core seeds are unchanged.
- All 52 embedded image/source payloads are byte-for-byte unchanged from Beta 2.
- Existing learned-seed databases remain compatible.
- No external image generator is claimed; imagery is created locally from available source images.

TRUTH BOUNDARY
The application can use only information and images actually available to its runtime. It does not gain access to hidden, private, unretrieved, or future information merely by evolving a seed.
