Section 01
Current State
Final Genspark milestone: V6 Safe Exit
Current implementation status: protected field-pilot MVP
Production readiness: not full production yet
Historical GenSpark capture gap: the original prototype enforced lock rules, correction policy, duplicate protection, auth, and validation client-side only
Section 02
Folder Map
01_processing/ holds the active prototype-capture container and any future upstream synthesis before stable promotion.
02_models/ is reserved for intentionally promoted stable MonguMeal model artifacts. It is currently empty on purpose.
03_assets/ stores project-owned operating assets such as checklists and reporting rules.
04_specs/ stores database, dashboard, and app requirements derived from the capture.
Section 03
Final V6 Preservation Locations
Final V6 source: 05_apps/02_src/Genspark_V6_Safe_Exit/
Final V6 technical docs: 05_apps/03_docs/technical_notes/Genspark_V6_Safe_Exit/
Live field-pilot current-state runbook: 05_apps/04_ops/runbooks/MONGUMEAL_FIELD_PILOT_CURRENT_STATE.md
Deployment and roadmap draft: 05_apps/04_ops/deploy/MONGUMEAL_DEPLOYMENT_AND_ROADMAP.md
Section 04
Older Snapshot Handling
Older frontend capture is preserved at 05_apps/02_src/archived_snapshots/Genspark_V3_Prototype_Snapshot/.
No separate V4 or V5 source bundle was captured on this branch. Their changes survive through the V6 safe-exit docs and changelog rather than standalone source folders.
Operators should not confuse archived snapshots with the final V6 safe-exit package.
Section 05
Rebuild Rule
Do not promote the preserved GenSpark app directly to production. Any future rebuild should move these controls server-side before deployment:
edit and delete lock enforcement
correction-session approval and expiry
weekly self-correction allowance
authentication and authorization
Section 06
Working Rule
Treat the GenSpark capture as source material and behavioral evidence. Extract durable logic into assets, specs, and eventually stable models before treating implementation details as canonical.