Spw Operator Atlas

Each operator is a small contract between the text and the tools around it. It tells a reader, runtime, LSP client, or future component what kind of structure is present and how it can be inspected.

?[operator_ring]

Operator Ring

Use the ring as a compact comparison view. Every card gives you the token, the intent, and a route into the deeper operator page.

#> Frame Name a unit so attention has a stable place to land. #: Layer Say what kind of interpretation the frame needs. .baseline Baseline Return to the local default or settled lens. ^object Object Hold material in an inspectable structure. ~ref Reference Point to a relation without forcing a change. ?probe Probe Ask, filter, or reveal an inquiry. @action Action Turn intention into a local change. *stream Stream Connect structure to event-like flow. &merge Merge Overlay fields so comparison can stay visible. =binding Binding Name, pin, or categorize a local value. $meta Meta Reflect on the medium, state, or trace. %normalize Normalize Scale salience into a comparable form. !pragma Pragma Apply a force, constraint, or runtime hint. >surface Surface Project structure into a rendered encounter.

^"spw_alchemistry"{

Spw Alchemistry

Transformation Model

Alchemistry is the transformation model for attention. Curiosity becomes a probe, relation becomes a reference, intention becomes action, action becomes stream, and structure becomes a surface only when the change remains inspectable.

Brace Physics

A brace marks a boundary where attention can gather. That energy may guide the next projection, but it should never hide alternatives or make an unavailable click feel broken.

Prefix / Postfix

A prefix operator prepares how the next structure should be read. A postfix operator marks what the structure leaves behind after contact. They mirror each other without having the same timing.

Future UI Surface

These pages are static first. Later, Spw blocks and scripts can use the same operator contracts to become widgets, inspect panels, spell boards, or LSP-backed navigation.

$"authoring_seed"

Authoring Seed

#>spw_operator_page
#:surface #!reference

^"operator"{
 token: "*"
 intent: "flow"
 interaction: "connect to dynamic or event-like content"
 metaphysics: "attention becomes a current"
 brace_physics: "stored charge biases the next projection toward motion"
}

?["What should tapping this operator reveal?"]{
 fallback: "show the inspectable contract before any runtime action"
}

The atlas starts as HTML, but the repeated structure is already shaped like something an authored Spw block could generate.