#>spw_operator_atlas
plain text operators brace physics alchemistry

Spw Reference Surface

Spw Operator Atlas

A sigil is useful when it changes what a reader knows how to do next.

Each operator is a small contract between text and tools. It tells a reader or runtime what kind of structure is present and how it can be inspected.

Operators are semantic actors; braces carry structural facts. The sigil tells you what kind of move is being made. The container tells you what kind of boundary or scope is being entered.

That makes Spw less like a secret code and more like compact notation for projection-based runtimes: nouns can hold variants, behaviors, and lenses; components can expose the same root under different display conditions; and familiar moves can recombine without every page explaining itself from zero.

Familiar root

The repeated word or sigil is the stable grip. It should remain readable in plain text, markup, and screenshot.

Typed distinction

Brackets, braces, and lenses clarify whether a difference is variant, behavior, scope, or interpretation.

Combinatoric genre

Reusable operators can produce cards, scenes, prompts, runtime handles, and visual motifs from the same semantic family.

Boonhonk can act like a combinatoric genre: a pantry of reusable moves where a familiar ingredient changes meaning through preparation, timing, pairing, and presentation. The grammar should let a reader notice the difference between a variant, a behavior, and a lens without needing a lecture every time.

This surface exists because

Sigils should stay learnable in plain text before they become interactive behavior.

Use this when

You need to inspect the semantic shape of a move, not only its visual token.

What it can produce

Operator literacy, route handles, promptable syntax, and reusable semantics for future public pages.

One reason languages like this matter is that they can train anticipation. A typed statement can be subvocalized and checked for shape before it runs. That same anticipation can spill outward into other literacies, including the more bodily ones around nutrition, chemistry, and weekly routine.

It can also spill back toward math. One structural clue I want to keep public on this site is that integration by parts can be read as a boundary-aware rewrite: the handoff becomes explicit, the residue stays visible, and the remaining work moves elsewhere. That is why the differential lambda calculus bridge belongs near the atlas.

#["operator_philosophy"]

Operator Philosophy

The atlas is not only an index of tokens. It is a claim about how readers, tools, and future interfaces should generalize what a semantic move means.

{ enter Opening edges should align a scope

An opening brace or frame edge should bias toward entry, alignment, and local orientation. It marks where attention gathers.

[ narrow ] Selections should clarify the working set

Square-bracketed structures narrow what is being addressed so a reader or tool can compare, quote, or inspect a smaller region.

( hold ) Grouping keeps relations nearby

Parenthetical forms hold a temporary relation together without claiming a stronger projection or commitment than the text has earned.

} close Closing edges should consolidate the block

A closing brace is where serialization, selection, or future projection can gather. It should feel like consolidation, not a dead ornament.

> project Projection manifests into another substrate

Projection is not a new source of truth. It is the same structure becoming visible in another room: page, panel, prompt, outline, or tool.

The public site should therefore translate plugin-shaped semantics into quieter interactions: enter the scope at the opening edge, inspect inside the body, and let the closing edge bias toward selection, serialization, or projection.

Orient

Use the atlas as a field guide

Inspect

Inspect tokens as semantic actors

  • Frame operator#> Naming a place is the first step toward shared human and machine navigation.
  • Object operator^ Objects show how structured material can stay inspectable inside readable text.
  • Probe operator? Inquiry operators are how a reader or tool asks more of the same source.

Commit

Separate action from projection

  • Action operator@ Actions are local commitments and should feel different from later manifestations.
  • Binding operator= Bindings pin names and categories so subsequent projections can stay faithful.
  • Pragma operator! Constraints and forces belong to the local runtime contract before they show up elsewhere.

Project

Follow the block into another room

  • Surface operator> This is the explicit projection move: the same structure rendered into another encounter.
  • Spw alchemistry>flow The alchemistry section shows how attention changes phase as it becomes stream or surface.
  • Website publishing register>site The public website is one projection surface where these operator contracts remain visible.

Operators are verbs for readers and tools

An operator should not behave like a cosmetic badge or arbitrary feature switch. It should announce an intent that both a human reader and a machine reader can understand: inquire, refer, bind, commit, project, compare, normalize.

Braces carry topology

The operator says what kind of act is occurring. The brace says what kind of container receives that act. That separation keeps the language extensible: the same semantic move can appear in different substrates without confusing action and boundary.

Generalization should follow intent groups

For menus and public interfaces, it is often better to group operators by reader intent than by raw token list: orient, inspect, commit, compose, and project. That keeps the language teachable without flattening away its semantic distinctions.

Projection is not the same as action

An action commits a local change. A surface projects a structure into another encounter. Keeping those separate matters because authors need to know when they are deciding something and when they are manifesting it for another substrate.

The atlas should stay compatible with the plugin

I mostly meet Spw through the VS Code plugin and local workspace. The website atlas should therefore act as a faithful public guide to the same semantics instead of inventing a prettier but incompatible vocabulary for readers.

Good semantics reduce fake interactivity

If a token implies selection, projection, or scope change, the interface should have a credible action for it. Otherwise the public surface should stay quieter. The language model should sharpen expectations, not disappoint them.

Nearby Context

Surfaces already in contact with the atlas

  • Software surface.surface The atlas is the smaller-scale grammar inside the broader readable-source argument.
  • Pretext lab.lab Experiments keep the atlas connected to authoring rather than drifting into pure abstraction.
  • Authoring seed.seed The seed shows how operator contracts can remain explicit inside one concrete block.

Subsequent Context

Where readers usually go after the thesis

  • Operator ring#ring Once the philosophy is clear, readers usually want the compact comparison map.
  • Action operator#action Separating local commitment from projection is one of the most important next distinctions.
  • Surface operator#surface Projection semantics become more intuitive once the explicit surface contract is read closely.

Projected Context

How these contracts leave the atlas

  • Website field guide>site The public site should teach the same semantics in a friendlier medium.
  • Spw workbench>plugin The plugin and local workspace are denser projections of the same operator and brace logic.
  • Blog surface>artifact Published fragments are where operator semantics prove they can survive outside a reference atlas.
~"voice_marker_palette"

Voice markers invite readers to try a stance.

Decorating language should not mean adding noise. A good marker gives the reader a small costume for attention: a way to read the sentence as question, artifact, spell, field note, rule, or scene.

# names the room

Use frame markers when a passage needs a place to stand: title, threshold, register, or route. The voice becomes more architectural.

? opens the aperture

Use probe markers when the reader should hold uncertainty instead of receiving a conclusion. The voice becomes curious, provisional, and generous.

~ keeps an echo nearby

Use reference markers for callbacks, memory, sources, and motifs. The voice becomes threaded rather than linear.

^ makes the phrase holdable

Use object markers when a phrase should feel like a card, talisman, specimen, or tool. The voice becomes more material.

@ asks for a move

Use action markers when language should become a ritual, instruction, edit, or invitation. The voice becomes more kinetic.

[] {} tune the costume

Use brackets for variants and braces for behavior: scene[comic]{soften}, note[field]{collect}, question[gentle]{return}.

#guide ?notice Field-guide voice

Starts by naming the habitat, then asks the reader to notice one thing. Useful when the page should teach without sounding like a lecture.

@cast ^token Spellbook voice

Turns a sentence into a small replayable outcome. Useful when the reader should leave with a phrase, gesture, or artifact.

~source {revise} Workshop voice

Keeps provenance visible while changing the material. Useful when the page should invite editing, comparison, and reuse.

The goal is not to make every sentence wear symbols. The goal is to develop taste: one marker can change the invitation, two can create a voice, and too many can turn the doorway back into a wall.

?["sentence_rhythm"]

Sentence variety is nutrition for attention.

A run-on sentence often means the writer has more energy than container. The goal is not to punish that energy. The goal is to give it more shapes, so the reader can breathe, follow, and still feel the momentum.

#simple Simple sentence

The door opened. Use this when the reader needs a clear beat, a fact, or a landing place.

&compound Compound sentence

The door opened, and the room remembered us. Use this when two equal forces need to stand side by side.

?because Complex sentence

Because the room remembered us, the door opened quietly. Use this when context should arrive before the action lands.

~delay Periodic sentence

After the dust settled, after the shelves stopped shaking, after every label turned forward, the door opened. Use this when suspense should gather before release.

^[list] List sentence

The room offered maps, jars, cards, keys, and one small bell. Use this when abundance matters, but the reader still needs order.

.beat Purposeful fragment

Then silence. Use this when the missing grammar is the point: shock, pause, afterimage, or emphasis.

~thread &return Braided sentence

The catalog wanted order, the children wanted dragons, and the librarian, who knew both needs were real, made a shelf for maps that could roar. Use this when several motives must stay visible.

{long} Long but controlled

A long sentence can work when each clause has a job, each turn changes the view, and the ending gives the reader a place to land.

This sampler exists because

newer writers often need more containers, not less imagination.

Use this when

a draft has energy but every idea is arriving in the same sentence shape.

What it can produce

a page, scene, or paragraph with clearer pacing and more available voices.

A useful revision move is to mark the job of each sentence before rewriting it: #land, ?open, ~return, @move, .pause. Then vary the shapes until the paragraph has a pulse.

$"structural_reduction_bridge"

Structural Reduction Bridge

Spw is not the differential lambda calculus. It still benefits from the same kind of discipline: name the boundary, keep the resource movement explicit, and do not mistake a cleaner surface for a vanished obligation.

Boundary-first reading

Good structure tells you where a block starts, what it depends on, and what residue survives after the local rewrite is finished.

anchor: operator philosophy

Why calculus belongs here

Integration by parts is a public example of the same structural move: expose the handoff, preserve the boundary term, and move the active differential burden.

route: calculus bridge

Why resource sensitivity matters

Projection is not duplication. Interfaces, caches, rankings, and human attention all behave more honestly once duplication and displacement are named as costs.

route: differential lambda calculus

Why teams care

When a system gets simplified, someone still needs language for what dependency moved, what boundary stayed, and what work the new interface still carries.

route: algorithm visualization
?[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.
Consideration: Operators > Schema > Alchemistry > Phase State
^"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. The root stays stable while the bracketed part changes the instance: brace[boundary] versus brace{transform}. 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. When the semantics are explicit, the page can jump between the same root in different modes instead of flattening them into one label.

$"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.