Registry definitions
The registry is available through the workspace and the public Agent Registry. Its GET /api/agents endpoint accepts query filters. It includes specialists across marketing, sales, finance, engineering, product, design, support, success, HR, IT, operations, data and legal work. Each definition lists its mission, instructions, inputs, outputs, quality checks and conceptual tool boundary. Platform roles coordinate and review the work.
Creature character library
Book Demo’s What to expect section uses the supplied pastel hologram illustration at its original proportions behind accessible HTML content and describes four informational walkthrough stages: goals, use cases, tailored demo and next steps. Book Demo presents its three plans in illustrated cards; the Recommended Founders badge is a presentation recommendation, not measured popularity. Its closing banner uses Starry Friends artwork, distinct from the Explorers footer. Its mobile footer separates artwork from navigation and copyright. The shared public footer uses five supplied backgrounds selected by page group across public pages, with a clean boundary and no gradient transition band. Its embedded character group replaces the separate footer portraits. The invitation and demo button sit beneath the logo, clear of the artwork. All 28 employee characters use the approved static reference artwork. Marketing ensembles, employee profiles, compact avatars, integration examples and the footer share the same stable employee-ID mapping. No exported employee 3D models or Blender renders are loaded. Shared marketing groups space each character in its own lane and use gentle staggered CSS motion. Hover pauses the group, and reduced-motion preferences disable animation. This movement is decorative and does not represent live employee activity.
The 28 employee characters use individual high-definition transparent PNG illustrations in web/public/ai-workforce/avatars-hd/. Stable registry IDs select each image through StaticEmployee, and each illustration preserves its role-specific character and props. The retired cropped tile images are no longer used. The Pod Manager preview shows the crowned lion. Characters and their idle motion are presentation assets, not live workers.
Assigning specialists
Choose specialists when creating a Pod. A Pod must have at least one and can have at most 25. Before execution begins, a specialist can be added or removed and the task plan refreshes. The application checks category-related company permissions for certain finance, legal and production tasks.
Operational status
The workspace derives employee state from persisted Pod tasks: idle, planning, working, waiting, blocked, awaiting approval, completed or error. These are work states, not a claim of autonomous external activity.
What a role cannot imply
A role card does not itself connect Slack, a CRM, a repository or a finance system. In live mode, compatible text-model gateways can draft text. External side effects need explicit adapters, scoped credentials and authorization.