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.
设定目标，从 Obsidian、Drive、Notion、Confluence 或你提供的文档中选择知识。
财务使用账单邮箱，销售使用销售账户。为每位高管选择可访问的工具和资源。
安排定期审查，或通过同事请求及已配置的应用事件唤醒角色。正在执行时，新请求会排队。
Fictional example. A line under the confidence floor stays empty for you, never a guess.
EXCOM 提供什么、你需要准备什么，以及哪些事项由你掌控。
聊天通常等待你的下一条提示。EXCOM 为每个角色提供连续对话、指定来源、工具，以及定时或事件驱动的工作。高管可以互相求助，并将行动建议汇集在同一处。
可以，需要已连接且兼容的 Melaya runner 以及受支持的模型配置。你提供服务商账户或本地算力。Runner 必须保持可用，相关高管才能工作。
只有在你明确分配时才会。每位高管都有具体的账户和资源权限。如果连接器支持，可以分配多个账户。
不会。高管协调持续职责，pipeline 执行可重复工作流。托管 pipeline 仍遵守现有平台限额和审批控制。
EXCOM 目前仅限预览。我们正准备更广泛的访问：Sandbox 观察、Forge 内部草稿、Bastion 受控自主行动。目前购买套餐不会解除预览访问限制。
mailchimp · campaign report
github · read pull requests
