Developers: continue a teammate’s fix
Ana discovers why invoice retries need an idempotency key while working in Codex. She captures the project session, reviews the proposed decision and links the Git evidence. Ben starts the next session in Claude Code and requests the project’s current decision and open work.
Shared: the reviewed retry decision, rationale, relevant repository revision, authorized Resources and remaining Work. Separate: Ana’s full transcript page and marked-private turns. Authorized project agents can search the non-private turns from the linked conversation. Ben’s project access and token scope still apply.
Check conversation capture and visibilitySysops: hand over an incident
Rui uploads the deployment runbook as a Markdown Resource, records the observed disk problem and submits a rollback decision for review. Marta takes the next shift, checks the current runbook revision, approved action and unresolved blocker before doing any infrastructure work.
Shared: the permitted runbook, reviewed incident knowledge, source references and open Work. Protected: credentials remain in Secrets; a visible capability label is not the password. An exact connector operation requires its own supported approval. ReasonTrail does not make an arbitrary SSH command safe or automatically execute the runbook.
Upload and version a runbookDeveloper + ops: agree on a release
The developer records a migration prerequisite; ops records a backup check and a release blocker. A reviewer resolves the decision in Needs Attention. The next authorized member reads the accepted decision in Memory, verifies current Git evidence and follows the authoritative Work item.
Shared: project-approved constraints, evidence and the current work state. Not implied: access to another private project, another organization’s records or a contributor’s entire chat history. Using the same SSO tenant does not grant those permissions.
Review members and team boundariesThese are illustrative workflows, not customer testimonials or measured savings. Start with one project, one runbook or decision, and a second authorized member who verifies retrieval.
Navigation and feature guidance reviewed 17 November 2026. Report a documentation issue.