Picture a small board of department heads who check the business every day and never act alone. Each one owns a part of your company and tells you what needs a decision.
An executive is not a chatbot you have to prompt. It has a role, goals, the accounts you let it read, its own memory and a daily review. It works on a schedule, reacts to events from your apps and asks its colleagues for help.
A title is a role, not a legal authority. An AI CFO cannot sign anything, and an AI CHRO never hires or dismisses anyone.
CEODirectionTurns the team's findings into the three decisions you must take this week.
CFOFinanceExplains cash, runway, collections and cost variances from your books.
CMOMarketingRelates channel spend to qualified pipeline and keeps your positioning distinct.
CTOEngineeringTracks delivery and reliability, diagnoses failed runs and proposes bounded repairs.
COOOperationsFinds stalled handoffs and duplicated work, then proposes the workflow that removes them.
CROSalesMoves qualified opportunities forward and keeps the pipeline honest.
Also on call: CPO, CXO, CHRO, CISO, CLO, CDO, CSCO and CQO. A role that sleeps costs nothing.
Every piece of work follows the same path, left to right. Reading is free to happen. Anything that leaves stops at the gate.
Obsidian vault, Notion, Google Drive, Confluence and your website, plus mail, books and CRM through your own connections.
Each one reads with its charter, its own memory and the team's shared knowledge, and cites every passage it uses.
A daily brief, tasks with evidence, drafts and questions to colleagues. None of this needs a card.
Anything that sends, changes or spends stops here as a card in the app, by email, on Telegram or on WhatsApp.
Telegram
WhatsAppThe exact call you approved runs, after grants, budget and the account are checked again.
Every call leaves a receipt. Approve the same thing three times and the executive proposes a precise rule.
Two routines straight from the role templates. The names and numbers below are fictional.
Every plan runs the whole team end to end. The plan sets how far the executives may go. Inside that ceiling you still choose Observe, Prepare or Run within rules.
EXCOM is in limited preview. These ceilings apply as access opens. Your plan's pipeline limits stay as they are. Compare plans and prices
| Plans | Sandbox and Outpost | Forge | Bastion and Citadel |
|---|---|---|---|
| Read assigned sources and accounts | Yes | Yes | Yes |
| Daily brief, tasks with evidence, questions to colleagues | Yes | Yes | Yes |
| Draft messages and documents | No | Inside Melaya | Yes |
| Send, post or change a record | No | No | Your approval or a rule you accepted |
| Spend, delete, deploy, legal and people matters | No | No | Always asks you |
| Run scheduled pipelines | Proposed as a task | Proposed as a task | After a trial and two approvals |
| Change its own permissions | Never | Never | Never |
Yes. EXCOM is the operating layer, not a model subscription. Each executive uses the model you pick: a cloud key, a router, or a CLI agent on your own machine through the Melaya runner.
With Claude Code, Codex or GitHub Copilot behind the runner, your executives think on the subscription you already pay for. The Melaya server still decides every tool call, so a runner model meets exactly the same approval gate as a cloud one. If the runner cannot get an answer, it runs nothing.
GitHub Copilot
Ollama
LM Studio
OpenRouterKeep the runner up to date. An older runner keeps its executives in Observe.
Safety here is not a prompt. It is a check that runs on every tool call, before anything happens.
Setup grants read access only, and every executive's first pass is read-only, whatever autonomy you chose.
Each account is read, draft or write, per executive. A read account never writes, even in Run within rules.
Payments, deletions, deploys, legal and people matters ask you every time. No rule can cover them.
Executives have no tool to widen their own grants, budget, rules, schedule or approvers.
Each executive reads only what it was granted. A colleague answers with its own access and never lends it.
Checked before every call: pause, grants, account, caps, rules, autonomy.
Six short steps in one window, about two minutes. The wizard saves after every step, so you can leave and come back.
Defina objetivos e escolha conhecimento do Obsidian, Drive, Notion, Confluence ou dseus documentos.
A caixa de faturamento para Finanças e a conta comercial para Vendas. Escolha as ferramentas e os recursos acessíveis a cada função.
Agende revisões ou ative uma função com um pedido de um colega ou evento configurado. Novos pedidos ficam em fila se já estiver trabalhando.
Fictional example. A line under the confidence floor stays empty for you, never a guess.
O que o EXCOM acrescenta, o que fornece e o que controla.
Um chat normalmente espera pelsua próxima mensagem. O EXCOM dá a cada função uma conversa contínua, fontes, ferramentas e trabalho agendado ou por eventos. Os executivos podem pedir ajuda entre si e reunir propostas em um só lugar.
Sim, através de um runner Melaya conectado e compatível e de uma configuração suportada. Fornece a conta do fornecedor ou o processamento local. O runner deve estar disponível para os executivos trabalharem.
Só se a atribuir. Cada executivo tem permissões explícitas por conta e recurso. É possível atribuir várias contas quando o conector o permite.
Não. Os executivos coordenam responsabilidades contínuas; os pipelines executam processos repetíveis. Os pipelines geridos mantêm os limites e controles de aprovação da plataforma.
O EXCOM está em prévia limitada. Estamos preparando um acesso mais amplo com observação no Sandbox, rascunhos internos no Forge e autonomia controlada no Bastion. Comprar um plano não remove atualmente a restrição de acesso.
Descubra como os executivos IA persistentes trabalham com seus modelos, contas e conhecimento empresarial.
Prévia limitada · Os seus modelos · As suas permissões
mailchimp · campaign report
github · read pull requests
