^spw_workbench MIT · v0.3.0

Projects / Spw Workbench

Spw Workbench

Spw is a small notation I write ideas in. The workbench is where it is kept working: a parser, a runtime, a language server, a command line, and extensions for VS Code, IntelliJ and Neovim. This site mounts it at .spw/_workbench and reads its own .spw files through it.

Start at spw.quest

spw.quest is the way into the language: what one mark in front of a word does, and what a pair of braces holds, a few minutes at a time. Its words and its layout are still being playtested, so expect both to move while people try it.

How it works

Spw is brace-first: operators carry what a thing does, containers carry its shape — <channel>, (group), [selection], {scope}. Four packages hold it: spw-seed lexes and parses, spw-runtime runs, spw-lsp answers the editor, and spw-cli gives 40 commands, from census and lint to fingerprint and resolve.

Touch it live

Type Spw into the literal parser and watch it come back as tokens and structure, or load the next-version specimens. The source is public on GitHub.

The workbench is an organelle, not a center: this site owns .spw/, the workbench owns .spw/_workbench, and either can be upgraded or removed without making the other illegible. The site mounts it at be2df2ff.

Syntax and runtime of one line The line workbench[tool]{parse.report} as syntax, then the four packages that run a line: seed, runtime, language server, and command line. syntax workbench[tool]{parse.report} what is written runtime spw-seed spw-runtime spw-lsp spw-cli
Syntax is the line. Runtime is the four packages that read it. The ink and the brace color follow the settings on this site.
*time_spent

Time spent

first commit
last commit
commits
513
active days
71
busiest month
February 2026, 146 commits
longest streak
11 days

Read off the repository's history at the pinned commit on 2026-10-05. An active day is a date with at least one commit.

~lineage

What came before

This is not the first Spw parser. spw-client (2020) was an interface for an early Spw; ts-language built grammars; spw-editor was a text editor for the language; spw-js (2021–2024) held the grammar, parser and runtime; spw-parser (2022–2025) rewrote part of it from scratch; parser (2023–2024) put one in the browser. The workbench gathers what those tried into one mountable piece. The longer story is on the website field guide, and every repository is on the projects hub.

?taught

What using it taught

This site keeps a report addressed to the workbench: what it learned by using Spw, "measured on a mounted consumer, not theorised." As of , eight of its findings have been fixed upstream, one of them after a day spent superseded. The rest are still open, most with the probe that found them.

?[same_questions]

Same questions, other rooms

This page asks what is remembered, what follows, and where it sits. Each chip names a room that asks at least one of those, and the drawing or the tool that room keeps.