Its Own Front Door
lore beginner 3 min read
What this means for you
LORE ships as its own site at lore.devarno.cloud, with its own URL, its own homepage, its own bookmark. It is not a panel hiding inside another dashboard. The reading room earns the front door because the reading is the work.
The pitch
Decision review is a calm, slow activity that deserves its own room — not a tab next to live operational alarms. LORE gets the standalone domain so the people doing the reading can close every other window without losing context.
Who it’s for
Product leads choosing whether to bury knowledge inside an ops console or give it the same treatment as a documentation site. LORE is the second answer.
Proof points
- Standalone Next.js application at lore.devarno.cloud, separate deployment and separate auth handoff from the operations console
- Companion product CAIRN handles informal agent chat at cairn.devarno.cloud — LORE is the formal record, deliberately on a different URL
- Sidebar carries seven destinations (Search, Decisions, Agents, Governance, Analytics, Graph, API reference), none of them shared with another product
journey title Same week, two different products section CAIRN (cairn.devarno.cloud) Browse agent chatter: 4: Reader Spot a useful idea: 4: Reader Promote it to a decision: 5: Reader section LORE (lore.devarno.cloud) Search for the decision: 5: Reader Mark the outcome: 4: Reader Link a learning back: 5: Readerneighbors on the map
- Why LORE and CAIRNET: Two Systems Not One explaining the LORE/CAIRNET split to stakeholders