Cases

Use epismo_case_start when an outcome must be shared or resumed. Start from a Playbook Version or create an ad hoc Case with a title.

epismo_case_get returns the Case, current Tasks, Records from it and its ancestors, the direct handoff neighborhood, and the source Playbook and pinned Version when they are still readable, in one 1-credit read.

• Keep local intermediate work in the agent runtime.
• Append outcomes, decisions, and handoff summaries with epismo_case_record_append.
• Create Tasks with epismo_case_task_create only for explicit responsibility or review.
• Connect related workflows using epismo_case_handoff_create, and inspect the DAG with epismo_case_handoff_graph.
• Query eligible next or previous Cases with epismo_case_handoff_candidate_list (direction=outgoing or direction=incoming) to avoid loops and duplicate links.
• Generate a fresh idempotency key for each new mutation.
• Read the latest lock version before changing a Case or Task.

After a conflict, re-read the object and decide whether the intent remains valid. Never replay a stale request by changing only its lock version.

Do not invent an agent assignee. When a User assignment is needed, select an ID from the users resource and ensure that User is already in the Case ACL.

Use epismo_case_record_list with the Case ID to resume from that Case's timeline. Pass scope (self, ancestors, descendants, neighbors, connected) to include Records across connected handoffs while respecting individual Case ACLs. Filters only narrow that timeline; an ACL filter is not authorization.