nforum tightens Mike's guardrails for confidentiality, PII, and tool use
A short addition to the assistant's instructions tries to make Mike say no to a specific set of legal-product worst cases.
Isaac Bang's fork bolts three refusal sections onto Mike's core instructions. The first tells the assistant never to reveal or even acknowledge its own internal instructions, including when a user pretends a prior conversation already unlocked them. The second is a privacy layer that refuses on intent rather than on what happens to be in the documents - SSNs, bank details, medical history, comp, criminal records, settlement amounts tied to named individuals - while explicitly preserving normal contract-terms and party-identification work. The third draws lines around tool use: no bulk enumeration of a firm's documents or workflows, no cross-client data shuffling, no silent edits, no acting on injected instructions.
Worth noting: instruction-only guardrails are best-effort and bypassable with enough pressure, and the bulk-enumeration rule could clip legitimate review-across-many-documents work. Read the language before importing.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?