- BIAS
- LOGIC
- HUMAN
- FIX
Short answer
Can my AI check if my technical docs are actually clear?
Yes. Your AI uses the Hawking Boundary Prover to scan documentation for optimistic bias and logical gaps. You'll get a breakdown of where workflows break down or assume too much knowledge from the reader.
Where every issue lands.
Audit outcomes
The AI categorizes every finding into specific buckets for your review.
BIAS
Optimistic bias detected
The AI flags spots where the text assumes the user knows something they shouldn't. You get specific locations where the tone is too confident.
LOGIC
Broken workflow steps
The AI identifies missing links in a sequence. It highlights where a step is described but the prerequisite isn't met.
HUMAN
Human comprehension gaps
This is where the AI tells you a human will likely get stuck. You receive warnings about overly dense or vague instructions.
FIX
Actionable corrections
The AI suggests how to rephrase or add detail to close the gaps. You get a list of specific edits to improve clarity.
The workflow
What your AI does when the documentation arrives.
The AI acts as a skeptical reader to find the friction points in your text.
Scan for assumptions
The AI reads the text to find where the writer assumes the user has certain skills or tools ready.
validate_hawking_boundaryIdentify logical leaps
It looks for jumps in logic where a step follows another without a clear transition or necessary setup.
validate_hawking_boundaryTest human readability
The agent simulates a first-time user to see where the instructions become confusing or too dense.
validate_hawking_boundaryFlag optimistic tone
The AI catches language that glosses over complex or difficult parts of a process.
validate_hawking_boundary
Try it
Copy these to start.
Use these prompts to kick off an audit.
Starting points
Swap the bracketed text for your actual file names or repository paths.
Hawking Boundary Prover Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_yMN6urkUYACm1x77B80uVAhuEDOIE9U6QYD0dyI8/mcpClaude Desktop
Follow the steps below to connect in seconds.
- 1In Claude Desktop, open Settings → Connectors.
- 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
- 3Click Add and start a new chat — Hawking Boundary Prover capabilities are ready to use.
{
"mcpServers": {
"hawking-boundary-prover-mcp": {
"url": "https://edge.vinkius.com/vk_preview_yMN6urkUYACm1x77B80uVAhuEDOIE9U6QYD0dyI8/mcp"
}
}
}Audit the documentation in my /docs folder for optimistic bias.
Check the workflow in setup_guide.md to see if a new user can follow it.
Scan the API reference in my GitHub repo for logical gaps in the sequence.
Review the troubleshooting guide in this Notion page for clarity issues.
Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline
Start here
Connect Hawking Boundary Prover once, then ask.
Just link the MCP to your client. Your credentials stay encrypted, and you can start auditing immediately.
Connect Hawking Boundary Prover to your AIFAQ
How the audit works
- 01
Can the AI rewrite my documentation for me?
No. The AI identifies the problems and suggests improvements, but you must perform the actual edits.
- 02
Does the AI change my original files?
No. The AI only reads your files to provide feedback. It cannot write to or modify your documentation directly.
- 03
How does it find 'optimistic bias'?
It looks for language that implies a task is easier or more straightforward than the logical steps actually allow.
- 04
Can I use this with my local files?
Yes, as long as your AI client has access to those files and the Hawking Boundary Prover is connected.
- 05
Will it flag every single typo?
No. This tool focuses on logical flow and comprehension, not basic spelling or grammar checks.
More questions about Hawking Boundary Prover? The Connector page answers them. See everything the Hawking Boundary Prover Connector can do
Connect Hawking Boundary Prover to Claude, Cursor, ChatGPT & more
