Skip to main content
Version: Current

Current limits

What the current version cannot do, what to do in the meantime, and where the target version solves it.

missingconsequence todayin the meantimein the target
A playbook's conditions on dataa task's or a method's when reads only the chosen kinds ($selection.kinds): not a room fact, nor a total, nor what a task read; and the model does not pick a method (choose: clm)one kind per case (pickup, delivery), read by when; a guard on the skill (require, check) for a condition on dataPlaybooks: when on $read or $result, and choose: clm
Playbook activationnothing opens a journey in the agent's place: it opens it if it wants to, on its goalauto_trigger on the entry skillActivation: seek_guidance and three levels
One identity per personone API key per station: everyone is the same user for the tenantkeep sensitive writes for a single-user stationIdentity
Several calls in one submita submit has one call per skill or per kind; a list of two is refused at loadtwo skills, each with its call, each the task of a playbook, the second reading the first through $submitted[<task>.<call>]Skills: several calls in order, cited by task, $submitted[task.call]
Who submitsalways a human, always the person in the room—submitted_by, in The submit
An approval before the choicethe submit confirmation serves as approval—the approval guard, in Guards
Reads in the selectiona read leaves no trace; the person who submits does not see what the action is based on—read traces, in Concepts
Where an argument comes fromthe station fixes an argument through invoke.args, to a literal or to a parameter (params) whose value is its default; the model fills the other invoke parameters. A playbook task binds a parameter read at submit to what another task filed ($submitted[…]), not to what a task read ($read[…]) nor to a sub-playbook's result ($result[…]); neither the model nor set_by sets a parameterhave the tenant compute amounts (update: {price: …} guard, invoke)set_by, and a task's params bound to $read or $result, in Budget: data & time
Data going outdata that was read can go back out in a writedo not list an operation that reads confidential datadata classes and audiences
Automationsnothing starts on an event from a tool—Automations
"Smart" rulesno fraud or injection detection by Coreinstructions in agent.rules (not guaranteed)smart policies, which can only tighten
Long journeysa journey lasts as long as one conversation—the run belongs to the room
Station versionsa modified config applies immediatelytest locally before publishingstaging, production, contract tests

The decisions behind these points: ADR-028 §6, ADR-029, ADR-030, in convoy/docs/adr/.