I need work or support.
Open Services, Cards, Now, or Contact when the goal is a commission, a referral, or a direct ask.
kernel entry
I'm Spwashi.
I build software and make art, then keep turning the process into tools, routes, proof, and whatever else survives contact with reality.
This site is for revisiting, not just arriving. Come here when you are trying to learn something, get your footing back, or find a next step that is playful enough to keep moving and concrete enough to keep.
Current direction
A simple way to say it is: this site helps me learn how I learn. Sharing the process is how I figure out what is only meaningful to me and what other people might care about-ish. The test is whether a private pattern can survive translation into a card, or a route, or a lesson, or a visual system, or a tool. If it can travel, it can teach. If it can teach, it usually earns another pass.
I think of the whole thing as a sharable recursive process for self-improvement. I make something, inspect it, notice the abstraction I was navigating, build a heuristic, reroute the result, and do it again. Make, inspect, reroute, repeat. Then again. 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.
One reason the website matters so much to me is stability. It lets me centralize digital structures instead of leaving the whole practice scattered across apps, feeds, drafts, and moods. If the structure holds, the learning can compound instead of resetting every week. There is less drift, and more carry, and more chance of returning to something before it goes flat.
A lot of this gets worked out in video. I do not treat speaking as a polished trait I either have or do not have. I treat it as practice. I stumble over words sometimes. I did not grow up on phonics. Could have enunciated that better. I am practicing. I still keep showing up because communication gets better by being used, and then used again.
Choose your entrance
Start with the role that matches what you want to do now. The rest of the site stays available, but the first screen should not ask you to classify yourself alone. Pick one need, not your entire identity.
I want to support or coordinate.
Use the current sprint, membership, and proof cards when the task is to help the work move forward.
I want to understand the system.
Use About, Software, and the Website Field Guide when the goal is method, architecture, or inspection.
I need a steadier next step.
Use Care, Topics, and proof cards when the problem is not only knowledge but getting your footing back well enough to act.
I am here to explore.
Topics, Town Atlas, Blog, Play, Research, and Tools are the broader lattice when you want to learn sideways.
Use the site like a learning surface.
Learning science is more useful here as a reading habit than as a slogan: start with one question, leave with one artifact, then revisit from a neighboring route.
1. Start with the smallest honest question.
Pick the route that matches your actual pressure now, not the most prestigious topic on the page.
2. Turn the visit into a visible artifact.
Make a card, note, screenshot, route map, or quest so the learning can survive mood drift and time passing.
3. Re-enter through a neighbor.
Use topics, play, care, or software to test whether the pattern transfers when the context changes.
Read the method or inspect the mechanism
Some visitors want the prose and canon. Others want the route model and runtime. Both get a first-class path, and both should leave with a smaller next move than they arrived with.
For readers
Start with About, the Website Field Guide, the Town Atlas, and Recipes when you want the site’s story, method, and reusable craft to stay close together.
For builders
Start with Design, Settings, Software, and the inspect query when you want the browser-local controls, CSS, and layout behavior to stay legible.
If you are returning, let the route change.
The center of gravity moves. Learning weeks, research weeks, playtest weeks, and publishing weeks should not all ask you to enter through the same door.
Changed center
Follow whatever has pressure now.
Some visits are about support, some about proof, some about learning, and some about finding a route you ignored the first time because it was not ripe yet.
Reasons to re-enter
Change is welcome.
Use a different route than last time on purpose. The atlas is healthier when it supports drift.
Wonder needs neighbors.
Software should be close to math, craft, care, and play so the questions can mutate.
Proof beats vague intention.
When a thought matters, turn it into a page, card, quest, prompt, or small spell someone else can point at and replay.
Fresh entry
Pick the route that makes your next question stranger and smaller.
That might be topics if you need a map, cards if you need a proof surface, or the blog if you need to watch fragments turn into public form.
Enter the Town Library.
Build your way into college-level thinking through a playable library, guide characters, studio quests, garden prompts, and portfolio-ready artifacts.
For the story substrate itself, move to the Town Atlas. That keeps the practical library and the world bible separate enough for humans and models to review without guessing which page is doing which job.
Start a first quest
Make a route map, sealed object card, or systems diagram in one sitting.
Meet the guides
Use Grounding Rod, Cask, and Avalanche Evan as learning interfaces, not only character art.
Practice the college bridge
Notice, name, build, document, connect, and extend before committing to a major label.
A screenshot can be more than content.
It can be a local record of an ask, offer, agreement, or reference point.
Fund the current sprint
See the active target, what it unlocks, and how someone can help in thirty seconds.
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.
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.
Thanks for wondering through the skills.
A skill surface should give something back for the attention it asks of you: a clearer question, a usable pattern, a replayable spell, or a next move you can actually take.
Gratitude
Thanks for staying with the strange routes long enough to find a handle.
Wonder is useful here because it keeps software, art, care, and play from sealing themselves off too early.
Rewards
A smaller next step
A route, card, or tool that makes the work feel startable.
A cross-link worth testing
A neighboring skill surface to borrow from before the thought stiffens.
A replayable spell
A screenshot, prompt packet, card, or route sequence you can run again under different conditions.
Take it sideways
Turn the wondering into movement.
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.
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.
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.