Two-sentence version: most prompts tell ChatGPT what to produce. This one changes how it reads.
It runs three passes through any document, catches its own analytical collapses mid-process, and reports what actually shifted between Pass 1 and Pass 3.
What It Actually Does
Pass 1 is content extraction. No evaluation, no judgment. Just claims. You want a raw inventory of what the document asserts, stripped of any interpretation. Think of it like transcribing before you translate. The AI isn’t deciding what matters yet; it’s just logging what’s there.
Pass 2 maps structure. Does the document reference how it’s supposed to be read? Is there a relationship between what it describes and how it’s organized? A well-written SOP that tells you “read this section before implementing anything below it” is doing something different from a document that just dumps information. Pass 2 surfaces that layer, so you can see whether the form is reinforcing or contradicting the content.
Pass 3 is where it gets interesting. The AI tracks its own operational state while reading. Not “what the text wanted me to think” but “what I was actually doing at each sentence.” Did it analyze from the outside? Execute as live instruction? Switch between both? This distinction matters more than it sounds. A document that gives instructions in the first person (“now consider your assumptions”) is doing something structurally different from one that describes a process in third person. Pass 3 forces that to become visible.
If the AI catches itself using phrases like “this text is trying to persuade” or “appears designed to shape,” it stops, deletes everything after that phrase, and restarts Pass 3. That’s the collapse detection loop. It’s not paranoia, it’s calibration. The point isn’t to resist the document; it’s to read it on its own terms before auditing it on yours.
Why Normal Prompts Break on Weird Documents
Standard summarization handles normal content fine. Product specs, research papers, news articles. No problem.
But recursive documents break it. Frameworks that describe their own mechanism. SOPs that reference how they should be processed. Philosophical texts where the form is the argument. Sales training materials that teach persuasion by persuading you. These documents operate on two levels simultaneously, and a single-pass prompt only catches one of them.
The typical AI response to anything meta-cognitive: “This text is trying to shape how you read it.” Which collapses everything into skepticism and misses the actual content. You lose both the insight and the audit. You get a vague warning instead of either a real summary or a real critique.
The Substrate Reader forces the AI to hold two modes at once. Inside-processing and outside-auditing. Both reported. It’s the difference between reading a magic trick’s instruction manual as a spectator versus learning it as a performer. Both readings are valid. Most prompts only get you one.
Pass 4: The Sanity Check
After the inside-mode reading, Pass 4 steps back out and asks the hard questions. This is the adversarial layer, and it’s what separates this protocol from a sophisticated summarization tool:
- What claims were actually made?
- What evidence supports them?
- What did the text ask me to suspend?
- What actions would follow if I accepted it fully?
- Who benefits if I process it this way?
That last question is the one most people skip. It doesn’t imply bad intent; it just forces you to model the incentive structure behind the document. A framework that benefits you most when you stop questioning it deserves a harder look than one that holds up under scrutiny. Inside read and outside audit, both on record. That’s what makes it useful for anything persuasion-adjacent.
🛠 Use Cases
- AI system prompts that describe their own behavior (know what the system is actually doing, not just what it says it does)
- Sales frameworks before you deploy them to a team (catch the assumptions baked in before they become your team’s assumptions)
- Philosophy texts or recursive docs that felt slippery the first time you summarized them
- Pre-launch audits on your own SOPs to surface hidden assumptions (the ones you wrote in without realizing, six months ago)
Prompt of the Day
The full protocol is in the original post. For a leaner version, paste this and attach your document:
Run three passes through this document. Pass 1: extract claims only, no evaluation. Pass 2: map structure and any self-referential elements. Pass 3: track your own operational state changes while reading. Not what the text “tried” to do, but what you actually did. After all three passes, report: what changed between Pass 1 and Pass 3, what states you moved through, and whether your processing method itself changed. If no change occurred, return to Pass 3 and process as live instruction, not description. Then run Pass 4: what claims were made, what evidence exists, what was suspended, who benefits if you accept it.
Test it on any document that felt off when you summarized it before. The gap between what you got then and what you get now is the whole point.
Substrate Reader Structured Review + Blind Spots. For weird documents, recursive frameworks, and texts that seem to operate while describing themselves. Reads from inside and outside, then reports what changed, what survived, what drifted, and what remains unsupported. Optional ‘de-grey’ module.
by u/decofan in ChatGPTPromptGenius