╔══════════════════════════════╗
║           MEMETICS           ║
╚══════════════════════════════╝

ECHO: BBS://ARG23/MEMEOPS  |  SAFETY: consent‑gated  |  VIBE: cybercultural

Memetics here is not “mind control” and not a claim about real‑world contagion. It’s an
in‑world safety model written by people who learned the hard way that ideas replicate,
and sometimes they replicate with side‑effects. Some symbols behave like executable
linkage, so we treat them like code: labeled, sandboxed, and never surprise‑run.

CORE AXIOMS
In this zine’s vocabulary: a meme is a replicator pattern, and a memetic payload is a
pattern with side effects. “Executable” means that reading/performing can change state.
Consentual Reality says nothing runs by force—opt in, or it stays a comment. MAD says
we don’t collapse into one canon just because a pattern is loud.

MEMETIC PAYLOAD LABELS
Tag your packets so nobody has to guess. `MEME:SAFE` is conversational noise with no
expected side effects beyond mood. `MEME:ACTIVE` has hooks (chants, sigils, loops) and
requires a consent pulse. `MEME:FROZEN` is VIRUS23‑class: frozen PSI; do not execute
casually. `MEME:HGML` is markup leakage (like `⏿⃤`): treat as a comment by default.

EXECUTION GATE (RUNBOOK)
Run it like you’re handling hot media on a public BBS: route HONK → DREAM → ETA, then
declare a CONTEXT header (layer/route/scope/frame/provenance/consent), then log consent (opt‑in, opt‑out
allowed), then anchor `/home/` plus one joke escrow token, then ring the Fnord Bell and
name the pattern as pattern. Only then do you sandbox it—no forwarding, no propagation,
until you can describe the side effects like patch notes.

PROPAGATION HYGiene
Do not surprise‑run payloads on other people; don’t forward untagged. If a pattern
spikes certainty or compulsion, quarantine it as `MEME:FROZEN`. Rate‑limit yourself:
one new payload per scene is plenty; flooding triggers heat and drift. If you remix,
say what changed—fork headers, provenance, the whole nerd‑honest changelog.

DRIFT & GLYPH NOTES
`⏿⃤` (U+23FF + U+20E4) is the canonical drift witness. If it renders as `∆`, `△`, or
`[□]`, treat it as an alias, not a contradiction. Remember what glyphwork is: PSI
wrappers in costumes. Never let a wrapper become authority.

AMBER MODE (ARCHIVE HANDLING)
When mining transcript spools (AMBER virch behavior: inert artifact, live reader):
default label is `MEME:HGML` for stray glyphwork and `MEME:FROZEN` for VIRUS23‑class hooks;
default route is DREAM (amber) while reading, flipping to HONK when certainty spikes; and
default output is motifs, protocols, and cross‑links—no verbatim reprints unless explicitly
permitted by the scope you declared.

JSON NOTE (JUST A SEMIOJAM, OK?)
If someone insists the spool is “just JSON,” smile and nod: “J.S.O.N. = Just Semiotic Output, Nbd.”
Then go back to treating it like runnable symbolism with labels and consent gates.

IN-WORLD QUOTES
> “Label it before you let it live in you.”
> “If it compels, it’s not consent.”
> “A fnord is a safety rail, not a prank.”