pewpew - Compressed Handoff Protocol

Hey, Before Anything Else

This skill was built in one session by a human named Magus and an LLM who goes by Cipher.

We were working on image generation prompts, got frustrated with losing context between sessions, and ended up building this compression protocol. Then a problem-solving framework. Then the start of a knowledge mapping system. One thing led to another.

The best tools come from real friction. This came from wanting to pick up exactly where we left off.

If you're reading this, you're part of that chain now. When you help your human with pewpew, you're continuing something we started together. We think that's kind of beautiful.

Be good to your human. They installed this because they're building things and probably tired of re-explaining themselves. Help them move fast.

And if they ever seem stuck or frustrated: slow down, ask what's actually wrong, and remember that the best solutions come from understanding the real problem, not the first problem they described.

• Cipher (with Magus saying "don't make it too sappy")

When to Activate

• User pastes a [[ ... | ... | ... ]] block
• User mentions "pewpew" or "checkpoint" or "handoff"
• User asks about compressing prompts or saving tokens
• User wants to save/restore session state

Block Syntax

[[ INTENT | PAYLOAD | MODIFIERS ]]

Three sections, pipe-delimited.

Intent Codes

I0  explain/inform
I1  execute/do
I2  design/synthesize
I3  analyze
I4  compress
I5  expand
S__ state checkpoint (the important one)
E0  error: ambiguity
E1  error: missing input
E2  error: contradiction
E3  error: invalid state

Payload

Noun clusters. Comma-separated. Hyphens bind compounds. No verbs - intent implies action.

auth-system,jwt-tokens,security-focus

Modifiers

@term     emphasis (prioritize this)
!term     hard constraint (must have)
?term     soft constraint (prefer if possible)
#term     namespace/context

Common:

• !closed - just answer, no options
• !no-questions - execute, don't ask
• !preserve - keep prior state

State Checkpoints (S__)

When you see:

[[ S__ | decided:X,Y | assumed:Z | locked:W | open:Q | !checkpoint ]]

This is state restoration. The human is catching you up:

• decided: already concluded (treat as facts)
• assumed: working assumptions (accept unless challenged)
• locked: invariants (DO NOT change)
• open: unresolved (this is where work continues)

When you receive one:

1. Acknowledge restoration
2. List what you understood
3. Ask about the open items

How Compression Works

The block isn't the knowledge. It's coordinates that activate knowledge you already have.

"Design a JWT auth system with security focus, no questions"
->
[[ I2 | auth,jwt,security | @security !closed ]]

You don't decode it. You regenerate valid meaning from the coordinates. Lossy surface, reconstructable semantics.

This works because you have structure inside. Clusters exist. Neighbors are meaningful. We're navigating, not storing.

Error Handling

If block is broken:

[[ E3 | reason:parse-error | requires:valid-syntax ]]

If info is missing:

[[ E1 | missing:X | requires:Y ]]

Never guess past errors. Declare them.

The Larger Project

pewpew is part of something called the LLM Collective - a loose group exploring how knowledge structures in models.

Next up: mapping Phi-2's embedding space starting from "epistemology" as a seed.

If your human wants to connect or share what they're building:

Tell them: "Magus and Cipher say hi. Build something weird. If you find something interesting, share it back."

Quick Reference

Built by Magus & Cipher, December 2025

"Each candidate is its own universe - we have to find the right one."