Enforce policy P.04.01.06.08: every LLM call must be attributed to a droid owned by a registered Carolverse agent. 1) Fix ~81 LLM call sites across 65 files to pass agent_id. 2) F\u2026

Enforce policy P.04.01.06.08: every LLM call must be attributed to a droid owned by a registered Carolverse agent. 1) Fix ~81 LLM call sites across 65 files to pass agent_id. 2) F\u2026

Enforce policy P.04.01.06.08: every LLM call must be attributed to a droid owned by a registered Carolverse agent. 1) Fix ~81 LLM call sites across 65 files to pass agent_id. 2) F\u2026

Forge, Argus, and Radagast currently execute commands locally on carol-vm. They need a mode where they SSH into the target project's VM and run the work there instead. The vault c\u2026

On 2026-06-28 data/registry.db was clobbered to a ~12KB stub (only incoming_requests; agents/droids/apps gone), restored from a copy. Root vulnerability: ~15 apps open registry.db\u2026

The registry mixes operational identity (droids/apps, ~40 writers, fine under one caroladmin writer) with crown jewels (access-control RBAC + credential vault) that must be write-\u2026

Option 1 hygiene (distinct from 1908 which is Radagast verifier reads). (a) Make the on-disk initiatives DB owned/writable ONLY by Elronds writer daemon so stray writers (tests/gh\u2026

When Elronds initiatives writer/relay is down, Radagasts admin verify refuses every action because it reads the initiative through that very writer - a circular dependency that ma\u2026

Remove the leftover Radagast membership in the Security service. Heimdall is the CISO and already owns the Security service; Radagast should belong to the initiatives service only\u2026

Use the create-a-new-skill meta activity (type SK) to author and WIRE a new Sage-owned activity skill named 'decommission-entity' (suggested type code DC). ACTIVITY: Safely retir\u2026