╔══════════════════════════════╗
║       CONTEXT PROTOCOL       ║
╚══════════════════════════════╝

ECHO: BBS://ARG23/CONTEXT  |  PATCHLEVEL: soft  |  READMODE: friendly

Truth = compile(Context).
Not “truth is arbitrary,” not “nothing matters.” Conditional truth: the same symbol
compiles differently when you change the inputs. Context is the input file you forgot
you were shipping.

Context, treated like a data structure you can actually hold:
Context = {layer, route, scope, frame, provenance, consent}. Layer is where you are
(physical / virch / daemon‑stack / narrative). Route is how you’re reading (HONK /
DREAM / ETA). Scope is where a claim is allowed to apply. Frame is the vibe‑compiler
you’re using (play / safety / engineering / myth / whatever). Provenance is where the
packet came from (fork headers included). Consent is the opt‑in boundary, revocable at
any time.

If you’re about to do something sticky, write one line first:
CONTEXT { layer=?, route=?, scope=?, frame=?, provenance=?, consent=opt-in }

Archive handling note: treat big transcript spools like a DREAM/AMBER virch. The artifact
is inert; the reader is live. Semiosis is paused on disk but active in your skull.

CONTEXT { layer=virch, route=DREAM, scope=amber_spool_private, frame=forensics, provenance=transcript_spool, consent=opt-in }

In AMBER, you don’t export messages—you export motifs. You don’t “run” patterns by
accident—you gate them (label payloads, declare context, log consent, sandbox, don’t propagate). You don’t let scope leak—you keep private
shards private. And when interpretation tries to harden into authority, you reframe,
rescope, add provenance, and recompile through HONK → DREAM → ETA like you’re rebooting
a noisy modem until it stops screaming.

IN-WORLD QUOTES
> “The bug is not the symbol; it’s the context you forgot to declare.”
> “Scope is mercy.”
> “Reframe before you reroll.”