IIAgents
An agent is a task someone runs by hand today, written down once: what it reads, when it runs, who owns it. By the time your team arrives, the result and the exceptions are waiting.
Acts vs e-invoices
What it read, what it prepared and who approved it, beside the definition of what it may touch.
Each agent has a name a colleague would recognise, a schedule, and an owner whose identity it runs under. The log names the owner, and the failure card reaches them.
A trigger, a read scope, a write scope, an approval rule and an owner. If any of the five is missing, the agent does not exist yet.
Finance matches acts to e-invoices, sales flags deals with no next step, HR sees who has waited longest. Each agent reaches only what its department already may.
Every act of completed work matched to its invoice, and the ones without a match listed for a person.
Deals with no next step, no date or no owner, surfaced the day before the pipeline review.
Who applied, who moved stage, who has waited longest for an answer. Read from the register, written nowhere.
The one agent that reads across departments, and the one where the permission check matters most. Each reader sees the total only over what they may see.
The agent prepares the change and shows it in Telegram. The owner approves, and only then does it land. A write outside the declared scope is refused.
Read scope is a subset of the owner's permissions. Write scope is narrower again, usually one place, named exactly.
The runtime refuses it before the connector sees it. The read half completes, the write is dropped, and the owner gets a card saying which one.
The agent prepares the change and shows it. The owner approves it where they already are, and only then does it land. An unapproved change expires.
An agent sees exactly what its owner sees. When the owner leaves, access revoked at the source stops the agent too.
What the owner may open, the agent may read. What the owner cannot open does not exist for the agent, and no setting widens that.
Access revoked at the source is access revoked here. A run with no principal behind it does not start, and the agent waits for a new owner.
A source times out, a record is malformed. The run retries a set number of times, stops whole, and sends the owner the step and the reason.
A failed step is retried a set number of times with a pause between. After that the run is marked failed and the owner gets a card with the step and the reason.
A change is applied whole or not at all. If the third of three rows fails, the first two are rolled back and the run reports zero written.
An agent acts through the same connectors that feed the index, and writes only where a connector has a write path.
Sales, acts, counterparties and the item catalogue read over OData. A change to a 1C document is prepared here and applied through the connector after approval.
Sheets are the usual write target: one sheet, one tab, named in the scope. Drive and Gmail are read, and a prepared email waits as a draft for a person to send.
Deals, contacts and tasks read over REST. A stage change or a comment on a deal is a write inside scope, applied after the owner approves it.
What it read, what it wrote, as whom, and what it refused. One log for people and agents answers who touched what.
Start, end, records read, rows written, the owner it ran as and the refusals along the way. Nothing happens off the record.
One table, one identity model, one filter. A question about a document answers across people and agents alike.
An agent's model calls leave through the same gateway as a person's questions: your key, zero retention, no training, and spend counted against its name.
The terms an agent runs under are the terms the gateway enforces, on every call, whoever made it. There is no second path for an unattended run.
Every call an agent makes is counted against its name and its owner. The cost of a process is a number beside its schedule, never a surprise on the invoice.
We build the first agent on your systems, under your permissions, and your people approve every write. Name the task somebody runs by hand every week.
