The sentences name what you might notice. The page then helps that notice travel: matching handles echo, glass and matte stay in their jobs, and the Midjourney renders keep one world across a folio, a card, and a session. Topics names the rooms. Settings names the variables.
home page entry
I'm Spwashi.
I build software and make art.
A folio, a proof card, a craft route, a Spw handle, math, recipes, play, the design lab, search, and the depiction bench.
If you already know the pressure, pick that room. Some people read. Some people scroll the rooms and work the components. Topics sorts the rest. Now is open this week.
Last night’s public prompts are on Now. Recipes is this week’s produce. RPG Wednesday is the table.
Choose a working view
Reweights related cards across this page; every route stays available.
.reading: Personal study routes, creator records, and craft traditions worth revisiting.
Holds: craft notes, essays, culinary theory, and design records. First move: <author_craft> or browse *field_dispatches.
^systems: Plain-text Spw grammar, compiler passes, and interactive workbench specimens.
Holds: syntax proofs, deterministic projections, and AST traversals. First move: #>operator_atlas or test ~software_parsers.
~play: RPG Wednesday weekly sessions, character sheets, and collaborative world lore.
Holds: session logs, table rulings, cast notes, and shared dice consequences. First move: *rpg_wednesday or visit #>town_library.
@studio: Systems, commissions, and public proofs.
Holds: service lanes, proof ledgers, and a visual world that stays coherent. First move: @studio_services or check !current_work.
- cookbook
- magazine
- research
- prompt
- lore
Business-minded, software-adjacent supporters of the arts — producers, commissioners, working engineers, and patrons who want the handles to mean something and the pictures to stay in one world. About is context. Services is a conversation.
A feel for how Spw behaves, a current map of the work, and a visual canon you can carry: proof cards, folio studies, prompt packets from the depiction bench, session traces from RPG Wednesday.
Example: hold any living term on this page to prime it as a working handle. Matching operators on the page should echo that hold.
Pick your door
Name the pressure you are under right now. Pick one door — not your whole identity.
-
For software-adjacent supporters of the arts
Notice how a handle behaves, which projects are live, and whether the renders hold a world together.
-
For developers
Route structure, reusable components, and prompts you can extract later.
-
For illustrators and painters
Scene pressure, material cues, and surfaces you can draw or stage.
-
For performers and RPG collaborators
Readable memory, dialogue pressure, and a table whose sessions leave traces without forcing one public voice.
Open the deeper atlas Resonance practice, image routes, and component paths.
A useful homepage is mise en place for attention: tools visible, surface clear enough to begin, next move findable without memorizing the whole pantry. Name the ingredients well and the same page becomes a story seed.
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.
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.
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.
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.
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.
Five transforms: boon, bane, bone, bonk, honk. A mix is how tone and structure stay in the same room.
*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.
Four good first loops
Four situations: a glossary, a live table, a kitchen, a texture surface. Sit .reading ^systems ~play @studio in the hook — the set filters like a Midjourney grid. The card that stays bright is the part you would print.
A reason to wonder today
One card makes the work easy to start. One card gives the page a reason to change tomorrow. Both work without JavaScript.
Daily promo
Help the next release land
Releases are scheduled for the 13th and 26th of each month. The A cycle closes on the 13th, and the B cycle closes on the 26th. Small support keeps the work moving and makes the next page easier to ship.
A direct contribution keeps the monthly cadence steady.
@supportDaily wonder
What changes if the page has a reason to return tomorrow?
A site can feel alive when one small surface changes on a schedule. This slot is here to make that return legible.
~systemRead the site as prose, grammar, outputs, and system
Prose
Prose keeps the homepage anchored in readable public language before asking you to inspect the machinery. Every character in <Spw> is a cognitive gesture. A frame #> orients. A probe ? opens inquiry. A reference ~ reaches without binding. A perspective @ charges. 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.
Grammar
Grammar makes the same homepage inspectable. Operators are vocabulary, braces mark containment by attaching local value and behavioral intent to a stable root, and the lines below show how the copy can become a reusable spell.
#>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"
}Outputs
System
The site itself is part of the practice: 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.
Living Concepts
Garden-and-apparatus ideas with a route where each one can be tuned, inspected, and carried into collaboration.
Attention Posture self / local / global
How the site names relation to self, immediate context, and wider horizon before generating or revising an artifact.
Media Cauldron seed / proof / carry
A local-first prompt instrument that turns a source ingredient and attention posture into copyable media or draft artifacts tuned to a collaborator's rhythm.
Spw Operators handles for action
Small readable marks for frames, probes, actions, references, topics, and artifacts so a page can be inspected and reused.
Developmental Climate orient / anchor / offer
The reading climate that controls how much support, density, and challenge the interface should carry while someone learns.
Town Atlas world rulebook
The public world-bible surface for places, customs, rules, guide figures, and details that have earned a structured home.
Proof Cards claim / evidence / action
Screenshot-ready records that name a claim, show enough context, and leave behind a next action or review boundary.
Motif Table sticker / motif / theme
A low-stakes reading surface where a sticker becomes a portable handle, a team reading stages possibilities, and repeated associations grow into a theme without forcing canon too early.
Use the site like a learning surface.
A prerequisite is only useful if something is built from it. One question in, one artifact out: a note, a card, or a brief you can hand to a later collaborator.
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
a proof card, a prompt packet, and a hireable brief: what the concept is, what the depiction tested, what a later illustrator should keep.
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. Separate the concept from a depiction, then keep both.
Name the idea in words. Test it as an image, card, or scene. The reward is the gap: you can see what the concept still needs before it is real enough to hire for.
3. Re-enter through a neighbor.
Use topics, play, care, software, or search to test whether the pattern transfers when the context changes.
Read the story or inspect the machine
Some visitors want story and accumulated craft. Others want the apparatus — routes, runtime, and inspectable structure. Both paths are first-class — and both should leave with a smaller next move than they brought in.
Every component here is a small machine for arranging attention.
For readers
Start with About, the Website Field Guide, Town Atlas, and Recipes when you want story, method, and craft in one readable loop.
For builders
Start with Design, Settings, Software, Search, and the inspect query when you want browser-local controls, CSS, and data attributes to explain themselves — not just render.
#>design @configure_settings ^software ~semantic_spells ? query
Enter the Town Library.
College-level thinking through a playable library: session notes, guide characters, studio quests, and curriculum surfaces with mandatory boundary tests. Choose a role, name the pressure, make the artifact, carry the evidence forward.
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, then save the reflection as evidence.
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.
Study technical fundamentals
CS concepts through bounded economic analogies, mandatory boundary tests, local artifacts, and developmental climate as equity buffers.
The kernel, component tags, and attention handles you tune here can travel with you — garden sediment meeting apparatus inspection. Feed them with garden prompts, compose them in the cauldron, or plant spell trails along ecological channels the Library can tend and replay at each collaborator's rhythm.
garden remembers —
A screenshot can carry intent.
A screenshot is a local record — an ask, offer, agreement, or reference point that says what happened here without asking anyone to guess.
Fund the current sprint
See the active target, what it unlocks, and how someone can help in thirty seconds.
Create a local record 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.
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.
Choose a first route
Action layer. Start with a topic route, a live playtest, a kitchen, or the tools that help someone describe their work well.
If you are returning, let the route change.
The center of gravity moves. Learning weeks, research weeks, playtest weeks, and publishing weeks deserve different doors.
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 semantic spell someone else can point at, inspect, and replay.
Novelty should deepen, not reset.
If you already read an earlier version, skip the intro and enter through a loop: pantry economics, a recipe category, an SVG behavior, a character hook, or a tool that turns the same idea into a local record.
Fresh entry
Pick the route that makes your next question stranger and smaller.
That might be topics if you need a map, search if you need a term to return through, cards if you need a proof surface, or the blog if you need to watch fragments turn into public form.
Integration loops for readers who already know the map
These are sideways doors — not a second homepage. Each loop names a pressure, a reusable component family, and a place on the site where the idea can become evidence, fiction, or a tuned behavior.
A limited pantry is a rules surface: substitution cost, batch base, trade route, spoilage clock, and who benefits when a byproduct becomes stock. Use budgeting for sprint money, recipes for ingredient grammar, and RPG Wednesday when scarcity should become scene pressure.
resource → price → choice
Principle routes teach verbs before dishes: mise, reduction, fermentation. Category clusters — soup system, wing sauce, batch base, byproduct realm — are promptable without pretending the full recipe already exists.
verb → cluster → scene
Path weight, label spacing, pointer fields, and wonder-memory carryover are easier to judge live. Start in SVG experiments, compare against CSS experiments, then project a diagram into Midjourney bench or a recipe card illustration.
stroke → field → screenshot
Contour grammar, cascade layers, and gesture states (charge, armed, sustained) are the same family as cauldron microinteractions. Tune in CSS experiments, inspect on Settings, then read the contract in the field guide.
token → state → legibility
Stock mentor, pickle trickster, and sauce mediator are recipe-native characters that can migrate to cast, world, or character sheet without losing their kitchen logic.
ingredient → person → trace
Profile, character sheet, budgeting, and Midjourney bench are local state machines: enter material, shape a record, screenshot the moment, export JSON when useful. No standalone games yet — play routes and table tools are the live game-like surfaces.
input → record → carry
Creative development prompts one constraint · one artifact
Small prompts for members and returning readers who want depth without a new feature announcement:
- Name one technique verb, one shopping list, and one character who would teach it from memory.
- Sketch one SVG prop (token, ring, bubble, silhouette) that could appear in a recipe card and an RPG scene.
- Tune one CSS state until a hover or hold makes the next action obvious without tooltip homework.
- Run one sprint budget against a real creative constraint: time, food, print, hosting, or release week.
- Plant one spell trail in the footer cauldron, then revisit it from Town Library a week later.
Thanks for wondering through the skills.
A skill surface should return something for the attention it asks: a clearer question, a usable pattern, a replayable spell, or a next move you can actually take.
Learning game
Notice, name, fold, note, return.
- NoticeFind a word, ingredient, operator, prompt, scene, or interface behavior that makes you curious.
- NameUse the visible label, Spw sigil, or nearby copy to give the discovery a handle.
- FoldOpen the details, related route, or resonance peer that keeps the idea one handle away.
- NoteWrite the smallest useful question, recipe, sketch prompt, or genre move before the context evaporates.
- 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.”
A route back to the term
Good vocabulary should help you rediscover the route, prompt, or proof card after the first reading fades.
Take it sideways
Turn the wondering into movement.
Tune the atlas
Settings stay in this browser. Palette bias, color atmosphere, and wonder memory — tunable without touching the kernel.