spw.quest

A language for navigating the metamaterial properties of linguistics

A notation for readings you can compare.

#>reading[compare]{shared}(shelf)<notation>
#>reading[compare]{parted}(shelf)<notation>

A mark says what a word is doing. A brace says which slot it fills. Change one slot and the reading updates. Explore lines as discrete monospace stamps here, or project their continuous topological forces on factshift.center.

Handed this address and a line? How to answer in Spw.

Start from a line

Each line below is a question to ask in one reply, a turn that keeps a longer conversation going, and a seed for a file. Change any slot to make it yours.

Marketing

launch[soft]{waitlist, story, proof}<audience>

Ask Which of the three would you cut first?

Talk Change soft to loud and say what each part has to become.

Build One line per launch you have run, so the next one starts from them.

Change a slot · Open Review voice · Canvas ↗

Growth

funnel[weekly]{visit ~> signup ~> paid}<cohort>

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.

Change a slot · Open Data pipeline · Canvas ↗

Frontend

page[slow]{bundle, images, fonts}<phone>

Ask Which of these would you measure first?

Talk Change phone to desk, and say what drops off the list.

Build A record of each fix: the metric, the diff, and the test run.

Change a slot · Open Engineering records · Canvas ↗

Finding talent

role[frontend]{react, a11y, design}<team>

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.

Change a slot · Open Role card · Canvas ↗

Incident triage

outage[p1]{triage ~> isolate ~> verify}<checkout>

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.

Change a slot · Open Incident review · Canvas ↗

Organizing a gathering

gathering[monthly]{host, access, food}<neighbors>

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.

Change a slot · Open Potluck & access · Canvas ↗

Your walk, in Spw

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

Still open: learn build forms

Read it line by line
  • #> 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.

Open in Build Canvas

38 files, written in Spw: a bench, a study, a board, a stage, a trial for the canvas, a team's files, and field practice

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.

lab-notebook.spw

Canvas ↗ Parser ↗

A dated work log tagged by what happened: catalog something noticed, try an alternative, measure what changed, and land the fix.

In hand line 1 of 11

Open it on the canvas ↗

Try Add a line inside the braces: >>[2026-11-07 10:00] catalog — the card, in two dialects: lifted and flat

Marks and braces#

Twelve marks, each with what it does in a sentence and a line it might start. The name is the workbench's. The runtime line is what the reader does with the mark today, and the numbers open the Learn panel that uses it.

  • potential ~

    Keeps options open. Use it for what is still being explored.

    ~launch{email, waitlist, beta}

    Runtime: Defers operand evaluation as a thunk, retaining the unreduced search space until demanded by an observer.

    2 act 5 point

    in lab-notebook.spw ×2

  • wonder ?

    Asks a question that evidence can settle.

    ?churn[q3]{pricing, onboarding}

    Runtime: Dispatches a conditional predicate, evaluating the contingent branch once the interrogative precondition holds.

    2 act 6 ask

  • action !

    Does something, so you can see what changed.

    !ship{pricing_page}

    Runtime: Forces eager evaluation of its operand, committing the state transformation and returning the actualized value.

    2 act 6 ask

  • value *

    Marks what matters most.

    *metric{activation}

    Runtime: Evaluates the operand to canonical normal form, recording the stabilized invariant into an addressable register.

  • ground .

    Names the defaults everyone already assumes.

    .brand{voice, colors}

    Runtime: Traverses a qualified property path or dereferences the scoped baseline context from the active lexical environment.

  • ascension ^

    Gathers parts into a whole you can inspect.

    ^funnel{visit, signup, paid}

    Runtime: Encapsulates operands into an integrated compound record bounded by unified relational type constraints.

    in lab-notebook.spw ×1

  • vibration #

    Gives something a name, so it can be found and linked.

    #>q3_launch

    Runtime: Reduces the structural payload into an addressable register entry registered within the global symbol table.

    4 name

    in lab-notebook.spw ×4

  • perspective @

    Says from where you are looking.

    recruiter@role[frontend]{react}

    Runtime: Projects the operand through a situated observer lens, evaluating expressions relative to that vantage frame.

    5 point

    in lab-notebook.spw ×2

  • subject &

    Holds several things to one topic.

    &hiring{role, budget, timeline}

    Runtime: Performs associative unification across arguments, merging congruent predicates into the primary subject register.

  • configuration =

    Fixes a setting the rest depends on.

    =stack{react, vite}

    Runtime: Binds an identifier to an evaluated value within the active register bank, governing downstream parameterization.

    4 name

  • measure %

    Measures, so before and after can be compared.

    %conversion{before ~> after}

    Runtime: Applies a metric evaluation function across focused registers, computing scalar distance, ratio, or cardinality.

  • substrate $

    Names what something runs on: time, money, machines.

    $runway{months, team}

    Runtime: Materializes underlying runtime metadata, exposing memory layout, latency bounds, and platform resource footprints.

  • <> concept Ontological boundary: encapsulates the semantic universe of discourse and categorical domain.
  • () scene Situational context: situates the spatiotemporal setting, environmental locus, and pragmatic frame.
  • [] mode Modal aspect: specifies the grammatical register, epistemic modality, and operational variant. 3 hold 6 ask
  • {} definition Constituent enclosure: encapsulates compositional definitions, internal clauses, and structural relations. 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.

Tools#

Take one line apart

Edit one slot. The reading updates.

!draft<chapter>(study)[second_pass]{voice, scene, turn}

About#

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.

The fuller statement is what Spw should let you say.

Recipe for agents · quest.json · Source · What was hard to follow