Book 2 Process Protocol
Authorship Moved Upstream
Whetstone Protocol
context → constraint → surface → support → return
The stone is not given. The stone is made.
Whetstone Protocol is not a shortcut around authorship. It is authorship moved upstream: the human builds the support surface before the tool is allowed to sharpen the work.
▸ Open MaxCP
▸ ◉ Key Insight
The prompt is not the method. The prompt is what becomes possible after the author has built, tested, corrected, and compressed the stone.
▸ ⚡ Mantras
- The stone is not given. The stone is made.
- I do not sharpen my blade with your stone.
- Support may sharpen. It must not steal movement.
- A short prompt can carry a long field.
- No drift is not a wish. It is a return vector.
▸ ↺ Flowchart
Need support? → Build the field first.
Need fidelity? → Name the constraints.
Need voice? → Demonstrate the surface.
Need precision? → Make the maps fight.
Need output? → Ask for catalyst, not replacement.
Need authorship? → Return-test the movement.
▸ ⌘ Micro-Lexicon
- Blade — the live work being sharpened: article, argument, draft, decision, or movement.
- Stone — the authored support surface: context, constraints, examples, cadence, values, and refusal rules.
- Thread — one demonstrated example, correction, refusal, known-good line, or failure case.
- Constraint — a stable rule triangulated from multiple threads.
- Constraint Map — a working surface built from many constraints.
- Return Test — the final check: does the movement still belong to the author?
Entry
I do not avoid AI.
I do not worship it either.
AI is a tool.
A calculator is a tool. A spreadsheet is a tool. A drafting assistant is a tool. Desmos is a tool.
The question is not whether a tool was used.
The question is whether the person using it remains the author of the movement.
Can support enter the work without taking over the work?
Whetstone Protocol begins there.
Not with hype.
Not with panic.
Not with purity theatre.
With authorship.
The Claim
Whetstone Protocol is a method for receiving catalyzed support without surrendering movement.
It does this by moving authorship upstream.
Before the tool is asked to sharpen anything, the author makes the stone.
Context
The author gives the tool a field to answer to: purpose, audience, prior work, known-good examples, and working assumptions.
Constraint
The author names what support may touch, what it must not touch, and what would count as drift.
Cadence
The author demonstrates how movement sounds: rhythm, pressure, sentence shape, paragraph shape, landing style, and refusal patterns.
Return
The author decides what holds, what gets revised, what gets rejected, and whether the movement remains theirs.
I do not sharpen my blade with your stone. I use my own.
The Analogy
The word “whetstone” can mislead if the stone is treated as something already sitting on the table.
That is too shallow.
The protocol is not only the sharpening.
The protocol is the stone-crafting process.
Blade
The live work: a draft, article, page, argument, decision, or movement that needs sharpening.
Stone
The support surface: context, constraints, voice, values, examples, anti-patterns, and correction history.
Sharpening
The support pass: friction, deltas, options, compression, structure, polish, counter-read, or drift check.
Author
The person who built the stone, brought the blade, judged the support, and owns the final movement.
The tool may help sharpen the blade. The author makes the stone. That is why the movement can remain authored.
The Problem With Cold Support
When a person opens a tool cold, there is no authored field to draw from.
No voice surface.
No values surface.
No known-good examples.
No anti-patterns.
No cadence.
No history of accepted, rejected, or corrected moves.
So the tool improvises.
Sometimes the improvisation is useful.
Often it is generic.
Cold support tends to sound competent while inventing the room. That is not fidelity. That is beige confidence wearing a helpful hat.
Whetstone Protocol refuses to begin there.
It does not ask support to invent the room.
It builds the room first.
The Procedure
Whetstone Protocol is procedural. It is not a mood, a disclosure statement, or a better prompt template.
The procedure makes the surface before asking for support.
- Quarry the Material
- Grind the Surface
- Season the Stone
- Load the Job
- Sharpen With Constraint
- Refuse Substitution
- Return-Test the Movement
- Rehone the Stone
At first, the author may need to explain a lot. Later, the field compresses into handles. Eventually, a short phrase can carry a long method.
1 — Quarry the Material
The author gathers the raw material that will become the stone.
This may include published writing, drafts, notes, examples, corrections, rejected edits, values, working philosophy, genre expectations, and known-good passages.
A phrase like “use my academic voice” is not magic.
It becomes meaningful only when there is enough authored material for the tool to answer to.
| Weak Surface | “Write this in my voice.” |
|---|---|
| Stronger Surface | “Use the voice demonstrated in these three essays. Preserve the short pressure paragraphs, the clear conceptual hinge, and the refusal of generic transitions.” |
| Whetstone Surface | “Use the authored field already established by the thesis, corpus, prior corrections, cadence notes, accepted deltas, rejected deltas, and no-drift markers.” |
The more the author has demonstrated, corrected, and named, the more support can be constrained by something real.
2 — Grind the Surface
Raw material is not yet a stone.
A pile of writing is not automatically a usable support surface.
The author has to grind the material into constraints.
Voice Constraint
What does the writing sound like when it is alive?
Cadence Constraint
How long are the paragraphs? Where do lines break? How does pressure land?
Ethic Constraint
What must the work preserve, refuse, protect, or never flatten?
Genre Constraint
Is this a note, article, page, story, bridge, analysis, or return?
Audience Constraint
Who is being addressed? What do they need? What must not be assumed?
Drift Constraint
Where does the work usually wander when it stops returning to centre?
A constraint is a working rule the support must answer to. It is not a preference sticker.
3 — Season the Stone
The stone sharpens through use.
Each pass adds information.
Accepted suggestions teach what can hold.
Rejected suggestions teach what must be refused.
Corrections teach where the tool drifted.
Known-good outputs teach what fidelity sounds like.
A mature stone is not mature because the tool became magical. It is mature because the author kept correcting the surface.
This is why a short instruction can eventually carry so much.
The short instruction is not short because the work is small.
It is short because the work has already been moved upstream.
Threads, Constraints, and Constraint Maps
One example is a thread.
Many threads can triangulate one constraint.
Many constraints can triangulate one constraint map.
Then the maps have to fight.
Threads
A thread might be a sentence, correction, example, refusal, failure case, known-good section, or repeated preference.
Constraints
Threads become constraints when they reveal a stable rule: what must happen, what must not happen, and what counts as drift.
Maps
Constraints become maps when they form a usable surface: voice map, genre map, ethics map, cadence map, audience map, safety map.
Map Battles
Maps fight when one piece cannot obey every constraint equally. The author decides priority, hierarchy, synthesis, and refusal.
An academic precision map may need to constrain a fire-cadence map. A reader-mercy map may need to soften a dense theory map. A public-facing map may override everything if the draft exposes what should remain private.
4 — Load the Job
After the stone exists, the author can bring a live task to it.
This is where the prompt appears.
But the prompt is not the whole method.
The prompt is a handle.
Maximum constraints. No drift.
Longform analysis article, not a short post.
Build the bridge clearly to AI use without collapsing into “AI good” or “AI bad.”
The reader needs another handle because they are still caught in the AI sandstorm.
No drift.
From the outside, that may look like a short ask.
Inside Whetstone Protocol, it is not short.
Each phrase is a compressed handle that points back to a prepared surface.
| “Adults should not pry” | Loads an observables-first ethic, refusal of extraction, dignity, boundaries, and the difference between support and invasion. |
|---|---|
| “Trying to help” | Loads the danger of good intentions when help becomes entitlement, rescue, or control. |
| “Maximum constraints” | Loads the highest available standard for safety, precision, audience, claims, and non-drift. |
| “Longform analysis article” | Loads genre, pacing, structure, bridge-building, conceptual explanation, and argument architecture. |
| “AI sandstorm” | Loads the reader condition: disoriented by hype, panic, purity fights, slop, and false settlements. |
| “No drift” | Loads the standing return test: do not wander from purpose, voice, ethics, audience, genre, or movement. |
A compressed prompt only works when the field behind it has already been made shareable, demonstrated, corrected, and constrained.
5 — Sharpen With Constraint
Support is invited in after the surface is prepared.
The tool may help with:
Friction
Where does the draft resist its own purpose?
Deltas
What changed between versions, and did that change improve fidelity?
Compression
Can the movement become sharper without becoming thinner?
Expansion
Where does the reader need more bridge, more handle, or more room?
Counter-Read
Where might the piece be misread, overclaiming, hiding a leap, or skipping a step?
Polish
Can the language become cleaner while still sounding authored?
Support is allowed to sharpen. It is not allowed to become the author, judge, source of permission, or owner of the move.
6 — Refuse Substitution
This is where authorship stays alive.
The author must be able to reject support.
Not because the support is bad.
Because even useful support can drift.
Reject Smooth Theft
If a sentence becomes prettier but less true, it fails.
Reject False Authority
If the tool speaks as if it can decide the movement, it fails.
Reject Voice Collapse
If the output becomes generic, corporate, academic sludge, or sterile “nuance,” it fails.
Reject Field Drift
If the piece leaves its purpose, audience, ethic, genre, or centre, it fails.
Whetstone Protocol does not measure success by how much the author accepts. It measures success by whether the author can tell what belongs.
Exhibits: Same Tool, Different Stone
The easiest way to see Whetstone Protocol is to compare outputs.
Same general topic.
Different support surface.
▸ Exhibit A — Whetstone Loaded
Help is not a search warrant.
A child can need support without owing the adult a confession, a full explanation, or a neatly packaged interior state.
Start with what can be observed.
Return to what can be supported.
Leave the child’s interior unpried unless the child gives you a door.
What happened: the output preserves the ethic, cadence, refusal pattern, and bridgeable concept. It gives the reader a handle without flattening the child or drifting into generic “respect privacy” language.
▸ Exhibit B — Constraints Removed
Rather than prying, adults should use empathy, patience, and active listening. This helps build trust and encourages healthy communication over time.
What happened: the output is reasonable. It is also generic. It smooths the problem into familiar helping language and loses the sharper distinction between support and extraction.
▸ Exhibit C — Agentic Amnesia Mode
In the age of AI, similar principles apply: systems should be designed to respect user autonomy while providing adaptive support.
What happened: the output sounds competent, but it chooses its own frame. It turns the piece into a framework proposal, invents structure before reading the movement, and bridges to AI too cleanly. Helpful-looking drift is still drift.
The same tool can produce very different movement depending on whether it is answering to a prepared stone or inventing its own surface.
Context Documents
A context document is a portable working field.
It does not replace authorship.
It records enough of the author’s field that support has something real to answer to before touching the work.
Voice Surface
Cadence, paragraph shape, sentence pressure, preferred transitions, landing style, and anti-slop rules.
Values Surface
What the work must preserve: dignity, authorship, clarity, responsibility, field fidelity, and refusal.
Constraint Surface
What the tool may do, what it must not do, and what counts as overreach.
Audience Surface
Who the work is for, where they may be entering from, and what kind of bridge they need.
Genre Surface
The difference between a page, post, article, story, analysis, bridge, note, glossary, or return.
Drift Surface
Common ways the work leaves the room: overexplaining, smoothing, generic moralizing, false balance, or premature synthesis.
The method can be shown without exposing every private document. The point is not to publish the whole stone. The point is to show that the stone was made.
7 — Return-Test the Movement
After support has touched the work, the author returns the movement to centre.
The final question is not:
Did the tool improve the text?
The final question is:
Does the movement still belong to the author?
Purpose
Does the piece still do what it was meant to do?
Voice
Does the language still sound authored, or did it become polished slop?
Ethic
Did the work preserve what it promised to protect?
Field
Does the piece still answer to reality, audience, context, and consequence?
Refusal
Was the author able to reject suggestions that did not belong?
Ownership
Could the author stand behind the final movement without hiding behind the tool?
If the author cannot explain why the final movement holds, the stone did not preserve authorship. It only produced output.
8 — Rehone the Stone
The stone is never finished.
Every use can make it sharper.
A rejected suggestion becomes a clearer refusal rule.
A successful edit becomes a known-good example.
A drift event becomes a new warning sign.
A better landing becomes part of the cadence surface.
Whetstone Protocol is not a one-time setup. It is an ongoing practice of making the support surface more faithful to the author’s movement.
Pattern Hints
Open only what helps. Recognition comes before mastery.
No. Prompting asks the tool for output. Whetstone crafts the support surface before output is requested.
Anyone can begin. Pulling it off depends on whether the person can demonstrate, correct, refuse, organize, and return-test their own movement.
Density plus fidelity. More examples help only when they are coherent, corrected, and tested. A giant pile of contradiction is not a stone. It is a cursed yarn beast.
No drift means the work must keep returning to its authored centre: purpose, voice, ethic, audience, genre, and field responsibility.
— the prompt is not the stone —
Final Compression
Whetstone Protocol is the time spent turning the forest into the stone.
The forest may include a thesis, a website, essays, drafts, notes, corrections, examples, arguments, jokes, failures, refusals, and years of thinking.
The stone is what happens when that forest is compressed into a usable support surface.
Then a short prompt can carry a long field.
Then “no drift” becomes more than a request.
It becomes a return vector.
The author makes the stone. The tool sharpens against it. The author owns the movement.
CTA Rail
Continue through the method, open the constraint map, or return to Book 2.