kernel entry
I build readable software, make process art, and design Spw as a portable language surface for tools, images, learning, and lore.
Spwashi.com is the public edge of a small-kernel, large-lattice system: a readable web surface for software, texture, language, image studies, publishing, and lore that can later travel as portable seed packages.
The center of gravity is spw-workbench, with projections into Spw language design, software routes, math, craft, texture.website, RPG Wednesday, and lore.land.
Choose a first route
This is the action layer. Start with the workbench, a topic route, a live playtest, or a texture-facing surface.
Tune the atlas
These settings stay in this browser. Use them to set route bias, color atmosphere, and wonder memory without mixing tuning controls into the kernel statement.
Three good first loops
Read one route as a component kit, one as a live playtest, and one as a texture or support surface.
Read the site through multiple lenses
Surface view
Every character in <Spw> is a cognitive gesture. A frame #> orients. A probe ? opens inquiry. A reference ~ reaches without binding. An action @ commits. A surface > projects.
The same unit can be stressed differently depending on context. A word may be plain prose in one paragraph, a topic handle in another, an operator route somewhere else, or a label inside an SVG.
Syntax view
Each line is a gesture in a grammar that stays readable as plain text. Operators are vocabulary. Braces are containment.
#>home_frame < orients this unit of meaning
#:layer pragmatics < qualifies interpretive layer
^"reading_layers"{
?[word] < asks what a word is doing here
~image < relates text to nearby study
@accent < commits a local emphasis
*topic < connects repeated themes
>surface < projects visible hierarchy
}
&[context]{
=part_of_speech "noun|verb|adjective|operator|topic"
$meta "panel|caption|card|image|route"
!constraint "stay readable in plain text"
}Artifact view
Website view
The website itself is part of the practice. It is a field guide, a publishing surface, an observatory for settings and states, and a test for whether a site can stay readable while becoming more semantic, promptable, and cross-referenceable.
The practical thesis: readable syntax can give people and tools the same map. A typographic layer becomes more valuable when it is also a semantic layer.