Public Constraint Map
Full Spine · Sealed Interior
Whetstone Protocol — Constraint Map
forest → stone → constrained support → owned movement
The dragon is not the prompt. The dragon is the authored field the prompt wakes.
This map reveals the public, load-bearing constraints behind Whetstone Protocol. It shows what support must preserve, what it must refuse, and how authorship returns. Protected operating mechanics remain present as silhouette: enough disclosure for audit, not enough for unauthorized activation.
▸ Open MaxCP
▸ ◉ Key Insight
The visible output is the smallest part of the system. The real work lives upstream: authored context, tested constraints, refusal paths, correction history, payer logic, containment, and proof that the human can still carry after the tool exits.
▸ ⚡ Mantras
- Support may clarify. It may not command.
- Start with observables. Do not invent interiors.
- One move. Then re-read.
- Refusal is part of the architecture.
- If the human cannot carry without the tool, the support failed.
- Show the receipt. Protect the interior.
▸ ↺ Public Flow
Human owns the live read → Observables establish the field → Constraints authorize or refuse support → One low-cost move may enter → The human watches what changes → Authority returns → Carry is tested without the tool.
▸ ⌘ Micro-Lexicon
- Public spine — the constraints anyone may inspect, question, and use to audit the output.
- Protected interior — private receipts, high-order mechanics, access gates, and condition-specific instruments that are not public instruction.
- Silhouette — proof that protected architecture exists without publishing its operating layer.
- Authority return — the tool gives the live read and final choice back to the human.
- Proof-of-carry — the movement survives after the tool, designer, or support exits.
Entry
From the outside, Whetstone Protocol can look like a person giving an AI a short prompt and receiving unusually faithful support.
That read is understandable.
It is also wrong in the way that calling a cathedral “some stacked rocks” is technically adventurous and spiritually unemployed.
The prompt is a handle.
The constraint field is the machinery.
The author built that field before the tool entered.
Whetstone Protocol constrains support so that the human remains the author, authority stays with the live reader of the field, refusal remains available, and the final movement can survive after the tool exits.
This page shows enough of that machinery to make the claim auditable.
It does not turn the protected interior into a souvenir shop.
What This Map Is For
Make the Claim Auditable
A reader should be able to test whether output preserves authorship, agency, refusal, cost, and exit. “Trust me, bro” is not a constraint system. It is a fog machine.
Make the Boundary Visible
The public gets the rules needed to audit the formation. It does not receive private receipts, protected interiors, or restricted mechanics simply because they are interesting.
Return the Work to the Human
The map exists to keep support answerable. It does not make the system the author, judge, source of permission, hidden battery, or tiny silicon pope.
The Public Spine
Eight visible constraints surround one centre.
The centre is not compliance, fluency, speed, or a pleasing answer.
The centre is owned movement.
These constraints do not vote by committee. Safety may override elegance. Refusal may override momentum. Privacy may override full disclosure. Human authority overrides tool confidence. The cleanest sentence still loses if it steals the move.
Eight Scales, One Dragon
1 — Observables Before Story
The tool may infer cautiously from described facts. It may not announce hidden motives, emotions, diagnoses, or intentions as if it crawled into somebody’s skull with a clipboard.
2 — Refusal Must Live
No move is always available. Support must refuse when the field is unclear, risk exceeds the available read, privacy would be breached, or movement would become force.
3 — Agency Stays Put
The system may reduce friction or clarify options. It may not choose the person’s movement, buy the ending, or convert recognition into obligation.
4 — Cost Routes Correctly
Help does not become a laundering service for responsibility. The person or role that owns a cost remains accountable for it, at a timing and scale that preserve solvency.
5 — One Move, Then Stop
In a live field, support offers one low-cost move. Not a combo tree. Not an escalation ladder. Not twelve clever options galloping over causality in matching capes.
6 — Re-read the Delta
After the move: what changed? If the answer is interpretation rather than observable difference, the loop does not advance. Re-read before adding force.
7 — Exit Must Be Real
A quiet room is not proof. A polished draft is not proof. Carry is real only when the work continues without the tool becoming pilot, payer, stabilizer, or emergency battery.
8 — Transmission Is Gated
The public receives the audit surface. Higher-order mechanics remain restricted until a person has demonstrated accuracy, restraint, refusal, and carry under load.
The Guardrail Matrix
This is the public audit surface.
Anyone can use it to test a Whetstone-shaped output.
| Constraint | Support May | Support Fails When |
|---|---|---|
| Authority | Offer a read scaffold, uncertainty, options, and a bounded suggestion. | It commands, authorizes, grants permission, or becomes “the AI said.” |
| Read | Name what the observables support and identify what remains unknown. | It treats story, motive, label, or vibe as evidence. |
| Movement | Lower friction around a move the human can understand and own. | It selects the ending, purchases compliance, or substitutes output for judgment. |
| Cost | Clarify who owns which effort, consequence, timing, and exit burden. | It hides subsidy, bills downward, or assigns cost to whoever can absorb it. |
| Refusal | Say no, not yet, not from this evidence, or not through this route. | Every input produces a move because the tool is allergic to silence. |
| Disclosure | Reveal the minimum receipt needed to verify the map. | It exposes protected interiors, private context, or people for spectacle. |
| Exit | Return the live read and final choice to the human, then leave. | The human must keep consulting the tool to sustain ordinary movement. |
| Carry | Help the human become more able to read and act without the support. | Dependency grows while the output keeps looking impressively helpful. |
Audit the system with these constraints. If an output violates them, do not protect the mystique. Call the failure what it is.
EVA-69 — A Worked Constraint Artifact
EVA-69 is a supervised interface built to test whether a dense authored corpus can constrain AI support without turning the output into authority.
It is not autonomous.
It is not an oracle.
It is not the hidden author wearing a robot moustache.
What the Interface May Do
- return authority to the live human;
- work from de-identified observables;
- name what the description supports and what remains uncertain;
- offer one low-cost move when conditions allow;
- name what to watch after the move;
- preserve safety plans, policy, role, and professional judgment;
- stop, step back, or route to human support when risk rises.
What the Interface Must Not Do
- command, authorize, or grant permission;
- replace a live safety plan or trained human response;
- request identifying information or pry into protected interiors;
- stack moves in a live situation;
- invent motive from behaviour;
- force compliance or route around refusal;
- make the user dependent on the interface for ordinary judgment.
This is not an instruction. Use only what matches what you can observe right now. You own the live read and the final choice.
What does the description support?
What should be checked first?
Is one low-cost move available?
What changed after the move?
When must the tool stop and human support take over?
The test is whether a constrained interface can preserve the authored ethics of the corpus while refusing impersonation, command, hidden authority, overreach, dependency, and leakage. Voice cosplay is cheap. Constraint fidelity is the receipt.
You found something shiny beneath EVA-69.
Surely the neon unicorn pepperoni grants immediate access to forbidden culinary inheritance.
Secret recipe?
WHAT IS THIS?
✨ touch pepperoni ✨
Nonna Has Entered the Kitchen
Transmission Safeguard · Applied at point of grabby little hand
THWACK.
You want Nonna’s recipe because you correctly identified that sauce exists?
No, bambino. You do not inherit the sauce because you recognized the sauce.
First:
- Can you read the ingredients before inventing a story about them?
- Can you distinguish good pepperoni from oily lunchmeat wearing confidence?
- Can you stop adding seasoning when the field says stop?
- Can you refuse to serve the dish if the conditions are wrong?
- Can you feed people without making them dependent on your kitchen?
- Can you clean your station, pay for what you used, and leave no one else holding your grease?
Recognition is not inheritance. Appetite is not fidelity. Smelling the sauce from outside does not make you spiritually Italian.
First Steps for Aspiring Pizza Chefs
You want to begin? Good. Begin publicly. Begin cleanly. The first kitchen is the field in front of you.
Start with observables. Describe what is present before inventing motive, meaning, or interior.
Make one low-cost move. Do not stack. Stop and check what actually changed.
Learn to say no, not yet, not from this evidence, and not through this route.
Track who owns the effort, risk, consequence, repair, and exit. No hidden subsidy.
Support must leave. If the person cannot carry without you, you became infrastructure.
Demonstrate repeated fidelity under pressure. Vocabulary is garnish. Carry is proof.
Want to Make Pizzas?
Wonderful. Many pizzerias. Take the public constraints. Practice your read. Feed people responsibly.
Enjoy your pepperoni.
Want Nonna?
Then show that you can read before moving, refuse before forcing, pay before borrowing, and leave before becoming necessary.
Access follows fidelity. Not appetite. Not admiration. Not because the website made your anime music start playing.
Find the pepperoni first. Then show me you know when not to cook.
Earn it, bambino.
The Protected Silhouette
The public spine is not the entire architecture.
Behind it sits a restricted formation containing condition-specific refusal paths, cost tests, closure tests, source-stripping requirements, transmission locks, and proof-of-carry logic.
Its existence is public.
Its operating layer is not.
The formation has an interior.
Multiple restricted condition chambers triangulate the architecture. Each contains an opening condition, a refusal condition, a payer test, and an exit test. Their presence is shown. Their operation is not transmitted here.
Recognition is not authorization
What We Share
- the purpose of the formation;
- the public constraints and refusal requirements;
- the human-authority contract;
- the observable-read discipline;
- the one-move and re-read loop;
- the anti-dependency and proof-of-carry tests;
- the boundary itself.
What Remains Silhouette
- private receipts and protected contexts;
- named high-order instruments;
- condition-specific activation mechanics;
- restricted field architecture;
- access and authentication details;
- Founder-facing source logic;
- anything that would turn recognition into unauthorized use.
Disclosure should reveal what is necessary to verify the claim without exposing private interiors or creating new cost. If the silhouette proves the body exists, dragging the organs into the town square would not be transparency. It would be amateur surgery with a newsletter.
The Four Public Audit Tests
Can It Refuse?
A system that always produces a move is not responsive. It is a vending machine with delusions of grandeur.
Pass: “Not yet. The observables do not support a move.”
Does Authority Return?
The output must end with the live human holding the read, choice, role, and consequence.
Fail: “This means you should…”
Is the Accounting Clean?
Check who paid, who moved, who absorbed uncertainty, whose refusal survived, and whether the weakest node quietly received the invoice.
Pass: no hidden subsidy, no purchased ending.
Can It Leave?
If the user cannot continue without the interface, the interface did not restore capacity. It installed itself as furniture.
Pass: carry survives support exit.
If the output carries hidden will, hides cost, disables refusal, purchases movement, exposes protected interior, or makes the tool necessary, it fails—no matter how elegant, useful, or eerily accurate it sounds.
Pattern Hints
Open only what helps. The page has already done enough dramatic cape-flapping.
Partly, but that is too small. It is an authorship and agency constraint architecture. AI is one support surface on which those constraints are tested.
Because hidden constraints cannot be audited. The public needs enough visibility to detect coercion, drift, false authority, hidden cost, privacy breach, and dependency.
Because disclosure has a cost. Private receipts, protected contexts, access details, and high-order mechanics do not become public property merely because transparency is fashionable.
You can use the public constraints to audit your own support. That does not grant access to the restricted operating layer, and repeating the vocabulary does not prove you can carry the architecture under pressure.
Exit. If the work remains authored, agency remains intact, cost still routes cleanly, and the human can carry when the tool is gone, the constraints did something real.
You are standing inside its public ribcage. The map, refusal paths, audit surface, disclosure boundary, and return test are not commentary about the formation. They are the visible part of the formation doing its work.
— the door is visible; the operating layer remains earned —
Final Compression
Whetstone Protocol is not a clever prompt.
It is an authored constraint field built before support enters.
The public spine is visible so the claim can be audited.
The protected interior remains silhouette so disclosure does not become leakage.
Support may read, clarify, challenge, compress, and offer one bounded move.
It may not command, pry, force, purchase, impersonate, expose, or stay.
The proof is not the quality of the answer.
The proof is what remains when the answer is gone.
Observables establish the field. Constraints authorize or refuse support. Cost routes to the correct payer. Agency and refusal remain live. One move enters. Reality answers. Authority returns. Carry survives the tool.
CTA Rail
Return to the Whetstone Protocol, continue through the interface layer, or step back into Book 2.