Project · Reader View

MonguMeal Project

MonguMeal project orientation.

View canonical Markdown copy Browse registered workspace
Reader View — generated from canonical Markdown.
This page uses the LifeHub Reader Site Styler skill for presentation, but it is still derivative. If it conflicts with the Markdown source, the Markdown controls.
Polished Reader ViewDesigned for study, browsing, and mobile reading.
Markdown Source ViewIn-site display copy for side-by-side verification.
Canonical RuleRepository Markdown remains the source of truth.
Canonical PathLifeHub/02_projects/MonguMeal/README.md
Source SHA-256704006e81185192cd69e28dd7526a6de47aaf9537a8ec15eefbf249f9b022433
Generatedregistry-2026-07-06-styler-test
PolicyLifeHub/08_admin/03_operator/READER_VIEW_POLICY.md
Design SkillLifeHub/03_systems/AI_Operator_Continuity/skills/lifehub-reader-site-styler.md

MonguMeal Project Workspace

MonguMeal now follows the current LifeHub project structure. This project preserves the GenSpark-origin capture while recognizing the live app as a Hermes-hardened backend/client MVP and protected field-pilot app. It is not full production yet, but it is also no longer only a preserved prototype.

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
  • Current Hermes MVP status: core validation, duplicate-date protection, server-calculated revenue, lock/edit rules, and correction policy are server-enforced for the field pilot; app-level auth is still not implemented.
  • Current live runtime paths: production and preview are documented in 05_apps/04_ops/runbooks/MONGUMEAL_FIELD_PILOT_CURRENT_STATE.md.
  • Current services: mongumeal.service (production) and mongumeal-preview.service (preview).
  • Current pilot URLs are documented in 05_apps/04_ops/README.md.

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.
  • 05_apps/ stores the preserved app source snapshots plus any future rebuild planning, docs, and ops work.
  • 05_apps/04_ops/ stores current-state notes, deployment planning, scripts, and runbooks for the live field pilot.
  • 06_outputs/ stores review-ready preservation artifacts, reports, screenshots, and normalization records.

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
  • Final V6 screenshots, final report, and public URL record: 06_outputs/Genspark_V6_Safe_Exit/
  • Normalization report for this branch: 06_outputs/MONGUMEAL_CAPTURE_NORMALIZATION_REPORT.md

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.

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
  • duplicate-date protection
  • field validation and revenue verification

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. For live pilot work, treat the current running service and its current-state docs as authoritative until a deliberate cutover is planned.