No, not by default. Slack posts, Jira updates, Linear writes, and outgoing email are HITL-gated for this crew. The agent prepares the action and waits for one-click approval. You can lift the gate per template once you trust the run.

Three ways. Static context attaches your runbook, SLA matrix, and on-call rota to specific personas on every run. The rag_retrieve tool lets ReportingAnalyst and ComplianceOperations pull from data dictionaries and policy docs on demand. Cross-run memory carries yesterday's open incidents into today's stand-up so nothing resets at midnight.

It is closer to a Zapier alternative for the reasoning steps, and an n8n alternative for the schedule and webhook plumbing. Where Zapier and Make.com chain fixed actions, Melaya runs reasoning agents between the steps so an incident can be triaged, not just routed.

Every report cites the SQL query, the row count, the freshness timestamp, and the data quality flag. ReportingAnalyst is required to attach the source query and the staleness check before any output ships. The COO reads numbers and provenance, not adjectives.

Any. Claude on OperationsSynth where multi-source reasoning earns the cost, GPT on ExecutiveAssistant drafting, a local Ollama on TradingOperations when balance data must not leave your network. Each persona picks its own model.

With Slack, Jira, and a database DSN connected, the morning health-check pipeline is a 4-node canvas: trigger on cron, check API matrix, build status table, post to Slack. Most teams ship it in a working session and have the first brief in channel the next morning.

IncidentManager classifies every anomaly as SEV1, SEV2, or SEV3 using the rules in your Static context. SEV1 routes to Telegram and Slack with the on-call owner tagged. SEV3 sits in the daily digest. The audit log captures the classification, escalation, and resolution timestamps.

Every run logs every tool call, every model invocation, every approval decision, and every retry. Replay any run at any time. The audit trail covers the data source, the query, the freshness check, and the human approver, so compliance ops can reconstruct any morning brief.

Yes. Tools are scoped per agent in the canvas. You can give DataOperations read-only http_request and sql_query, while only IncidentManager carries jira_create_issue and linear_create_issue. Scopes are enforced before the model even sees the tool.

Native connectors for Slack, Telegram, Discord, Gmail, Google Calendar, Jira, Linear, Postgres, SQLite, Excel, Word, and PowerPoint. The melaya_exec bundle reads live positions and balances from the same exchange keys your trading desk already uses.