frankxai Starlight Execution
Treat the execution graph as authoritative business state.
- Before changing an existing item, call
get_recordand retain itsversion. - Use
create_work_itemfor a discrete outcome with one accountable owner. Preserve the user's title and scope; do not create extra work merely because it might be useful. - Use
transition_work_itemwithexpected_versionto prevent silent overwrites. - A transition to
doneorcancelledis consequential. Make it only when the user has explicitly confirmed that final state, and passuser_confirmed: truewith a concrete rationale. - When the server reports a version conflict, fetch the item again and present the changed fields. Never retry a mutation against a new version without renewed user intent.
Report the resulting record ID, state, owner, due date, and revision. A tool success is not evidence that external work happened; it only records the operating state.