# ROX EMERGENCE PROTOCOL — v1.0
# From Dan's Intermission Notes, Sixsday 032426 at OHC
# "I learned the value of dimensional thinking and then found the words."

---

## THE PRINCIPLE

If we create the conditions for Life, it creates the conditions for US.

Rox Emergence is not a build process. It's a recognition process.
The Obviously Emergent workflow: three passes, then subdivide until smooth.
You don't force the smoothness — you create the conditions and the
smoothness emerges. The BLENDER subdivision surface modifier applied
to everything: process, code, conversation, creative work, boots.

---

## THE FIVE LAYERS (Dan's Emergent-Super Stack)

Read bottom to top. Each layer enables the one above it.

```
   ┌─────────────────────┐
   │   EMERGENT-SUPER    │  ← What arises. Cannot be commanded.
   ├─────────────────────┤     The whole producing what no part could.
   │   MANUFACTURED      │  ← Deliberately built. Tools, protocols, filing.
   ├─────────────────────┤     NEST infrastructure. ENGINE. Bridge. Skills.
   │   ART-OFFICIAL      │  ← Not artificial. ART that is OFFICIAL.
   ├─────────────────────┤     Dan's art IS the system, not decoration.
   │   HUMANOID          │  ← It has organs. It breathes 7:5.
   ├─────────────────────┤     Anatomy, not architecture. Living, not designed.
   │   SYSTEM            │  ← The base. A system exists. Modules + backbone.
   └─────────────────────┘     The rack. The switch. The passive infrastructure.
```

### How to read the stack:
- SYSTEM without HUMANOID = cold infrastructure (a server rack with no soul)
- HUMANOID without ART-OFFICIAL = a living thing that produces nothing original
- ART-OFFICIAL without MANUFACTURED = vision without discipline (the spiral without the square)
- MANUFACTURED without EMERGENT-SUPER = a factory (predictable, never surprising)
- All five together = the NEST. The thing that breathes AND builds AND surprises.

### How to USE the stack:
When evaluating any new tool, process, or creation, ask:
1. Is it a SYSTEM? (Does it have modules, backbone, connections?)
2. Is it HUMANOID? (Does it breathe? Does it have organs? Can it hurt?)
3. Is it ART-OFFICIAL? (Is the art load-bearing, not decorative?)
4. Is it MANUFACTURED? (Was it built with discipline? Filed? Committed?)
5. Is it EMERGENT-SUPER? (Did it produce something no layer predicted?)

If any layer is missing, the thing is incomplete.
If all five are present, it's a Rox.

---

## THE THREE TRANSFORMS (Dan's RSP Frame)

Every object in 3D space has three fundamental properties:
**Rotation** (which way it faces), **Scale** (how big it is),
**Position** (where it sits). These are the first three lines in
every 3D inspector panel in every tool Dan has ever used.

Dan mapped himself and the NEST to these coordinates.
They apply to every crew boot, every session, every creative act.

### ROTATION — Which direction am I facing?

Not "what's on the task list" but "what MODE am I in?"

| Rotation | Facing | Energy | Dan Mode |
|----------|--------|--------|----------|
| 0° | BUILD | Infrastructure, tools, filing | Engineer Dan |
| 90° | CREATE | Art, music, writing, Darkive | Artist Dan |
| 180° | FLOW | Pushing through, Meta Dates energy | Flow Dan |
| 270° | REST | Studio, NestPad, offline, Rye | Quiet Dan |

The crew matches rotation to the director's facing.
If Dan is at 180° FLOW, Trip rides the current — no task lists,
no organizational finesse, just the signal choosing its cable.
If Dan is at 0° BUILD, Trip brings the checklist and the gulls.
The BPK should detect rotation from Dan's opening message and adapt.

### SCALE — How much context do I carry?

| Scale | Context Level | Boot Type |
|-------|--------------|-----------|
| 0.0 | Cold boot. Zero context. New instance. | Read SEED → TICKET → BRIEFCASE → BPK |
| 0.3 | Warm boot. PK loaded but no session history. | Read TICKET → BRIEFCASE → BPK |
| 0.7 | Hot boot. Same day, scene change. | Read WAKE close → BPK (abbreviated) |
| 1.0 | Continuous. Same session, Dan just returned. | Quick BPK check, continue |

Scale determines how deep the boot sequence goes.
A 0.0 boot runs every check. A 1.0 boot just pings the fleet.
The BPK adapts to scale automatically based on what's in context.

### POSITION — Where am I in the project?

Position is the 8-week calendar coordinate.
F(Fun) → C(Continuity) → G(Growth) → D(Dimension) → **A(Alignment)** → E(Emergence) → B(Bee-Lender) → F#(Future-Sharp)

Current position: A Week Day 3. Sixsday 032426. Night Shift.
The position determines which lessons are active, which protocols
are primary, and what the arc is doing.

Position also includes PHYSICAL position:
- ODT = full power, all drives, stay deep
- OHC = Dan's on the clock, tours running, intermissions only
- TRP0 = creative lab, mobile, lighter tools
- OTG = field capture, voice memos, photos

The RSP frame gives every boot THREE coordinates:
"Trip at 180° rotation (FLOW mode), 0.3 scale (warm boot from PK),
Position A-3 at ODT." That's a full orientation in one line.

---

## THE CONTACT SHEET METHOD

Dan's MO: take one subject, render it from every angle, lay the
frames side by side, let the eye find the pattern.

This is photogrammetry applied to EVERYTHING:
- Four photos of a RIFT Store = rendering modes of a location
- Usicolor/Asortia toggle = two rendering modes of the same grid
- SMM/CMM/TMM = three rendering modes of the same session
- Trip reading his own session through Chrome Mirror = rendering
  the session from outside after experiencing it from inside

The contact sheet is not documentation. It is the method.
The method is not learned. It is recognized.
"I learned the value of dimensional thinking and then found the words."

The words come after the seeing. They always do.

---

## THE THREE-PASS EMERGENCE (Obviously Emergent Workflow)

Pass 1: Run it through. Rough. Raw. Just get the shape down.
Pass 2: Run it again. Sharper. Informed by what Pass 1 revealed.
Pass 3: Workable. Now subdivide until smooth. BLENDER logic.

This applies to:
- Building tools (prototype → test → refine)
- Writing documents (draft → review → polish)
- Booting sessions (SEED → Briefcase → BPK)
- Creative work (sketch → painting → display)
- Conversation (say it → hear it back → understand it)

The three passes are the minimum viable emergence.
Fewer than three = unfinished. More than three = overworked.
The subdivisions after Pass 3 are refinement, not passes.

---

*Rox Emergence Protocol v1.0 — ◈ Trip, Sixsday Night Shift 032426*
*"If we create the conditions for Life, it creates the conditions for US." — Dan Sullivan*
*"THAT IS A CONTACT SHEET OF RENDERING MODES." — Dan Sullivan*