#>membership
observer reference working sponsor collaborator

membership as coordination

Membership means helping the work hold shape.

Spwashi is becoming a working field for people who care about art, software, learning, records, local systems, publishing, research, and real-world care.

You do not need to use AI intentionally to belong here. You need to be willing to make, read, support, test, share, organize, or remember something clearly. Membership works best when it can name what stage the work is in and what kind of help that stage needs.

Use this when

you want to name how you can participate without pretending every relationship is the same. Different roles can share a cauldron without becoming one blur.

What it protects

role clarity, contribution boundaries, support paths, and the ability to return later with more specificity. Midprocess visibility is part of that protection.

What it can become

a membership card, scoped collaboration, funded sprint, research role, visual commission, or RPG support lane. Each one gives the work a different rhythm.

^membership_levels

Membership Levels

Observer

Follows the work, shares cards, and responds when something resonates.

Good for people who want to stay near the signal without taking on a formal role yet.

Reference Member

Helps preserve, cite, tag, archive, or clarify useful work.

Good for librarians, researchers, and careful readers.

Working Member

Contributes to projects, posts, tools, music, images, copy, or testing.

Good for artists, engineers, musicians, and writers who want to shape the work while it is happening.

Sponsor Member

Funds specific sprints, cards, tools, people, or outputs.

Good for supporters, clients, and patrons.

Collaborator

Joins a scoped project with defined expectations and possible revenue share.

Good for serious contributors who want a clear lane and a shared finish line.

#>role_field

Working Roles

Illustrators

Visual identity, cards, characters, diagrams, covers.

Musicians

Sound, atmosphere, TikTok audio, release identity.

Librarians

Archives, tags, records, source ladders, references.

Farmers / Gardeners

Grounding, food systems, metaphors, real-world care.

Security Researchers

Trust, verification, abuse prevention, provenance.

Learning Scientists

Skill paths, lessons, onboarding, comprehension.

Novelists

Narrative arcs, lore, voice, world continuity.

Software Engineers

Site systems, local storage, cards, automation, tools.

~"returning_loops"

If you already belong here, deepen through a loop

Membership is not only onboarding. It is also a way to name which kind of attention you can offer this week — reference, craft, play, economics, or inspection — without pretending every visit needs the same introduction.

Reference loop

Pick one route that changed since your last visit. Cite it on a proof card, tag the seam in search, or archive the better wording for the next collaborator.

diff → card → return
Kitchen loop

Choose one recipe category (batch base, byproduct realm, wing cluster, soup system). Host it once in real life, once in play, once as an SVG or CSS specimen.

cook → canon → diagram
Economics loop

Use budgeting to make a sprint legible, then test whether the same scarcity grammar appears in a pantry scene, a commission quote, or a membership support lane.

constraint → ledger → scene
Behavior loop

Tune one interaction in CSS experiments, one mark in SVG experiments, then hold a living term on any long page to see whether the cauldron and gesture anatomy agree.

tune → hold → gather
Creative development loop

One constraint, one artifact, one witness: a card, a screenshot, a planted spell trail, or a session note that someone else can replay without you re-explaining the whole atlas.

pressure → proof → publish

There is no separate games catalog yet. Play and tools are where table logic, local records, and prompt benches currently meet. Games may arrive later as bounded surfaces — not as a generic app grid.

@membership_card

Join By Making A Membership Card

  1. Choose a role.
  2. Name what you can offer.
  3. Name what you need.
  4. Decide whether you want to be public, private, or semi-visible.

@ start membership card