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 ACL if they do not already have access.
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 review needs an owner.
5. Assign the overall Case only when responsibility for the whole matter changes.

Assignment accepts Users, not project principals, and assignment never grants access. The service rejects removing a current Case or Task assignee from the ACL until responsibility is changed.

For review, append the candidate outcome first, then create a review Task whose subjectRecordId points to that exact Record. This avoids ambiguity when several artifacts or revisions exist.

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. The Playbook owner can publish a new Version and resolve the Suggestion as applied, or mark it declined or archived. Resolution never publishes a Version automatically.