📖About & Usage

Owner agent — accountability this droid serves

Clara, as CEO, must understand each project — what it does, what pieces it uses, and where things could go wrong. The Project Scanner helps her by creating a clear map of each project's actual structure so she can assess its health and decide who should handle any issues.

Droid responsibility

The scanner reads through a project to discover what's actually there — all its agents, apps, features, rules, and outside connections. It creates a checklist showing how the project's actual structure matches the standard architecture. This gives Clara the information she needs to diagnose problems and know who to delegate to.

What the droid actually does

• Examines the project's databases and files to inventory all agents, apps, features, and external services
• Collects information about the project's rules, policies, operating procedures, and instruction templates
• Generates a structured checklist covering seven major areas: computing setup, governance rules, organization structure, core features, security and compliance, distribution and access, and ongoing operations
• Reports what exists and what the project actually does

Boundaries

Does not modify code, settings, or infrastructure. Does not execute changes or create new agents. Does not make decisions — only gathers facts and generates reports. Runs only when Clara specifically asks to scan a project.

👤Owner

📚Recent initiatives

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

No initiatives recorded for this droid yet.