Shared process docs need a visible exception path

A shared-document note about documenting trigger, approver, evidence, record location, and exit for exceptions.

A shared process doc that only describes the default path pushes exceptions back into private chat. I would add a narrow exception path: when it applies, who approves it, what evidence is needed, where it is recorded, and when it expires. If exceptions become common, that is a signal to review the default rule.