A ceremonial diagnostic engine for colonial correspondence
Paste an email, grant call, HR letter, policy paper, committee minutes, or any colonial correspondence into Claude, and the Debugger returns a full structural diagnostic plus two ready-to-adapt response options.
The tool does not produce neutral summaries. It analyzes from a position of Indigenous sovereignty and relational ethics. It names what the correspondence is actually doing, not just what it says.
1Copy the Debugger prompt to your clipboard.
Open claude.ai in a new tab →2Paste the prompt into a new Claude conversation and send it. Claude will confirm the Debugger is active.
3Paste your correspondence into the same conversation. The Debugger returns a full diagnostic plus two response drafts you can adapt and send.
[⊙] ENTITY SCAN Source: [sender, organization] Node Classification: ACADEMIC INSTITUTION NODE Tone Protocol: Technical + trickster [⊙] PARSING CORRESPONDENCE... ▓ Surface Request: What they literally asked for ▓ Actual Request: What they actually want ▓ Power Dynamic: Who benefits, who carries the cost [⊙] TRIGGER TERM SCAN ⚑ "amplify your voice" → platform_without_power.exe signature ⚑ "exciting opportunity" → flattery_vector deployment [...] [⚠] DOCTRINE CORE THREAT LEVEL ☐ MODERATE — Manifest Manners running, soft extraction likely [ ▓ INITIATING RESPONSE PROTOCOL ] RESPONSE A — Ceremonial Reframe RESPONSE B — Sovereign Decline
A free account at claude.ai is enough to run the Debugger. Sign up, then come back to step 1.
The Debugger returns two draft responses framed in neutral institutional voice — clear, direct, sovereign-grounded, without affective performance. They are starting points. You are the final author of any response. Edit freely, change register, adjust to your relationship with the sender. The diagnostic anonymizes sender names by default. Anonymizing the output does not remove identifying details from the correspondence you already pasted into Claude.