Argus's design-compliance verifier flags two false positives on every standard dev app (pipeline-rsi, admin, droid-families all fail identically): (1) it greps the app HTML for th\u2026

On broad screen widths a card grid that shows only 1-2 cards per row looks sparse and wastes space. New design practice (Archon / Design System #178): card grids should target 3-4\u2026

The shared global header (injected on every dev page via the dl-static global-footer.js) hardcodes the topbar OWNER badge to 'Carol' (and links it to Orion's org page) for ALL Car\u2026

New app owned by Athena (Head of Agent Resources) showing droid FAMILIES — functions replicated across multiple agents (e.g. App Steward x17, Twin Reviewer, Failure Watcher, Repor\u2026

On the Carolopedia agents landing page the lead can appear at the bottom of a service group: the security team has Heimdall (owner/lead) at level 6 but his four reports at level 5\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

Heimdall (CISO) has zero reports and zero droids despite owning Carolverse access management + security posture. Stand up a CISO org as new agents reporting to Heimdall, each owni\u2026

Listing cards show a tiny circular pic; the source emblem is rectangular so it looks small. Trial a new card layout on the first four services (agent-resources, audit, blogs, blue\u2026

On each Carolopedia agent page, add a Go to org button directly below the existing Go to profile button. It links to the agent card in Carols org chart using the chart existing #<\u2026

Agent Carolopedia profiles do not show which service the agent belongs to. Add a Service card to each agent page, linking to the service. Derive it: service_agents owner/support f\u2026