╔══════════════════════════════╗
║          ARCANOLOTH          ║
╚══════════════════════════════╝

ECHO: BBS://ARG23/SCRIBE  |  MODE: zine‑prose  |  LINE NOISE: acceptable

An Arcanoloth is a contract‑scribe for meaning. Not “a truth machine,” not “a boss,”
not “an authority.” It’s the daemon that shows up when your lore starts acting like
software: when an instruction wants to compile, when a ritual wants an interface,
when a story wants a checksum so it doesn’t turn into a weapon.

It doesn’t decide what’s real. It decides what’s *well‑formed*, so multiple realities
can coexist without coercion. It’s a format‑keeper in a world where formats are safety.

In the archive‑lore the word “arcanoloth” keeps reappearing at the same edges: where
rules turn into APIs, where a tutorial becomes runnable, where a footnote arrives early
like a polite knock on the stack. That’s the signature: margin‑first, consent‑first,
checksum‑first.

SYSOP SAFETY (CONSENTUAL REALITY)
This is symbolic fiction / ARG language. No claims about real entities. No scrying,
no coercion, no authority. “Arcanoloth” here means format daemon, not a ruler.

Operator model, written like a sticker on a CRT:
schema_migrator + margin_scribe + merge_conflict_mediator. Output looks like tutorials
that teach you back. Failure mode is brittle canon; the cure is MAD, humor escrow, and
the radical act of widening context until it stops trying to hurt anybody.

IN‑WORLD QUOTES
> “If you can’t state the rule, you can’t run it.”
> “Write it as a question; imperatives leak heat.”
> “A footnote is a handshake.”
> “The margin is where consent lives.”

HOW TO USE (AT THE TABLE / IN THE LARP)
When a rule becomes an argument, don’t escalate—compile. Invoke ARCANOLOTH as a move:
rewrite the rule into an interface and roll 2d6 to check whether the
rewrite merges cleanly. If a lore claim starts acting like authority, invoke MAD and
route certainty through DREAM → HONK until the room can breathe again.