Chowpatty was added to the business-lines registry with its human owner stored as the text 'Ninad' while the other four store the user id 1. Align Chowpatty to id 1 so the field i\u2026

Follow-up to the service-model unification. (1) Chowpatty, Prancing Pony and Ventures are aspirational service rows that are really BUSINESSES — the business-lines registry sits a\u2026

Replace direct send_whatsapp calls in chowpatty with relay_to_carol so user-facing messages are drafted by Carol per policy P.01.02.07.03. Primitive landed in INI-745.

Create services/knight-bus/ as parent service for Carols direct-delivery brand (own service_meta, prompt, tools, droids, internal sub-routing for restaurant children). Move servic\u2026

Register the missing Carolverse services so every org function is a service with a distinct owner (1 agent : 1 service). New catalog entries: WhatsApp Assistant (Galadriel), Sales\u2026

Policy P.01.02.07.03 mandates that every user-facing message be drafted by Carol. Current violators (direct sends): subscription_approver (Clara INI-718 ceremony), proactive, vent\u2026

Catalog overhaul. (1) Add audience (external/internal) + readiness (ready/wip/concept) fields to every service_meta.json. (2) Set owner_agent per Ninad: Blueprint=Leo, Initiatives\u2026

Carol per-turn inference is bottlenecked by the 43KB system prompt. Targets: dedup repeated guard rules in RESPONSE STYLE (~29 lines of similar never-expose-X rules), move CHOWPAT\u2026

Currently, all users have access to all service tools (initiatives, chowpatty, frankfurt-food) regardless of their subscription status. We need to enforce subscription-based gatin\u2026