Back to corpus
technical noteexperiment writeup candidatescore 40

CODEX PROMPT — LUME repo production-grade restructure

The repo at `[home]/Desktop/lume-commerce/` is functionally production code masquerading as demo code. The Unity bar visualization, live LaunchAgent service plists, mocopi/audio bridges, and pytest suite all live under `software/demo/` — a path that misleads anyone reading the tree.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

Paste-ready. Run on Mac1 (canonical tree). Estimated wall time: 2-4 hours. ~12-15 commits across 3 stages. The repo at `[home]/Desktop/lume-commerce/` is functionally production code masquerading as demo code. The Unity bar visualization, live LaunchAgent service plists, mocopi/audio bridges, and pytest suite all live under `software/demo/` — a path that misleads anyone reading the tree. Your job: restructure to enterprise-level monorepo with proper service/app/package boundaries, while preserving git history (every file move uses `git mv`), Unity .meta GUIDs (don't use raw `mv`), and runtime continuity (LaunchAgent paths re-bootstrapped, Python imports updated, K11 NSSM paths updated before next K11 reboot). **Current state ground truth (verify before starting):** - HEAD = `83b565e3 [W9M] launchd plist for Sony→LUMM bridge service` - Pytest baseline: `139 passed, 6 skipped` - Wave 8 tip: `da8d1478` (DON'T TOUCH) - 8 unpushed commits since Wave 8. M-1 PAT rotation pending. DO NOT push to origin. - Stale git index.lock at `.git/index.lock` from yesterday's Codex absorption — `rm` it before starting. **Required reading before action:** 1. `[home-path]` — the audit + risk matrix 2. `[home-path]` — overall state 3. `Desktop/evo-cube-output/lume-creative-engine-2026-05-02/DIVERGENT-RAIL-2026-05-03.md` — forward roadmap 4. `[home-path]` — Duncan v3 priorities (informs which Wave 9 components are next)

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.