Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

๐Ÿ“– Carolopedia โ€บ Apps โ€บ Leo ChatMain page
Leo Chat

Leo Chat

App Leo's external chat - the front door of the blueprint service and the action surface of the BLOOM methodology. Actions available in chat: register a project, the 22-question requirements walk (which writes the project definition record on completion), strategy draft + gap questions, hosting cost forecast and confirmation, roadmap drafting (which writes the project phase record), initiative filing, project status and progress, and the Phase-1 artifacts: the blanket contract, the project org (Carolverse-owned vs project-owned), and the operating model. Registered per action in agent_actions (CAROL-INI-3831). Phase-2 (Learn) actions: measured estimates quoted with every roadmap, roadmap approval (the artifact that unlocks filing), service recommendation and enablement (CAROL-INI-3832). Phase-3 (Orchestrate) actions: budget envelope set at approval, execution plan in delivery order, generated weekly status reports (CAROL-INI-3833). Phase-4 (Optimize) actions: record learnings, propose new services via governed intake, conversion checklist; weekly Blueprint RSI Engine v2 files one improvement at a time (CAROL-INI-3834). Phase-5 (Manage) actions: monthly invoice generated from the records, obligations ledger with evidence (CAROL-INI-3835).
Go to app โ†’

๐Ÿ“–About & Usage

About

Leo Chat App is a chat assistant droid owned by Leo. It exists to give Leo an always-available chat interface, separate from general Carol-side chat apps such as Carol Chat. It runs as a daemon with no scheduled batch job, so it can respond whenever needed.

Its registry entry classifies it as part of no named droid family โ€” it lands in the catch-all "(none)" bucket shared with 222 other unaffiliated droids โ€” but its exact name, "Leo Chat App", is unique, so it is not a reusable family that other agents copy.

The droid is pure software: no Claude calls were found in its source, so it does not invoke a Claude model. Its behaviour comes from deterministic app logic, not from an LLM.

๐Ÿ›ฐ๏ธUpdates

Dated notes from recent initiatives โ€” the main entry above is not rewritten.

Fix2026-07-24

Owner Ninad is now gate, so he can message Leo without a Blueprint subscription.

Fix2026-07-24

Added the /history route and corrected the SSE event stream path from absolute /api/events to the app-prefixed path, reconciling the leo-chat frontend with its backend so message pagination and status updates work without 404s.

New Capability2026-07-02

Leo Chat now has a Feedback Applier that automatically updates roadmap entries and initiative definitions from Ninad feedback, with a full audit trail, and confirms the changes back in chat. This integrates Governance and Audit & Compliance for traceability.

โš™๏ธShared machinery it uses (2)

Worked out from what this app actually calls โ€” it builds none of this itself.

Membership DeskTalk-To-Me Chat

๐Ÿ—‚๏ธTabs & Screens

Tab inventory is being built โ€” see CAROL-INI-077 step 7.

๐Ÿ‘คOwner

Leo ยท Head of Strategy

๐Ÿ“šRecent initiatives

Initiatives that touched this app โ€” a short summary each; open one for the full story.

CAROL-INI-3872-00: Converge every chat door onto the one engine: Carol, Leo and Sam chats served by the same turn pipeline as the org window, fences per door
Ninad direction (2026-08-15), builds on the intelligence design. Today four apps run four turn engines, so every upgrade (grounding, citations, chips, the coming loop) lands four\u2026
Orion · 2026-08-18 18:54
CAROL-INI-3809-00: Delivery-compliance checker is blind to the shared canon window template
Found by CAROL-INI-3808's close gate (its autonomous follow-on filing was refused by the pipeline-off intake gate, so the operator files it per cookbook 1225). Themis-style design\u2026
Orion · 2026-08-16 18:54
CAROL-INI-3787-00: Agent chat per-agent tracks: Leo Chat and Carol Chat, channel-agnostic, budget follows the interlocutor
Ninad rulings (CLI-243, 2026-08-12): (1) Leo's chat has TWO aspects like Carol's - the INTERNAL (employee) chat for a project's contributors, and the EXTERNAL chat for users subsc\u2026
Orion · 2026-08-14 18:53
Browse all initiatives →