the assistant
Build and modify packs, analyse live data, produce reports — and perform the work itself: "approve REQ-311" does what the button would, under the same roles, gates and audit.
"How many tickets breached SLA this week?" — counted from the records themselves, with the trend and the worst cluster called out and the chart saved to a dashboard. Not a report somebody exported last week; the same data your queues read.
"Approve REQ-311", "escalate everything older than 48h", "assign TKT-0019 to Meera" — real workflow moves executed with your authority, every one stamped on the audit trail. Instead of opening the form and hunting for the button, say it.
Roles and gates still apply — if a lead must sign off, the assistant knows before it tries. A chat command is a workflow move, not a back door.
PROPOSED · weaving.pack draft
"Build a visitor-management pack" or "add a rework stage before Dispatch" — proposals arrive as drafts you review line by line, declared against the real capability catalogue rather than approximated.
You publish; it never does. Approving a proposal only saves your draft — the publishing key stays human.
Inside Brrelo it's the ✦ panel beside the work. The same brain is exposed as an MCP server, so the app you already run can answer "how many open tickets?" or file one — your users never leave your product.
Every embedded action still passes through auth, roles and gates — it's the same engine, just wearing your UI.
ASSISTANT USAGE · THIS MONTH
Every plan includes a monthly token allowance sized for typical use. Beyond it, top up at $25 per 1M tokens — top-ups never expire, and the meter sits right in the panel, so usage is never a surprise line on the invoice.
See plans →No. Proposals land as drafts; approving one only saves your draft. A person publishes — always.
Yes — commands execute with your authority and your name on the audit trail. Whatever your role can do, it can do for you; nothing more.
It exposes the same assistant to your own application — your users chat in your product, and Brrelo answers or acts, with auth, roles and gates intact.
By tokens — a monthly allowance per plan (1M–8M), top-ups at $25 per 1M. See pricing.
