The AI brain behind Chilla.
Built to follow your choices and explain what happens.
M-II is the AI brain behind Chilla
and the technology that helps it run reliably.
It does not choose for you. It makes sure Chilla follows what you chose — clearly, safely, and with full transparency.
M-II turns your Chilla choices into a task it can run, checks the boundaries you set before anything happens, keeps your connected account secure, and reports activity through Flow.
These commitments keep Chilla clear, bounded, and under your control.
M-II helps Chilla run only the task a user approved. It stays within the chosen style, market, account, and boundaries.
Every potential action is checked against account compatibility, comfort, and safety boundaries first. Anything outside those boundaries is skipped.
All system activity generates human-readable output in the Flow interface. Users can see exactly what happened, what was skipped, and why — in plain language, in real time.
Chilla runs only on the connected account the user selected. Funds stay in the user's own trading account.
M-II is the technology that lets Chilla run multiple styles and tasks reliably, keep them separate, and explain activity clearly through Flow.
M-II turns Chilla choices into tasks it can run, checks boundaries before action, monitors activity, and sends clear updates to Flow.
Sign-in, consent, capacity, account connections, and plan access all rely on M-II so Chilla can keep each user's tasks clear and separate.
M-II is designed so future Beaverly products can use the same clear, bounded approach without changing what Chilla users control today.
Every function M-II performs is designed around the same principle: automate only what is authorized, and never skip the checks.
M-II manages the complete path of a user task — from draft review and activation to updates, multiple active tasks, and stopping a task.
Before any task becomes active, the system checks user authorization, consent, account compatibility, and plan eligibility. Only fully checked tasks are allowed to run.
Before any action is attempted, M-II runs a series of pre-automation checks: task status, account compatibility, plan and capacity eligibility, signal freshness, and duplicate protection.
Action size is determined by user comfort inputs, available account balance, optional monthly comfort caps, and account-specific minimum constraints. Actions that exceed defined boundaries are skipped safely — never forced.
M-II generates human-readable activity updates for every meaningful event: entries, exits, skipped actions, warnings, and monitoring updates. These appear in the Flow interface in real time and remain queryable historically.
Flow entries are bounded to the relevant user and task context. Users can filter by event type, review a specific time window, export activity logs, and expand individual events for full context.
M-II monitors platform health, maintains account connectivity, synchronizes account status, and enforces entitlements continuously. Automation eligibility is constrained or halted automatically when integrity conditions are not met.
The system maintains auditable records for task lifecycle, automation activity, comfort usage, capacity consumption, and operational status changes. Historical activity is reviewable by time window and event type.
These are not policy statements. They are architectural commitments reflected in how M-II was built — and what it is designed to never do.
Users configure, activate, pause, and stop their tasks at any time. M-II does not modify task scope on its own.
Funds remain with the user-selected trading account. M-II submits authorized actions to the connected account — it holds nothing directly.
Chilla activity is always bounded by the user-approved task. M-II does not infer, extend, or act beyond the defined scope.
Every meaningful system event produces a human-readable Flow entry. Nothing significant happens silently.
Safety checks are mandatory, not optional. Comfort boundaries, account constraints, and capacity limits are always enforced before action.
Most automation tools are reactive. M-II is built around authorization, validation, and accountability at every layer.
The future isn't platforms.
It's technology that knows what it's authorized to do,
checks before it acts,
and tells you exactly what happened.
Chilla is the user-facing layer built on M-II. Set up your tasks, connect your trading account, and let the technology handle the rest.