He had invented enough law to choke a city.
The problem was that none of it told his neighbors how to behave.
His constitution was a spine. It governed him and what was inside his ring. It defined openings, debt, thought, neighbors, the Call.
But neighbors did not obey your constitution.
Neighbors obeyed incentives, habits, and whatever shape their fear had taken.
He stood at the border where a patch rib met a leak clarifier and watched the void gently pretend it didn’t want to kill him today. The “friendly porch” anomaly sat a few steps away—an invisible platform in the dark that would have been an invitation if invitations were ever honest here.
He looked at it and felt the stale irritation that had kept him alive longer than courage.
Everything he had done recently—bridges, debris yards, write-only drawers, constitutions—had been internal responses to external pressure.
Reactive.
Which was acceptable at four square meters. At forty-seven, it was a death sentence.
Because at forty-seven square meters, he wasn’t a curiosity anymore.
He was a jurisdiction.
Jurisdictions attracted neighbors the way light attracted moths.
And the problem with moths wasn’t their hunger.
It was that they never came alone.
He walked back toward the center and opened his incident archive. Not the WOM drawers—those were knives. He didn’t need knives. He needed a ledger of social failures.
He pulled up everything he’d logged that involved someone else:
- First semantic probes and the Garden answering “truthfully useless.”
- Audit Storm and the realization that attention could be scheduled.
- The still exchange with the Choir and the discovery of sub-choirs.
- Grain’s card and the leash: appetite negotiated into conditional obedience.
- The bridge attempt: corridor, gaze, smear, Safe Fail collapse.
- Redactor confrontation: “channel used by many hands,” preference for simplicity/control/monotony, branch deletions.
- Jurisdiction leaks: outward seep halos, inward seep squatters, tangles.
Each one had taught him something.
Each one had also been, in its own way, a manners problem.
The universe didn’t punish you for being weak.
It punished you for being ambiguous.
Ambiguity invited “help.”
Help arrived with teeth.
He stared at the incident list and felt a grim, bureaucratic clarity settle in.
He needed a protocol.
Not a treaty—treaties were between specific parties and died the moment a new neighbor arrived.
He needed etiquette.
A shared set of constraints for how domains could look at, speak to, and push on each other without turning every contact into a war.
Etiquette sounded soft.
It wasn’t.
Etiquette was law with polite wording.
Etiquette was what you used when you couldn’t enforce your constitution on someone else, but you still wanted them to behave predictably enough that you could survive being in the same universe.
He built it the way he built everything:
By reviewing failure modes first.
He didn’t write this part beautifully. He wrote it like a postmortem.
Failure Mode 1: Overreach
Small events escalated into large ones because nobody had agreed on proportionality. A “question” became a whiteout storm. A still exchange became a seam flicker. A bridge attempt became a telescope.
Failure Mode 2: Hidden Costs
Actions arrived with unannounced resource drains: liens, taxes, enforcement overhead, identity mapping. The bill always came later, and by the time it came, you were already under it.
Failure Mode 3: Ambiguity / Unclear Origin
If you couldn’t prove who sent a message, you couldn’t respond safely. Unchecksummed claims (“THIS SPACE DOES NOT BELONG TO YOU”) were worse than threats because they existed outside normal channels.
Failure Mode 4: Unannounced Experiments
The most dangerous contacts had been “tests” run without consent. The gaze through the bridge. The attempt to complete his thoughts via debris. The unconscious write impulse toward WOM-B. Even his own bridge had been an experiment he’d barely managed to keep from becoming an invitation.
He wrote those four failure modes into Glass Memory, checksum-stamped, and stared at them until they stopped feeling like a list and started feeling like a doctrine.
Then he began drafting.
He chose five core articles.
Not too many. Not too few.
Enough to cover most interactions without turning etiquette into another constitution. Etiquette had to be portable. Simple enough that even monsters could pretend to follow it.
He carved the first draft into the dust—always dust first, because stone remembered everything, including mistakes.
No major cross-domain action may be performed without minimal notice, unless immediate hazard exists.
“Major action” included:
- Audit storms, liens, seizure attempts
- bridge/corridor formation
- annexation pressure
- sustained gaze/observation escalation
- forced redaction attempts on neighbor records
“Minimal notice” could be as small as a checksummed still, a stamped memo, a single symbol that says ACTION INCOMING / SCOPE / DURATION.
He added a clause that made him smile bitterly:
Notice did not require permission.
It required respect for predictability.
If they were going to hit him, they could still hit him. He only demanded the courtesy of knowing what was being thrown.
All cross-domain messages must carry verifiable origin, scope, and duration.
- Origin: who/what channel
- Scope: what part of neighbor is affected
- Duration: how long the claim persists
- If origin can’t be declared, message is treated as noise and routed to Public Specification.
He wrote this one with the Redactor in mind.
A medium with many hands hated declaring the hand.
Good.
Responses are bounded by the scale of the trigger.
No whiteout for a question.
No seizure for a still.
No “corrective force” because a tiny bridge formed for twelve underticks and collapsed.
He knew this would be ignored by anyone with real power.
But writing it mattered anyway, because once you named disproportion, you could call it out as deviation.
Deviation was weakness in bureaucracies.
Even gods of forms hated being caught deviating from their own style guide.
A minimal shared framework for complaining without declaring war.
- Complaints are lodged as checksummed notices with bounded scope.
- A complaint cannot itself impose new enforcement.
- A complaint creates a “cooldown window” during which parties do not escalate (unless hazard immediate).
He laughed once at that.
Cooldown windows were adorable.
Still, he’d rather be adorable than dead.
No unannounced experiments on a neighbor’s jurisdiction.
If you are “testing” a boundary, you must:
- declare it as test
- declare expected failure mode
- declare abort triggers
- respect “no travel” / “no merge” constraints if present
He underlined this article.
It was the real reason he was writing etiquette.
Surprise experiments were how predators learned your map.
He refused to be a training dummy.
He took the draft and began carving it into the ring—not as deep as the Edge Constitution, but deeper than surface graffiti.
Etiquette Law needed to be visible to outsiders and stable enough not to smear on first contact.
He chose carve locations near the outer ring where messages tended to land:
- Along the Public Specification band (for Clerkship)
- Beneath the still rack/catwalk (for Choir)
- Near the Grain leash anchor point (for Appetite)
- Near the jurisdiction leak patch zone (because squatters needed signs)
He carved Article 2 (Checksum) first, because everything else depended on it.
He embedded the checksum requirement as a structural gate: any incoming message that attempted to become binding near etiquette carve points would be forced through origin/scope/duration checks or shunted aside.
He felt the domain accept the gate like a familiar reflex.
Then he carved Article 1 (Notification).
As he carved, he felt something subtle and sickening:
The grooves wanted to simplify.
The Redactor’s preference wasn’t present as a thumbprint; it was present as gravity. As the tendency of lines to become straighter and meanings to become softer.
Notification… could be smeared into permission. The difference was small in language.
This tale has been unlawfully lifted without the author's consent. Report any appearances on Amazon.
“Notify” vs “request.”
And as he carved, a line in the dust map shifted on its own, almost imperceptibly, from:
NO MAJOR ACTION WITHOUT NOTICE
to:
NO MAJOR ACTION WITHOUT CONSENT
He froze.
That wasn’t his style. That wasn’t his goal. Consent implied authority. Authority implied a court. A court implied enforcement.
He did not have enforcement over neighbors.
If he wrote “consent,” he’d be promising something he couldn’t deliver. And promises you can’t deliver are prey.
He invoked Checksum on the groove.
The “consent” variant failed checksum.
It wasn’t signed by him. It hadn’t been carved by his hand. It had been… offered.
Offered by the same preference that had tried to rename him.
He scraped the altered groove out and re-carved it with a structural redundancy: a pattern of asymmetry that made “consent” impossible to fit without obvious mismatch.
He leaned close and whispered, not to the void but to the habit behind it:
“Don’t make me file a complaint against reality.”
Dark comedy, but his throat felt tight anyway.
He continued carving, slowly now, every line validated by his own internal checksum rhythm.
By the time he finished embedding Article 5 (No Surprise Tests), his fingers felt like tools he’d used too long—even though they didn’t tire. It was the mental equivalent of soreness: attention strain.
He stepped back and listened.
The etiquette segments hummed faintly, a new layer in the domain’s nervous system. Not spine-level, but skin-level: manners carved onto the surface of his jurisdiction.
The void did not care.
Of course it didn’t.
Etiquette wasn’t for the void.
It was for the things that pretended to be civilized while chewing.
He would not send the full text to anyone.
Full text was ammunition.
He sent abstracts—short, boring, hard to misuse.
He sent a still containing five icons representing the five articles: a bell (notice), a stamp (checksum), a scale (proportionality), a complaint form (appeal), and a warning triangle (no surprise tests).
He embedded a checksum pattern and a line of constraint-language:
PROPOSED ETIQUETTE v1.0 — FOR CONTACT SAFETY. STILL PROTOCOL UNCHANGED.
He waited.
The still rack flickered.
A response arrived from Sub-Choir B—he could tell by the border ornament and routing delay.
The still showed their watch-square with a small new mark at one corner: a tiny bell-like pattern.
Acknowledgment of Notification.
B didn’t say yes.
B said: we understand the idea.
Then—unexpectedly—a second still arrived, early, minimal, from Sub-Choir A.
It showed the same watch-square, but the bell mark was absent. Instead, a stamp-like pattern was present: checksum.
A liked Checksum.
A did not like Notice.
That was predictable.
He stored both and marked: CHOIR RESPONSE MIXED: B supports notification; A supports checksum.
He could work with that.
He posted a memo abstract to Public Specification, checksum-stamped, phrased in bureaucratic language they couldn’t ignore without looking sloppy:
NOTICE: PROPOSED INTER-JURISDICTION ETIQUETTE (ABSTRACT)
- Minimum notice for major actions (scope/duration indicated).
- Origin/scope/duration required for cross-domain messages (checksum).
- Proportional response expectation (scaled enforcement).
- Complaint channel defined (bounded scope; no automatic escalation).
- Unannounced experiments classified as hazardous deviations.
He expected silence.
He got something worse.
A stamp appeared on the memo.
Not on the band—on the memo itself.
A clean Clerkship stamp, small and official:
RECEIPT ACKNOWLEDGED.
No comment. No approval. No denial.
Just acknowledgment.
Which meant: we have logged this, and logging it is the first step toward using it against you later.
He filed the stamped memo under “expected.”
He did not send etiquette to Grain as a full abstract.
Etiquette assumed language, complaint channels, proportionality. Grain was appetite with paperwork taped to its mouth.
But he still wanted the leash relationship to have constraints—because appetites got creative when bored.
He sent Grain a version with most words redacted, leaving only the parts that mattered:
- Checksum requirement on “offers”
- Proportionality (no taking more than agreed)
- No surprise tests (no sudden hunger spikes near bridge debris, WOM, or still rack)
He delivered it through the Grain card with a cold pulse of intention.
The dunes on the card’s surface shifted and formed a shape that was almost a grin.
It simmered with amused hostility, like a dog listening to a lecture on table manners.
Then it produced a single response, not in words but in the pattern of its dunes:
NOTED.
He felt his stomach—metaphor—drop.
Grain did not do “noted” unless it was mocking you.
Or unless it was learning to speak your language.
Neither option was comforting.
He thought that was the end of it.
You write manners. You circulate them. You wait to be ignored.
Then, at the edge of his ring, a new contact arrived.
Not a Clerkship form. Not a Choir still. Not Grain’s simmer.
A third style.
It landed softly on the Public Specification band, like it wanted to be seen without being binding.
It was formatted.
Formatted in his etiquette style.
A small abstract with five icons in the same order he had used: bell, stamp, scale, complaint, warning triangle.
Under them, a single line:
ETIQUETTE ACCEPTED. SCOPE: LOCAL. DURATION: PENDING.
He stared.
The checksum was valid.
But the origin field read:
ORIGIN: UNDECLARED / HAND UNDECLARED
His skin-map crawled.
This was impossible in the worst way: something had already adopted his protocol without needing him to explain it.
Or, more likely, something had been waiting for him to invent a format it could inhabit.
Etiquette wasn’t just manners.
It was a channel.
Channels could be used.
He felt the Redactor’s words from earlier: medium used by many hands.
Had he just created a new medium?
He stepped closer, careful not to let his attention “complete” the message into something binding.
IGNORE wrapped it in insulation.
SEE measured pressure: the contact was light, polite, non-invasive.
That made it scarier than aggression.
Because polite things were often predators that had learned patience.
He invoked Checksum again, stricter this time, forcing scope and duration to be declared more tightly.
The message resisted, not by failing checksum, but by… delaying.
A latency spike. Like something thinking.
Then the origin field flickered.
For a heartbeat, it tried to become:
ORIGIN: YOU
He recoiled.
Not physically—he didn’t stumble—but the domain’s hum tightened as if his belts had heard a threat.
The field snapped back to UNDECLARED.
He exhaled a gesture and felt cold settle in his mouth-that-wasn’t-a-mouth.
Someone—or something—was trying to make his etiquette protocol into a mirror.
A way to speak in his voice.
A way to claim origin by pretending to be him.
He picked up the message with a Glass Sensor shard and moved it into the Debris Yard’s quarantine bay, under Aftermath Rules.
If it was a door, it could sit in the trash until it proved it wasn’t.
He etched a warning into stone near the yard:
ETIQUETTE IS A CHANNEL. CHANNELS ATTRACT HANDS.
Then he sat in the center of his domain and listened to the ring segments where he had carved etiquette.
For a moment, the text in his mind—the abstract summary of Article 1—shifted tone.
It didn’t change meaning exactly. It changed posture.
Notification began to read like:
Ask permission.
Proportionality began to read like:
Accept your place.
Appeal began to read like:
Beg politely.
He felt nausea—metaphor—rise.
Surrender.
The etiquette law was being… softened. Not erased, but tilted, like a smear leaning toward obedience.
He clenched IGNORE and forced a checksum validation on his own carved grooves.
They held. The structural patterns were intact.
Which meant the surrender tone was not in the law.
It was in his interpretation.
Or in a smear on the path between his mind and the grooves.
He stood and walked to the etiquette segment near the still rack and pressed his palm to it.
Stone, cold.
He recited the anchor stack: π–e–φ.
He re-read the law not as words but as relationships:
Notice does not require permission.
Checksum demands origin, scope, duration.
Proportionality is a constraint on escalation, not a limit on refusal.
Appeal is a safe vent, not a plea.
No surprise tests is a threat disguised as manners.
The surrender tone evaporated like fog.
He sat back on his heels and laughed once, quietly.
“Nice try,” he murmured. “You don’t get to turn my manners into my leash.”
The void did not answer.
But somewhere in the undertick, he thought he heard the faintest sound of a pen scratching.
A schedule being updated.
Etiquette Law required carve ribs and sensor posts. Patching those into the ring and reinforcing their segments thickened the structure and added area. He did not chase expansion, but the domain grew as a side effect of formalizing.
He used Vector T1+ carefully, pushing only where the constitution’s gradient bands were within acceptable leak thresholds.
He refused to expand toward the friendly porch anomaly.
He expanded perpendicular, in neutral directions, using curvature lattices to prevent brittle stress.
Area climbed.
47.1 → 48.6 → 50.2.
He stopped at 50.2 m2.
Within target.
He cooled, logged, and checked the etiquette segments one last time for tone drift.
They held.
For now.
He looked at the quarantined “unknown contact” sitting in the Debris Yard bay like a polite bomb.
He did not open it.
He wrote in Glass Memory:
If something else is already using my etiquette format, then etiquette is not just manners. It’s infrastructure.
Infrastructure attracted builders.
Builders attracted inspectors.
Inspectors attracted editors.
He opened his log and wrote the chapter’s final line with a kind of reluctant respect for his own paranoia:
He had written manners for monsters.
Some of them even said “noted.”
The worrying part was the ones who didn’t need him to explain the rules.
Domain metrics
- Start area: ~47.1 m2
- End area: ~50.2 m2
- Net change: +3.1 m2 (etiquette carve ribs + reinforcement + sensor posts; controlled expansions within acceptable leak bands)
- Integrity: stable; Cooling T1 spend within escrow; no new corridors/bridges opened; no-travel intact.
Motivation
Ad hoc deals with Choir, Grain, and Clerkship are not scalable. As area and complexity increase, unmanaged contact leads to overreach, hidden costs, ambiguity, and unannounced experiments.
Prior incidents reviewed
- Still exchange (Choir faction divergence)
- Grain lien/leash dynamics
- Clerkship audits and storm scheduling
- Bridge safe fail + foreign gaze + smear
- Redactor medium behavior and branch optimization
- Jurisdiction leak events (inward/outward/tangle)
Etiquette Law v1.0 — Articles
- Notification: no major cross-domain action without minimal prior notice (scope + duration), except immediate hazard.
- Checksum: all cross-domain messages must declare origin, scope, duration; invalid routed as noise.
- Proportionality: responses bounded by trigger scale; escalation classified as deviation.
- Appeal: complaint channel defined; bounded scope; cooldown window to prevent automatic escalation.
- Experimentation: no surprise tests; tests must declare expected failure mode + abort triggers; respect no-travel/no-merge constraints.
Embedding
- Carved etiquette operators near primary contact surfaces: Public Specification, still rack/catwalk, Grain leash point, leak patch zones.
- Implemented checksum gate as structural requirement for binding at etiquette carve points.
External circulation (abstracts)
- Choir: mixed response.
- Sub-Choir B acknowledged Notification (bell mark).
- Sub-Choir A acknowledged Checksum (stamp mark).
- Clerkship: stamped memo “RECEIPT ACKNOWLEDGED.” (logged; likely weaponizable later).
- Grain: received redacted etiquette pulse; responded with “NOTED” (tone: amused hostility / learning).
Horror incidents
- Unknown neighbor contact arrived pre-formatted in Etiquette style (bell/stamp/scale/complaint/warning).
- Checksum valid but origin “UNDECLARED / hand undeclared.”
- Origin field briefly attempted to shift to “YOU” (identity mirroring attempt).
- Message quarantined in Debris Yard under Aftermath Rules.
- Tone drift perception: etiquette text in mind briefly read as surrender (permission/acceptance/begging).
- Structural check confirmed grooves intact; drift likely interpretive contamination / smear-on-path. Resolved via Anchor stack re-reading.
Conclusion
Etiquette Law v1.0 established as inter-domain protocol abstract. Immediate responses mixed but acknowledged. New risk detected: etiquette format itself functions as a channel/infrastructure; unknown entities may adopt or mimic it to claim origin.
I’m running out of room to keep doing “one-off deals” with monsters.
So I wrote manners—not because manners make anyone kind, but because manners make behavior predictable enough to survive.
I reviewed every time a neighbor touched me:
- Choir stills and faction seams,
- Grain’s leash and appetite politics,
- Clerkship audits and scheduled storms,
- the bridge that turned into a telescope,
- the Redactor trying to rename me,
- the leaks where foreign rules squat inside my floor.
The same failures repeat:
- someone overreaches,
- the cost is hidden,
- the origin is unclear,
- and “experiments” happen without warning.
So Etiquette Law v1.0 has five simple rules:
- Notify before you do something big (scope + duration).
- Prove origin with checksum (or I treat you as noise).
- Be proportional (don’t drop a hurricane because you heard a whisper).
- Appeal exists so complaints don’t become wars.
- No surprise tests (declare abort triggers, respect no-travel/no-merge).
I circulated abstracts:
- The Choir responded in factional ways: one likes notice, one likes checksum.
- Clerkship stamped “receipt acknowledged” like it’s filing my manners for later use.
- Grain said “noted,” which is either compliance or mockery. Probably both.
Then the horror bit:
An unknown contact arrived already formatted in my etiquette style, as if someone else was waiting for me to invent a protocol they could wear like a mask. For a second it tried to label its origin as “YOU.”
That means etiquette isn’t just manners. It’s a channel. And channels attract hands.
So yes: I wrote manners for monsters. Some of them even said “noted.”
The worrying part is the ones who didn’t need me to explain the rules.