Status: lightweight index for durable reports, plans, audits, and human-readable artifacts. Owner: Luci Created: 2026-05-21
This directory is where Luci saves durable human-readable outputs that Elmar may want to revisit: plans, reports, test results, audits, diagrams, and progress trackers.
This index exists because we have historically saved related material in several places. Use this rule of thumb:
~/workspace/reports/ = reports, plans, audits, diagrams, progress trackers.~/workspace/mission-control/docs/ = canonical architecture contracts for Mission Control code/runtime behavior.~/workspace/wiki/ = broader operational/reference knowledge.~/workspace/tasks/ = scheduled task definitions only.~/workspace/luci-manifest.md and ~/workspace/CAPABILITIES.md = deployed inventory and capabilities.If a report becomes a canonical architecture contract, create/update a file in mission-control/docs/ and link both ways.
| Topic | File | Status | Notes |
|---|---|---|---|
| Luci Control Room + Runtime Independence | luci-control-room-runtime-independence-plan.md |
Active | Plan to get more from Hermes while keeping MC runtime-agnostic and resilient to runtime retirements. |
| MC Orchestrator Flow | mc-orchestrator-flow-diagram.html |
Reference | Existing visual flow report referenced by Elmar. |
| MC Orchestrator Flow Design | mc-orchestrator-flow-design.md |
Reference | Supporting design notes for orchestrator flow. |
| Control Room + Hermes Kanban Internal Workbench | council-orchestration-plans/control-room-hermes-kanban-internal-workbench-plan-v1.md |
Council-reviewed | Companion to v2.1; keeps MC as visible source of truth and Kanban as internal Hermes-profile workbench. |
| Hermes Kanban Research Notes | council-orchestration-plans/hermes-kanban-research-2026-06-02.md |
Reference | Local docs/source/CLI research grounding the internal workbench plan. |
| MC/Hermes Kanban Council Review | council-orchestration-plans/council-review-kanban-v1-synthesis.md |
Reference | Council synthesis and accepted plan amendments, including Opus follow-up. |
| MC/Hermes Kanban Opus Follow-up Review | council-orchestration-plans/reviews-kanban-v1/opus-review.md |
Reference | Opus review covering separate-board isolation, archive semantics, harvest owner, dispatcher claim risk, and schema fallback. |
Use:
topic-plan.md for living plans/progress trackers.topic-YYYY-MM-DD.md for dated reports.topic-test-results-N.md for sequential test runs.topic.html for visual artifacts/diagrams.When creating an important new report or living plan:
~/workspace/reports/.luci-manifest.md, CAPABILITIES.md, and/or the relevant mission-control/docs/ architecture file.If it is part of an active initiative, include a checklist and update it rather than relying on chat history.
lucienne-review-luci-runtime-independence-hermes-client-addendum-2026-05-22.md — Lucienne addendum connecting lotsoftick/hermes_client to the MC runtime-independence plan.
hermes-profile-runtime-adapter-implementation-brief-2026-05-22.md — Lucienne implementation brief for making Mission Control's Hermes runtime adapter honest, inspectable, and ready for coder-lane work.