209. Prismatic Lumen names the owner's mesh-wide view, and it owns no scheduler, event bus, store or API
Context
On 2026-10-18 the owner asked for one skill and one page that keep the tool updated, join the mesh, report regularly and act as the interface to the whole mesh, and chose the name prismatic-lumen over Oracle, Helm and Prism. The proposal that followed mapped it to /lumen, /ui/lumen, majordomus lumen and lumen.*; the critique the owner asked for warned that Lumen and Majordomus would compete (two cockpits, two context engines, two APIs) unless Lumen owned only interaction and projection.
Decision
Lumen is the name of a composed view: it reads the runtime's existing capabilities (blackboard, peers, mesh, monitor, intents) and invokes existing capabilities for any action. It adds no scheduler, event bus, store, registry or API namespace of its own. Its first slice is one page with freshness and reconnect recovery and one authorised action. Whether the name also becomes a route, CLI command, MCP namespace or skill is decided by the owner separately; until then the page is /ui/mesh. Scheduled reports, federation across Prismatic projects and a Pages gateway are out of its scope until each has its own measured problem.
Alternatives rejected
- Lumen as a separate application or repository
- Lumen as an orchestration layer above the mesh
- A lumen.* capability namespace duplicating mesh.*
Consequences
Lumen work is post-alpha and sequenced after 5a's blackboard and f6's /proceed entrypoint, each proposed on its own unlanded branch. docs/CONCEPTS.md gains one term. Intent the-owner-oversees-the-mesh-from-one-page carries it.
Sources
Promoted on 2026-10-18 from the owner's ChatGPT project (workspace chatgpt-majordomus, issue I3100). The owner has not accepted it; it is proposed for the owner's decision.
chatgpt-majordomus:c296#0chatgpt-majordomus:c296#8chatgpt-majordomus:c296#9chatgpt-majordomus:c296#14chatgpt-majordomus:c296#18