Overview
SKYVIEWER is an internal explorer that runs inside the generator layer known as SKYGEN. It lets operators walk layers and flag anomalies without exporting or patching. This page explains the viewer, hotkeys, PID tags, LINK and LOCATE, the BLUEN intake rig, and ANATOMY tower handling.
Controls & Hotkeys
U internal wireframe
Opens a wireframe grid view of the generator internals. Shows the current layer surface and nearby constructs as edges and nodes. Use it to spot overlaps and stray entities.
L link
Binds the nearest eligible entity to your session for observation. The viewer mirrors state, stress, and the entity PID. The link is read only and can be released at any time.
P pid overlay
Toggles a small overlay with the entity PID next to its marker. PID means PlayerID. Entities are trained on player behaviour traces; the PID identifies which trace family shaped the agent.
O locate
Helps you see linked and nearby entities by fading clutter. The viewer applies temporary transparency to non-essential parts while keeping navigation surfaces solid.
When LINK is blocked
- Entity is already linked to another operator
- Entity shows destabilization (looping edits, hostile seeks)
- Layer policy requires diversion to ANATOMY
SKYVIEWER
In scope
- List and enter layers: Color, Bug, Red, Gall, Fritz, Gen
- Tag anomalies with reason and severity
- Show nearby agents, PID, and link status
- Route to safe training instances when a seed is provided
Out of scope
- Teaching or overwriting agent behaviour
- Bypassing containment or patching core memory
- Direct edits inside Gen layer
BLUEN Rig
BLUEN is the intake rig positioned before ANATOMY. It filters inbound agents and checks for signs of user modification or distress. If flagged, BLUEN diverts the agent to intake instead of allowing entry to live memory.
- Signal lights show pass, review, or divert
- On divert, the viewer marks the agent as protected and disables new links
ANATOMY Tower
What happens
- The agent is isolated from live memory
- State is quantumised into a bounded orb record
- The orb orbits the tower at low energy for sampling
- Operators receive an Orb ID for follow-up
Restore path
- Compare the orb with a baseline archetype
- If stable, rehydrate in a training layer first
- Do not restore directly into Gen
Quick Reference
- Open internal wireframe U
- Link nearest entity L, show PID with P
- Use locate to reduce clutter O
- BLUEN divert blocks links and starts intake
- Intake stores the agent as an orb for safe study and potential restore