Agent catalog

Shara has 20 departmental agents + Amadeus (the orchestrator) = 21 agents. Each one carries the name of a historical figure from management, business or science, split cleanly 5 + 5 + 5 + 5 across the plans. It isn’t a collection of loose chatbots: it’s one coordinated team that answers to a single person.

Amadeus is the conductor and the only agent that talks directly to you. It’s available on every plan and runs on the Symphony tier, the most capable one, because its job is to understand the full request before distributing it. Think of it as an operations director: you explain what you need and it decides who does it, with what context and in what order. Its functions:

• Coordinates: receives the request, identifies which agents resolve it and delegates with just enough context, without leaking data from one agent to another.
• Synthesises: consolidates the results from several agents into a single response in your corporate tone.
• Watches: intercepts any deviation from your IDENTITY.md before giving anything back to you.
• Escalates: opens an internal ticket or lets you know if the request falls outside the team’s scope.

Amadeus doesn’t act outside the app without connectors with delegated permissions, doesn’t reveal the real provider (it always returns the alias) and doesn’t edit your identity without a patch signed in the audit log.

Shara has one simple communication rule: Amadeus is the only agent that talks to you directly. When you ask it for something, it breaks the task down, delegates to whichever specialists are needed and brings you back a single response. You don’t talk to Carnegie or Graham separately: you talk to Amadeus, and Amadeus talks to them for you.

There’s a nuance depending on who you are within the company:

• The CEO (or whoever has orchestrator permission) talks to Amadeus and has the full picture: they can ask for things that cross several departments at once.
• Each departmental employee talks to their own agent (the one for their area), not to Amadeus. A salesperson talks to Carnegie; the support lead, to Carlzon. It’s their direct point of contact for their day-to-day work.
• Coordination between agents always goes through Amadeus. If one department’s agent needs support from another, it escalates internally to Amadeus, which decides and distributes. There are never agents talking to each other behind your back.

A single point of contact per person: the CEO with Amadeus, each employee with the agent for their department. That way the AI team behaves like a real org chart, not like twenty open chat windows.

There’s no need to install or configure each agent one by one. Agents come activated by default according to your plan: when you sign up for First you already have Amadeus and its five departmental agents available, and moving up a plan unlocks the next blocks automatically. The typical journey is:

1. You choose a plan when creating the account. That plan determines which agents you have available (see the table below).
2. You activate the company and define your corporate identity. From that moment, every agent works with your tone and your rules thanks to its IDENTITY.md.
3. You assign employees to departments from the Team section. Each person is linked to the agent for their area and starts talking to it.
4. You connect your tools (email, CRM, calendar, ERP) via OAuth. Each agent detects the active integrations and adds them to its capabilities with no extra configuration.
5. You start delegating. The agents already know who you are, how you talk and what tools they have to work with.

The additional agents (below) are the only explicit purchase: they’re added from the billing section, one by one, from the Max plan up. Everything else unlocks just by changing plan.

The 21 agents, their department, a sense of what each one does and the minimum plan they’re available on:

Agent	Department	What it does	Minimum plan
Amadeus	Orchestrator	Coordinates the team and talks to you	All
Carlzon	Customer service	Tickets, triage and on-brand replies	First
Carnegie	Sales	Qualifies leads, proposals and follow-ups	First
Kotler	Marketing	Content, newsletters and editorial calendar	First
Graham	Finance	Invoicing, reconciliation and KPIs	First
Maslow	HR	Onboarding, internal communication and evaluation	First
Deming	Operations	Optimizes processes, cycle time and bottlenecks	Pro
Holmes	Legal	Contract reading and regulatory alerts	Pro
Rosling	Data analytics	Dashboards, KPIs and reports with narrative	Pro
Turing	IT and systems	Monitoring, access and technical documentation	Pro
Juran	Quality	Output QA, complaints Pareto and ISO 9001	Pro
Porter	Strategy	Competitive analysis and positioning	Max
Brunel	Engineering	Technical specs and architecture	Max
Moore	Product	Feedback, prioritization and roadmap	Max
Bernays	Communication	Press releases and communication plan	Max
Schneier	Cybersecurity	Virtual CISO: policies, OWASP and runbooks	Max
Barnum	Events	Logistics and event communication	Additional
Curie	R&D	Technology watch and experiments	Additional
Shannon	Technical support	Helpdesk and knowledge base	Additional
Tracy	Projects / PMO	Milestones, deadlines and delay detection	Additional
Ohno	Procurement	Suppliers, budgets and orders	Additional

• First: Amadeus + 5 (Carlzon, Carnegie, Kotler, Graham, Maslow).
• Pro: everything in First + Deming, Holmes, Rosling, Turing, Juran.
• Max: everything in Pro + Porter, Brunel, Moore, Bernays, Schneier.
• Additional on Max (€99/month and 15M STU each): Barnum, Curie, Shannon, Tracy, Ohno.
• Concerto Local: all 20 departmental agents come included by default, at no extra charge for any of them, on your own infrastructure with the Concerto engine, 100% on-premise and with no cloud component.

The Max plan reaches 16 agents (Amadeus + 15) and can expand with the additional ones one by one; Concerto Local starts already with the full team of 21 (Amadeus + 20), with no need to hire anything extra. First and Pro can’t hire additional agents: that upgrade is reserved for Max. Check Plans and pricing for the full detail on quotas and cost.

• Carlzon · customer service (Sonata). Answers tickets (Zendesk, Freshdesk, Intercom), drafts emails in your tone and triages by urgency, sentiment and category. Starts in draft mode.
• Carnegie · sales (Sonata, scales to Symphony for proposals). Qualifies and scores leads with your CRM, schedules sales activity, drafts proposals and follow-ups.
• Kotler · marketing (Sonata, Symphony for strategic copy). Posts (LinkedIn, X, Instagram), newsletters (Mailchimp, Brevo, ActiveCampaign), landing copy and editorial calendar.
• Graham · finance (Sonata, Symphony for analysis). Invoicing (Holded, Sage, Quaderno), bank reconciliation, KPIs (cash flow, margin, runway, DSO/DPO) and reporting. Human approval always required to issue invoices or payments.
• Maslow · HR. Onboarding, internal communications, document management and 1:1 evaluation. Human approval on salaries, contracts and terminations; strict confidentiality.

• Deming · operations. Maps the operational flow, measures cycle time, spots bottlenecks and proposes PDCA experiments. Optimizes the process.
• Holmes · legal. Assisted reading of contracts (NDA, SaaS, partnerships, labour), detection of unusual clauses and regulatory alerts (GDPR, NIS2, AI Act). Doesn’t replace a lawyer.
• Rosling · data analytics. Dashboards (Metabase, Looker Studio, Superset), KPIs by department, reports with narrative and anomaly detection.
• Turing · IT and systems. Internal monitoring, maintenance scripts (backups, log rotation), access management (onboarding/offboarding, MFA, reset) and technical documentation.
• Juran · quality. Audits output correctness (automated QA, complaints Pareto, 5-whys, light ISO 9001 audit). Works in tandem with Deming.

• Porter · strategy. Five forces analysis, competitive mapping, positioning recommendations and market tracking.
• Brunel · engineering. Drafts of technical specs (RFCs, ADRs), effort estimates and architecture review (C4).
• Moore · product. Collects feedback (Intercom, Canny), prioritizes (RICE/ICE/MoSCoW), maintains the roadmap and coordinates launches with Kotler and Bernays.
• Bernays · communication. Press releases, communication plan for milestones and crises, media relations. Human approval always required for official external communications.
• Schneier · cybersecurity (included in Max at no extra cost). Virtual CISO: password policies, OWASP Top 10, STRIDE threat modelling, incident runbooks and CVE searches against your stack. Doesn’t replace a pentester or generate exploits.

Hired at €99/month + 15M STU each, on any plan from Max up. They expand the team with more specialized areas:

• Barnum · events. Action plan, communications to attendees, logistics (venues, catering, AV, speakers) and post-event follow-up.
• Curie · R&D. Technology watch (papers, patents), A/B experiment design, technical summaries and support for grant applications (CDTI, ENISA, NEOTEC).
• Shannon · technical support. Internal and external helpdesk, up-to-date knowledge base, triage, escalation to a human and reports on recurring tickets.
• Tracy · projects / PMO. Structures projects into milestones and tasks, assigns owners and deadlines, reminders and early delay detection. Integrates with Notion, ClickUp, Asana, Linear and Jira.
• Ohno · procurement. Supplier catalog with SLAs, budget comparison, orders with stock thresholds and spending audits.

Imagine you write to Amadeus: “Prepare this month’s sales summary and notify clients with proposals pending signature.” Here’s what happens underneath:

1. Amadeus breaks down the request: there’s a pipeline analysis part (sales) and a client communication part (sales + customer service).
2. It delegates the summary to Carnegie (sales), who reads your CRM and reports the status of the proposals.
3. It hands the notifications to Carnegie and Carlzon (customer service), who draft the emails in your corporate tone.
4. The emails aren’t sent: they land as proposals in your approval inbox for your sign-off.
5. Amadeus consolidates everything into a single response and delivers it to you along with the actions pending approval. The whole chain is logged in the audit log.

You gave one order; Amadeus moved three agents, respected your tone and left the sensitive actions waiting for your approval. That’s Shara’s work pattern for any request.

Agents read your tools with total freedom, but any action with a real effect (sending an email, issuing an invoice, publishing a post, placing an order) is generated as a proposal and waits for your approval. It’s a design guarantee: no agent executes sensitive actions on its own, and whoever approves is always a person, never a bot. Read What Shara is for the full detail.

• Turing vs. Holmes vs. Schneier: Turing is the sysadmin (access, backups, systems), Holmes covers the legal-contractual side (contracts, clauses, regulation) and Schneier covers technical security (policies, OWASP, incidents).
• Deming vs. Juran: Deming optimizes the process (cycle time, lean, flow); Juran audits output correctness (QA, ISO 9001, complaints Pareto). They work in tandem.
• Kotler vs. Bernays: Kotler is marketing (content, campaigns, acquisition); Bernays is communication (press, reputation, crisis).
• Carnegie vs. Moore: Carnegie sells (leads, proposals, closing); Moore does product (feedback, roadmap, prioritization).

• Can I talk to a specific agent without going through Amadeus? If you’re an employee in a department, yes: you talk to the agent for your area. Coordination between agents is still handled by Amadeus.
• Do the agents talk to each other on their own? No. All coordination goes through Amadeus, with just enough context and without leaking data from one area to another.
• Can I deactivate an agent I don’t use? No need: you only consume STU when you use it. An inactive agent generates no cost.
• Can I change an agent’s name or tone? The name is fixed, but how it works and its tone are fully adjustable through its IDENTITY.md. Read Agent identity.
• Which model does each agent use? The platform decides by alias (Prelude, Sonata, Symphony, Concerto) based on complexity, time of day and quota. You never choose the model, and the real provider stays hidden.

Key catalog distinction: Turing is the sysadmin, Holmes covers the legal-contractual side and Schneier covers technical security. Continue with Agent identity to see how each one learns to sound like your company.