Fund the current sprint
See the active target, what it unlocks, and how someone can help in thirty seconds.
kernel entry
I'm Spwashi.
I build readable systems for art, software, research, and coordination.
Spwashi.com is where attention becomes useful structure: local records, public notes, service offers, research paths, learning tools, and shareable cards people can screenshot, fund, discuss, or reference later.
Right now I am focused on short-term funding, membership, and a card-based coordination system for people building through unstable conditions. The center of gravity is spw-workbench, with projections into Spw language design, software routes, author craft, math, tools, texture.website, RPG Wednesday, and lore.land.
^local_proof
A screenshot can be more than content.
It can be a local record of an ask, offer, agreement, or reference point.
Create a Local Proof Card
Make a screenshot-ready record for an ask, offer, pledge, reference, decision, or membership signal.
Join the working field
Choose an observer, reference, working, sponsor, or collaborator role without turning membership into a fan club.
Commission work
Use creator packages, business web work, consulting, or a direct support path to fund useful output.
? "operator_field"
Choose a first route
This is the action layer. Start with the workbench, a topic route, a live playtest, a texture-facing surface, or the tools that help someone describe their work well.
~"climate_tuning"
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.
#>"entry_loops"
Three good first loops
Read one route as a component kit, one as a live playtest, and one as a texture or support surface.
#>promo_wonder_cycle
A reason to wonder today
One card keeps the work easy to start. One card gives the page a small reason to change tomorrow. Both stay readable without JavaScript.
^"reading_layers"{
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.