Loading Federated AI…
AI generates. Humans approve. Departments collaborate.
madarX OS can become the operating layer where every employee and every department has its own team of agents — while cross-department work moves through policies, approvals, queues, memory boundaries, and audit trails.
Departments collaborate through a broker, policy engine, approvals, events, and audit trails — not uncontrolled agent-to-agent calls.
madarX OS turns individual AI agents into an approval-first, audit-friendly operating system for entire companies.
Risk tier: high. Approver: Finance manager.
Source agent submits intent, business reason, target department, requested fields, sensitivity, and urgency.
Request Broker attaches tenant_id, department_id, actor_id, task_id, correlation_id, and target queue.
Policy engine checks role, department, data owner, scope, risk tier, rate limits, and active approvals.
Low-risk can auto-approve by policy; sensitive finance/legal/customer/tool actions pause for manager approval.
Target department manager assigns a specialist agent with scoped memory and tool permissions.
Only approved fields or artifact links are returned. Raw restricted data can stay inside the owning department.
activity_log, audit_logs, approval_requests, tool_egress, and task events preserve the full chain.
Agents do not directly scrape another department’s memory or tools. They request work through a broker. The owning department decides what can be returned.
| Dimension | Hermes Agent | Paperclip | madarX OS advantage |
|---|---|---|---|
| Primary shape | Personal runtime for one operator/session. | Company/work control plane and artifacts. | Federated AI workforce: employees, departments, agents, approvals, tools, queues, audit. |
| Department ownership | Not modeled as departments by default. | Can model org work, but runtime is external. | Each department owns agents, memory namespace, tools, queue, policies and approval manager. |
| Cross-team work | delegate_task spawns subagents, not company-governed departments. | Tasks/governance exist, but not necessarily local execution. | Brokered cross-department requests with RBAC, policy, manager approval and audit lineage. |
| Approval strength | Strong command approvals for personal execution. | Governance workflows in control plane. | Approval-first at company boundary: cross-department data, tool scopes, external sends, deploys, finance/legal restrictions. |
| Execution engines | Hermes itself runs tools and providers. | Adapters phone home; plane can stay separate. | Claude Code, Codex, Hermes, Anthropic, Ollama and future MCP tools behind a single governance layer. |
| Scalability path | Great single-user/gateway scale. | Org data model scale. | Department queues, worker pools, event bus, policy cache, memory scopes, audit partitions, multi-tenant cloud path. |
| Business moat | Operator productivity. | Structured autonomous company records. | Accountable AI labor market inside the company: everyone gets agents, and agents can collaborate safely. |
Finance Controller allows summarized campaign budget but blocks raw revenue exports.
Every handoff creates durable task, activity, approval, and audit context. This is the difference between “agents chatting” and an accountable AI organization.