section
#>home_frame
kernel_entry

kernel entry

I'm Spwashi.

I build software and make art.

This site turns recurring practice into public artifacts: software notes, proof cards, study routes, visual systems, and reusable surfaces that can still read clearly in a screenshot, pitch, or live conversation.

On the software side, I care about languages and interfaces that model real situations: projects, stories, classrooms, and businesses under pressure before the costs get larger.

A good surface gives the reader a place to stand, a reason to return, and one handle they can tune back into frame.

Try this as a tunable reading surface: culinary reading, garden room, or runtime atlas.

  • cookbook
  • magazine
  • research
  • prompt
  • lore
Why home exists

To keep engineering, art direction, and story seeds in one durable frame instead of scattering them across drafts and apps.

Primary readers

Developers, artists, returning students, and working adults who need one practical route into a larger field.

Concrete things you can leave with

Route maps, proof cards, session seeds, screenshot-ready references, and reusable components that can travel into another project.

Current direction

A simple way to say it is: this site helps me practice through recipes, components, spells, study plans, and session notes, then share the ones worth reusing. The current metaphor is a cookbook with engineering notes in the margins. The test is whether a pattern can be read, reused, revised, and served to someone else without losing its source.

I want the site to work for adults still learning in the middle of ordinary life: parents keeping their minds warm, engineers who want theory without losing craft, and people who need humor, fantasy, and nourishment to stay connected to practice.

I think of the whole thing as a recursive editorial loop: make, inspect, reroute, repeat. The center of gravity is spw-workbench, with projections into Spw language design, software routes, author craft, math, tools, texture.website, RPG Wednesday, lore.land.

That is part of why I care so much about helping non-coders build intuition. CSS can describe constraints, spacing, overflow, and adaptation. Lower-level languages make memory, timing, and resource pressure easier to speak about plainly. A small set of rules can expand into many states, which is why software is also a good way to model stories, businesses, towns, and long-running projects before they harden into expensive habits.

One reason the website matters so much is stability. It lets me centralize digital structures instead of leaving the practice scattered across apps, feeds, drafts, and moods. If the structure holds, the learning can compound instead of resetting every week. RPG Wednesday has been developing for more than a year now, so the public pages can treat it as a recurring release surface: sessions, library cards, cast notes, and logs that keep accumulating usable canon.

The story seed is practical: a reader can enter through soup, wings, a component, a character, a CSS state, a research question, or a trade ingredient and still find the same underlying move. Stock becomes context. Reduction becomes compression. Sauce becomes byproduct recovery. Mise en place becomes dependency clarity. A session becomes a test kitchen for lore.

Culinary techniques are useful because they ask for inventory. If a page says bloom, temper, deglaze, ferment, fold, or reduce, it can also suggest a shopping list, a memory character, and a scene. A cook learns what to buy; a software engineer learns what operation is happening; an RPG table gets a mnemonic creature or ritual that makes the concept easier to recall.

I want the interface to feel less like a pile of controls and more like a marked-up field guide. Links should still navigate plainly. Buttons should still announce themselves to assistive technology. But the visible language can call them handles, lenses, provisions, route clues, spell marks, and pantry notes when that helps the page feel like a place someone can mosey through instead of operate.

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 still keep showing up because communication gets better by being used, and then used again. That matters here because the boonhonk idea is less a label than a disposition: a way to test how tone, force, and interactivity change when structure is allowed to recombine.

The site should feel learnable before it feels elaborate. A good surface gives a stable ground, then lets depth appear through repeated handles, visible state, and small changes in spacing, color, or copy. That is the practical meaning of resonance here: not sound, but a visual relationship that teaches the reader what changed and why it matters.

Touch interactions should be mindful. Hover, focus, tap, and settings can reveal relationships without stealing the page from the reader. Semantic resonance is there to help someone discover the same concept in another card, route, recipe, prompt, or lore fragment when they are ready to follow it.

Spwashi logo plate showing the Spwashi mark and wordmark in teal and gold on a warm paper field.
Logo concepts Common Premium
A wide teal and amber threshold scene with small glowing structures and a celebratory field-like atmosphere.
Occasion threshold A landing image for the holiday feeling without naming the holiday: a page can invite return, preparation, and shared practice before the next occasion arrives.
#>entrance_sorter

Choose your entrance

threshold

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.

For developers

Use About, Software, and the Website Field Guide when you need route structure, reusable components, or something that can become a prompt later.

For illustrators and painters

Use Play, Town Atlas, and Recipes when you need scene pressure, objects, surfaces, and material cues that can be drawn or staged.

For performers and RPG collaborators

Use RPG Wednesday, Sessions, Cast, and Library when you want readable memory, dialogue pressure, and a durable place for a table to become public.

A useful homepage should behave like mise en place for attention: the tools are visible, the work surface is clean enough to begin, and the next move does not require memorizing the whole pantry. The same page can also hold a story seed when the ingredients are named well enough for another person or model to expand.

I have a concrete request.

Open Services, Cards, Now, or Contact when the work needs to become an offer, a referral, a UX-flow test, or a direct ask. This path helps when the page should name the next move plainly instead of asking the reader to translate the whole atlas first.

@ services ^ cards

Why this card exists

This route gives a collaborator a direct way to ask for help without first learning the rest of the atlas.

It produces a live offer path, a proof surface, or a small next action that can be completed quickly and shared without extra framing.

I want to keep the cadence public.

Use the current sprint, membership, and proof cards when the task is to help the work move forward. This route connects to the work-in-progress state, the recurring release cadence, and the small actions that keep the system alive while the public can still follow along.

$ now #> membership

Why this card exists

This card helps when support is logistical rather than expressive.

It keeps coordination visible enough to share without turning it into a bigger task than it needs to be, which makes the cadence easier to trust.

I want to inspect the method.

Use About, Software, Settings, and the Website Field Guide when the goal is method, architecture, or inspection. This card helps when a route should explain itself before it asks for trust, and when the reading climate itself needs a visible control.

? about #> field guide

Why this card exists

This surface exists because a reusable medium should teach its own structure.

Developers and curious readers can use it to find the method before they commit to the whole site, and to see which parts are browser-local versus authored.

I need a smaller next move.

Use Care, Topics, and proof cards when the problem is not only knowledge but getting your footing back well enough to act. Return here after the immediate pressure has been named, because the next move should be small enough to finish and obvious enough to start.

! care * topics ^ cards

Why this card exists

This route exists for moments when the page should lower friction before it asks for a decision.

It can produce a steadier entry path, a topic neighbor, or a proof card that makes progress visible without adding ceremony.

I want neighboring routes.

Topics, Town Atlas, Blog, Play, Research, and Tools are the broader lattice when you want to learn sideways. This surface produces neighboring routes, not just more labels, so the next click can feel like a good adjacency instead of a random exit.

* topics #> town atlas ~ play ? research

Why this card exists

This is the exploratory route for when a visitor wants to move by relation instead of by category.

It helps the site remain a field guide rather than a single-path funnel, and it makes the adjacent routes legible enough to compare.

I want to tune the boonhonk register.

Use the boonhonk register when the question is how a system behaves once disposition, signal, and recombination are part of the interface. This is the route for playful-social generosity with enough structure to stay useful and noticeable.

* boonhonk register ~ rpg Wednesday

Why this card exists

This card exists to show that tone is part of system design here, not an afterthought.

It gives the site a way to surface wonder, recombination, and public play without losing the practical route or the reader’s footing.

^learning_loop

Use the site like a learning surface.

gateway

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.

What this loop protects

the site should help people learn something that survives the visit.

Best use

you need a visible loop from question to artifact to return path.

Leave with

proof cards, route maps, prompts, and recurring habits that make the site easier to revisit.

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.

#>reader_builder

Read the method or inspect the mechanism

paths

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.

A component is a small machine for arranging attention.

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. This path connects to lore, practical routes, and the material practice behind the pages.

? about #> website guide ^ town atlas . recipes

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. This surface helps the site feel like a system that can explain itself, not just render itself.

#> design = settings ^ software ? inspect query

~"returner_drift"

If you are returning, let the route change.

re-entry

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.

#>town_library

Enter the Town Library.

library

Build your way into college-level thinking through a playable library, session notes, 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, quest seed, or systems diagram in one sitting.

@ choose quest

Meet the guides

Use Grounding Rod, Cask, and Avalanche Evan as learning interfaces, not only character art.

~ guide cards

Practice the college bridge

Notice, name, build, document, connect, and extend before committing to a major label.

? wonder path

^local_record

A screenshot can explain intent.

record

It can be a local record of an ask, offer, agreement, reference point, or chosen disposition.

Fund the current sprint

See the active target, what it unlocks, and how someone can help in thirty seconds.

$ open /now/

Create a local record card

Make a screenshot-ready record for an ask, offer, pledge, reference, decision, or membership signal.

^ open /cards/

Join the working field

Choose an observer, reference, working, sponsor, or collaborator role without turning membership into a fan club.

#> open /membership/

Commission work

Use creator packages, business web work, consulting, or a direct support path to fund useful output.

@ open /services/

Privacy stays direct: drafts are not automatically public, screenshots should say why they exist, and shared records should expose only the context someone needs to act well.

? "operator_field"

Choose a first route

field

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.

* "wonder_rewards"

Thanks for wondering through the skills.

memory

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.

Learning game

Notice, name, fold, note, return.

  1. NoticeFind a word, ingredient, operator, prompt, scene, or interface behavior that makes you curious.
  2. NameUse the visible label, Spw sigil, or nearby copy to give the discovery a handle.
  3. FoldOpen the details, related route, or resonance peer that keeps the idea one handle away.
  4. NoteWrite the smallest useful question, recipe, sketch prompt, or genre move before the context evaporates.
  5. ReturnReset the page, change the climate, or revisit the route later to test whether the idea stayed legible.

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.

A reason to collect

Collection should mean “this helped me notice,” not “the page awarded a score.”

~"climate_tuning"

Tune the atlas

tuning

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.

Current state

Read the active environment

mode: auto pack: neutral paper palette: route memory: nearby

Resonance dimension

Choose a reading bias

Theme

Set light and material family

Wonder memory

Control resonance carry

Vocabulary discovery

Choose how loudly concepts answer back

Minimal keeps the page quiet. Field shows nearby relation cues. Rich turns vocabulary, prompts, ingredients, and Spw handles into a more collectible learning surface.

Runtime plumbing

Show why scripts are present

Turn on module visuals when you want rails, seams, and handles to say which scripts evaluate semantics, layout, state, visuals, routing, or interaction.

Show plumbing Skip crossrefs
#>"entry_loops"

Three good first loops

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

cycle

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

layers

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.