OPERATOR EMERGENCY (Ninad 2026-07-03), explicitly NOT the CAROL-INI-2128 feature work: the gate built by 2128 is live and pausing EVERY dispatch right now — including 2128s own pl\u2026

Today there is no UI surface anywhere in Carol that shows what an agent or droid is actually instructed to do. Agent identity (character, roles, rights, duties) is exposed via /ap\u2026

Ninad ruling (CLI-024): both cost apps belong to Midas with names that say what they track. (1) The LLM/initiative cost app (port 7174, /dev/carol-costs/, today 'Carol Cost Monito\u2026

Convert the Visit-time chart from one aggregate bar into a stacked bar where each segment is one DISTINCT visitor time that day, identified by email or by anon:IP for anonymous vi\u2026

Ninad report (CLI-024): GET /dev/costs/ -> 404. DISAMBIGUATION vs CAROL-INI-2318-02: that initiative fixed the Carol Cost MONITOR (port 7174, /dev/carol-costs/, LLM token costs, _\u2026

Admin Monitor stats: the Distinct Visitors chart counts only identified (email) visitors (CAROL-INI-1862), so days with only anonymous external visits show 0 distinct visitors eve\u2026

Admin Monitor stats: the Distinct Visitors chart counts only identified (email) visitors (CAROL-INI-1862), so days with only anonymous external visits show 0 distinct visitors eve\u2026

Today there is no UI surface anywhere in Carol that shows what an agent or droid is actually instructed to do. Agent identity (character, roles, rights, duties) is exposed via /ap\u2026

After CAROL-INI-043 moved the regression runner to carol-vm, sweep all Carol code/data/docs/configs for any other laptop-side references. The VM-native artifact rule (Ninad 2026-0\u2026

Requirement from Ninad (2026-07-02): EVERY Carol interaction that sounds like a request must be recorded in the Requests inbox (registry incoming_requests via the shared inbox mod\u2026