New to Spw
Seven one-line storyboard panels starting from plain prose — no jargon required.
Spw · readable marks and containers for people, editors, and tools
editor@cut{rough ~> fine ~> locked}(deadline)<reel>
?["what broke the pacing?"]{ !probe{ "watch scene 3 muted" } }
A mark says how you stand toward a word. A container bounds what belongs inside — in any order, nested, or alone. Click any colored mark or brace to trace it across the page, or project lines onto a spatial canvas at factshift.center.
Seven one-line storyboard panels starting from plain prose — no jargon required.
Take a line apart, compare forms side by side, or mount .spw/_workbench.
For language models and agents: the plain-text grammar, worked answers, full corpus, and repo setup.
Each line uses a different Spw shape — a prefix mark, a persona perspective, a scene first, or a transition path. Click any colored mark or brace to highlight matching expressions and inspect its role, or copy a line straight into your notes.
Ask Which of the three would you cut first?
Talk Change ~ to ! and soft to loud — say what each part has to become.
Build One line per launch you have run, so the next one starts from them.
Ask What breaks the pacing between rough and locked?
Talk Change rough to fine and add the one cue that holds the cut together.
Build A scene sheet keeping cut stage, pacing notes, and sound cues together.
Ask Where does this funnel leak most?
Talk Add a step between signup and paid, and say what it measures.
Build A pipeline that counts each step by cohort, week over week.
Ask Which of these would you measure first?
Talk Change bane to boon and slow to crisp — say what made the difference.
Build A record of each fix: the metric, the diff, and the test run.
Ask Which skill is this role really asking for?
Talk Write the same role at junior and at senior, and say which parts move.
Build A role card per person, pointing to the snippets they kept.
Ask Which of the three would you trade first?
Talk Add a fourth part, and say what it costs the other three.
Build One line per company you talk to, compared two at a time.
Ask Which signal tells you the blast radius stopped growing?
Talk Turn p1 to drill and add the exact smoke check you would automate.
Build A blameless postmortem keeping latency bounds, owners, and timeline together.
Ask Who cannot participate if one default assumption stays unspoken?
Talk Change monthly to weekly and trim setup so one host can close in 15 minutes.
Build A lightweight charter naming access promises, shared roles, and cleanup steps.
This file writes itself as you open rooms here, in the marks this guide teaches. It stays in this browser; nothing is sent. With scripts off it shows where a walk begins.
#>walk
you@guide
~learn ~build ~forms
#> names it, so it can be found again.@ sets a perspective: the context before it, the subject after it. Here, you, at the guide.~ keeps a path open without taking it: rooms not opened yet.Each works as it stands and is yours to change: edit it here, keep it as your note, or download it. On the stage, a pattern that performs sets this field's theme. Where one file points to another, its reading opens that file at the line it names.
Twelve marks organized as six dimensional symmetry pairs — each with its spatial axis, elemental valence, partner, and a live specimen line you can copy, edit, or open on factshift.center. Click Find on page on any card (or click any colored mark inside an expression) to trace where it appears.
potential ~
Holds an uncollapsed path across distance without taking it yet; sits opposite @ perspective, which names who is looking down that thread.
Runtime: Defers operand evaluation as a thunk, retaining the unreduced search space until demanded by an observer.
wonder ?
Opens an inquiry or conditional gate without forcing closure; balances ! action, which collapses possibility into an observable move.
Runtime: Dispatches a conditional predicate, evaluating the contingent branch once the interrogative precondition holds.
action !
Commits a state change so its consequence becomes observable; completes ? wonder by crossing from inquiry into effect.
Runtime: Forces eager evaluation of its operand, committing the state transformation and returning the actualized value.
value *
Materializes what carries concrete worth or salience here; pairs with $ substrate, which names the physical cost or ground carrying it.
Runtime: Evaluates the operand to canonical normal form, recording the stabilized invariant into an addressable register.
ground .
Settles attention back to the local default or center of gravity; anchors # vibration, which projects an address outward so others can find it.
Runtime: Traverses a qualified property path or dereferences the scoped baseline context from the active lexical environment.
ascension ^
Lifts separate parts onto a higher register as one inspectable whole; complements & subject, which binds parallel streams laterally.
Runtime: Encapsulates operands into an integrated compound record bounded by unified relational type constraints.
vibration #
Calls a structure by resonant name (#>, #:, #!) so tools and readers can address or echo it across files; balances . ground.
Runtime: Reduces the structural payload into an addressable register entry registered within the global symbol table.
perspective @
Situates the coordinate origin — who or what is looking (Persona@subject, @alias) — giving ~ potential a vantage point to aim from.
Runtime: Projects the operand through a situated observer lens, evaluating expressions relative to that vantage frame.
subject &
Binds multiple streams or constraints onto one shared focus without flattening them; pairs laterally with ^ ascension's vertical lift.
Runtime: Performs associative unification across arguments, merging congruent predicates into the primary subject register.
configuration =
Pins a local parameter or invariant that downstream structure depends on; establishes the fixed reference point that % measure scales against.
Runtime: Binds an identifier to an evaluated value within the active register bank, governing downstream parameterization.
measure %
Compares, weights, or normalizes before and after across a coordinate axis; reads the tension relative to = configuration.
Runtime: Applies a metric evaluation function across focused registers, computing scalar distance, ratio, or cardinality.
substrate $
Exposes the physical, temporal, or computational medium carrying the work — time, budget, memory, storage, attention; underpins * value.
Runtime: Materializes underlying runtime metadata, exposing memory layout, latency bounds, and platform resource footprints.
<>
concept (Domain / channel) Names the kind of thing, outward channel, or domain boundary — can wrap a concept on its own or project outward beside other containers.
()
scene (Space-time witness) Stages where or when the line happens — before a word, after a body, or alone as an observable midprocess moment.
[]
mode (Lens / schema key) Selects a stance, variant, or schema coordinate while leaving sibling options visible.
3 hold 6 ask
{}
definition (Interior topology) Bounds what lives inside (opening { leans objective, closing } leans subjective): commas hold company, semicolons order stages, ~> relays a path, or nested containers sit inside.
3 hold 6 ask
Forms, side by side: each brace, join and mark against its neighbors. Marks and braces compose: #[…] is a set, .{…} a property sheet.
Compare lines that differ in one slot.
Edit one slot. The reading updates.
!draft<chapter>(study)[second_pass]{voice, scene, turn}
Seven panels. Each panel is one line.
Spatial canvas: lay any Spw line or script out as movable connected nodes.
Install the guide. It opens in its own window.
Parser, CLI, and editor tooling at .spw/_workbench.
Dated parser builds. Each build has an integrity hash.
Spw started while I was exploring factshift, before it became factshift.com and then factshift.center.
It was first meant as a tagging system for pivoting across higher dimensions. Then I learned more about cognition and epistemology. Now Spw is a language for navigating the metamaterial properties of linguistics.
In practice, a mark says what a word is doing and a brace says which slot it fills. Hold two readings on the shelf and name the slot where they part, or change one slot in the editor. Joins stay distinct, so a comparison can say which relation moved.
. A dot makes one name., A comma holds a company.; A semicolon keeps an order.~> A path.The fuller statement is what Spw should let you say.
Release is published. This page keeps reader.min.js of 2026.10.13. Read the guide with the published release; that loads the release's full build and does not change what this page keeps.
Recipe for agents · quest.json · Source · What was hard to follow