Clara escalated twice (the SST Scanner repeat-failure family on 2026-08-10, and the never-ran at-010/stw-010 family on 2026-08-02) and both escalations exist ONLY as rows in her o\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 (2026-08-12): (1) Remove the Folder Structure card (/home/caroladmin tree) from Carol Infra, including its backing folders endpoint and scanner. (2) The RAM headline (75.7%,\u2026

Ninad (CLI-238): the SST scan copies registry facts (owner, port, description) into sst.db and its app serves the copy - a second home for facts the registry owns, violating the o\u2026

Ninad moved Carolopedia to Bilbo and asked for a CLEAN transfer, plus a skill if none existed for doing it properly. MEASURED 2026-08-02 (CLI-201). Moving the app record alone is\u2026

The Source of Truth scan run at 20:41 on 2026-07-30 was killed by its own 2-hour limit. The nightly run six hours earlier, on a quiet machine, took 72 minutes - so the limit is no\u2026

Phase 1b of the spend-accountability plan (Ninad ruling, CLI-165: start with the droids consuming most of the cost, then continue with the others). The biggest spender is now pin\u2026

Service-driven ownership fix: the Source of Truth, Carol Org, Carolopedia, and Carolverse Roadmap apps are owned by Orion but belong to Clara (CEO/Governance) — the blocks (Knowle\u2026

The SST holds no public/browsable URLs (only ports, relative API paths, filesystem paths), and it lumps published blogs together with Orion work sessions with no slug. Two fixes t\u2026

The SST scanner indexes 21 categories but none for Orion session history. The Orion Logbook DB is only counted as one database file; its contents (what Orion did each CLI-NNN sess\u2026