📖About & Usage

About

In Carol's AI ecosystem, many agents need to do the same kind of thing — send a notification, look up a policy, generate a report. Rather than each agent reinventing the wheel, these shared capabilities are packaged as droids (small, reusable functions an agent can call). When the same droid appears across multiple agents, sometimes with local tweaks, it forms a droid family: one canonical version plus all the agent-specific variations.

Droid Families is the app that maps this landscape. Owned by Athena, it gives Agent Resources a single view of every cross-agent droid family — showing the "main" droid, which agents carry a copy, and what customizations each agent has made. It also surfaces potential future families: clusters of similar logic that could be consolidated into a shared droid but haven't been yet. Think of it as a genealogy chart for Carol's reusable building blocks.

Usage Patterns

Athena and her team use Droid Families when onboarding a new agent, deciding which existing droids it should inherit, or when auditing duplication across the organisation. For example, if Forge builds a handy utility droid for Elrond's engineering team and Merlin later needs something almost identical, Agent Resources can open Droid Families, spot the overlap, and promote the droid into an official family — with one well-maintained main version and lightweight per-agent customizations.

The app is also useful during periodic housekeeping: scanning for "potential families" highlights places where multiple agents have quietly built near-identical functions, signalling an opportunity to refactor and reduce maintenance overhead. It lives within the agent_apps card group and is accessible to authenticated users at its dedicated portal.

🗂️Tabs & Screens

Tab inventory is being built — see CAROL-INI-077 step 7.

👤Owner

📚Recent initiatives

Initiatives that touched this app — a short summary each; open one for the full story.