#>home_frame

kernel entry

I'm Spwashi.

I build software and make art.

This version of the site is meant for revisiting, not only arriving. Use it when your priorities changed, when a neighboring route suddenly matters more, or when you need a smaller next step than the last visit gave you.

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.

Logo concepts Common Premium

~"returner_drift"

If you are returning, let the route change.

The center of gravity moves. Funding 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.

Build your way into college-level thinking through a playable library, guide characters, studio quests, garden prompts, and portfolio-ready artifacts.

Start a first quest

Make a route map, sealed object card, 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_proof

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.

$ open /now/

Create a Local Proof 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/

? "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.

* "wonder_rewards"

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.

~"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.

A corridor-like structural image with luminous paper seams, suitable for a component glossary or onboarding route.

#>component_glossary Design components A practical entry for collaborators who need the card, chip, slot, and runtime-state vocabulary before patching.

An energetic RPG Wednesday signal image with green and amber light, like a social playtest surface gathering momentum.

*rpg_wednesday RPG Wednesday A live play route where interface, prompts, memory, screenshots, and lore are tested under social pressure.

A warm library-like craft register image suggesting texture, study, publishing material, and sustained independent work.

>texture_surface Texture surface A style-contagion route for materials, patterns, promptable specimens, and reusable page feelings that can later travel as portable seeds.

#>promo_wonder_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.

JavaScript is off, so this section will stay on its embedded fallback copy. The page still points to a clear next step and a weekly question.

^"reading_layers"{

Read the site through multiple lenses

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.

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"
}

I'm Spwashi.

I build software and make art.