Collaboration and handoff

Epismo separates access, responsibility, and evidence. An ACL says who may read a case. An assignee says who is responsible now. Records say what has actually been shared. None of these silently implies another.

A reliable handoff

1. Read the current case, open tasks, and recent records.
2. Add the next user to the case editor grants if they cannot already edit.
3. Append the outcome, unresolved questions, evidence, and relevant references as records.
4. Create or assign a task when a specific piece of work or approval needs an owner.
5. Assign the overall case only when responsibility for the whole matter changes.

Assignment accepts users, not team principals, and requires existing edit access. The service rejects removing a current case or task assignee from the ACL until responsibility is changed.

For approval, append the candidate outcome first, then create an approval task whose subjectRecordId points to that exact record. This avoids ambiguity when several artifacts or revisions exist. Case evaluation is separate: any case editor can use epismo report case generate <case-id> (POST /v1/cases/{caseId}/report) to queue an asynchronous AI evaluation of the case's evidence and records, charging token-based credits to the case's current owning account.

Resume instead of replay

A new agent should read the case and its records, not reconstruct the previous runtime session. Preserve source links, inputs, conclusions, uncertainty, decisions, and next actions. Keep ephemeral scratch work, hidden reasoning, retries, and tool chatter in the runtime that produced them.

When a recurring problem is discovered, keep the one-time observation in a record and open a suggestion against the relevant immutable version. Playbook editors can publish a new version and resolve the suggestion as applied, or mark it declined. The author can withdraw their own proposal as archived while retaining parent access. Resolution never publishes a version automatically.