Ninad ruling (2026-08-15, CLI-262): a user talking to an agent gets the SAME experience irrespective of channel - WhatsApp or web. Recorded as a DESIGN POLICY and implemented unif\u2026

Ninad ruling (CLI-249, 2026-08-13): a certain TYPE of app must be designed a certain way, and the mechanism must BIND EVERY BUILDER, not just the operator - a skill only binds Ori\u2026

Ninad: the pipelines five states generalize to every service and track. Build the Service Tracker app: all services sorted by spend (highest first), tracks nested and spend-sorted\u2026

DISTINCT FROM CAROL-INI-3465, which covered SCHEDULED processes being charged under the wrong worker's name and is already delivered. This is about ACTIONS TAKEN FROM AN AGENT'S C\u2026

When an agent is asked a factual question, the query builder is told which databases it may read but never WHO is asking. So a question phrased in the first person -- 'how many de\u2026

A conscious agent's Mind is attached to model calls by looking up a self under the exact identity on the call. But agents almost never call under their own name -- their droids do\u2026

Ninad found Athena showing the being-built banner for 3 weeks. Three stacked causes: (1) her stored wiki row still carries status=being_built from before her identity file existed\u2026

Users need to hand an agent a file (e.g. a zip of their app for migration) through the chat. Carols chat has an attachment system but Leos chat only copied the frontend UI (no bac\u2026

Leos email side (his Reporter) and his chat side do not share awareness. The Reporter emailed Ninad an open question (recorded in leo_questions), but the chat reply builder never\u2026