#>plans_surface
strategic direction feature horizons wonder hooks

Strategic Landscape

Plans & Horizons

This page maps the active and future plans for spwashi.com. Each plan explores a feature consideration or brand horizon, grounded in interactive semantics, operator physics, and the spatial grammar of the site. Plans are elaborated as they develop; some are complete foundations, others are active explorations.

^"operator_semantics_plans"{

Operator Semantics & Lore

Plans that refine how operators work, what they mean, and how they create meaning through composition, symmetry, and priming.

Operator Semantics Refinement

foundation

Refine Spw operators to be true to the established lore and original set, with room for interpretation based on the physics of the language and traditions that emerge through symmetry and priming.

Feature Considerations:
  • Operator lineage documentation: original meanings → current implementation
  • Physics explanations: spatial acts, priming properties, interaction semantics
  • Symmetry mappings: 9 operator pairs that create coherent dynamics
  • Priming rules: why sequences like ~(#frame) ?! feel inevitable
  • Interpretation emergence: how traditions arise from physics, not imposition
Wonder Hook:

The deeper insight: operators are not arbitrary symbols, but spatial and attentional relationships that can be felt, discovered, and built upon. Understanding operator physics makes everything else on the site feel less like a collection of features and more like a coherent language.

~ full plan ^ semantics document

Spw Operator Pages

active

Create a public atlas where each operator gets a stable, beautiful page before it gets richer runtime behavior. Pages explain interaction semantics, metaphysics, brace physics, and prefix/postfix symmetry.

Feature Considerations:
  • One page per operator: ~, #, ., ?, !, *, &, @, ^, <>, [], {}
  • Sections: interaction (invoke/inspect/unavailable/pass-through), metaphysics, brace physics, symmetry
  • Symmetry visualization: show which operators pair with this one
  • Public discovery: accessible from home, software surface, route navigator
  • Operator-aware CSS: each page demonstrates its own operator through styling
Wonder Hook:

Documentation as experience: reading about the reference operator (~) on the reference operator page should teach through spatial demonstration, not just explanation. The medium is the message.

~ full plan ^ atlas
@"interaction_patterns"{

Interaction Patterns & Circuits

Plans that build interactive patterns that reward familiarity, feel natural through operator priming, and progress from entry-level to fluent mastery.

Interaction Grammar

active

Develop practical interactive circuits that become satisfying and familiar over time. Rethink brace physics toward vocabulary that is cognitively accessible while using Spw to exercise spatial relationship.

Feature Considerations:
  • Interactive circuit ladder: entry → practiced → fluent → habitual progression
  • Brace physics vocabulary audit: accessibility of boon/bane and candidate alternatives
  • Familiarity feedback: subtle signals that don't feel gamified
  • Circuit recognition: the runtime learns what patterns the user gravitates toward
  • Mobile-first circuits: touch gestures that honor operator priming
Wonder Hook:

The site becomes an instrument to learn: just as a musician builds fluency through practice, a visitor builds fluency with Spw operators and spatial grammar through repeated, rewarding interaction. Depth emerges from familiarity, not from required upfront knowledge.

~ full plan ^ semantics

Cinematic Handles

planning

Give page components semantic handles — named timing tokens, transition phases, and attention curves — so that interactions can be composed with cinematic intention, not just mechanical timing.

Feature Considerations:
  • Named timing tokens: practice-settle (100ms), threshold-reveal (300ms), full-express (600ms)
  • Attention curves: how components become more legible when addressed vs. ambient
  • Transition composition: sequences that feel coordinated across multiple elements
  • Screenshot capture: pause moments where semantic intent is visible
  • Customizable pacing: settings that let users adjust timing sensitivity
Wonder Hook:

Interaction timing as storytelling: every transition, fade, and reveal becomes a moment of intention rather than accident. The site learns to whisper and shout, to pause and accelerate, with semantic purpose.

~ full plan

Cognitive Navigation

active

Design spatial navigation that builds cognitive maps. Users should feel they understand where they are, how they got there, and how to return — not through breadcrumbs, but through spatial fluency.

Feature Considerations:
  • Spatial address: frame hierarchy and path legibility
  • Local ground (.): always accessible return point within any depth
  • Surface map: visual representation of the site's spatial layout
  • Wayfinding affordances: how to discover routes without external maps
  • Cognitive load: minimum needed to build a spatial model
Wonder Hook:

The site itself becomes a space you can learn to navigate like a building: familiar rooms, recognizable landmarks, and the confidence that you can find your way around without a GPS. Spatial fluency transfers to spatial thinking.

~ full plan
*"platform_horizons"{

Platform Horizons & Features

Plans that expand what the site can do: asset management, responsive design, advanced settings, gameplay, and multi-language surfaces.

Semantic Asset Management

foundation

Organize images and assets by purpose/surface with sidecar .spw metadata. Each asset gets a spirit name, thematic mapping, and optimization record. Assets become discoverable participants in the site's semantic system.

Feature Considerations:
  • Surface-specific organization: rpg-wednesday, pretext-lab, illustrations, motifs, home
  • Sidecar .spw metadata: spirit name, thematic mapping, optimization metadata
  • Image optimization pipeline: multi-format variants (AVIF/WebP/PNG) at surface-specific tiers
  • Whimsical naming skill: /image-naming-magic for spirit-based image naming
  • Asset discovery index: .spw/assets.spw as navigable registry
Wonder Hook:

Images stop being anonymous assets and become named, semantically classified participants in the site's lore. A Midjourney render becomes "threshold-poise" with its own spirit mapping and discovery tags, turning static images into discoverable content.

^ conventions @ naming-magic skill

Mobile Runtime Foundation

active

Build a mobile-first runtime that keeps interaction semantics intact on small screens. Touch gestures honor operator priming and symmetry; layouts adapt without losing spatial coherence.

Feature Considerations:
  • Touch gesture semantics: tap, swipe, long-press mapped to operator interactions
  • Viewport management: how much UI chrome, how much content space
  • Progressive disclosure: what's always visible vs. revealed on interaction
  • Spatial address on mobile: how to maintain navigation fluency on smaller screens
  • Performance optimization: connection and battery awareness
Wonder Hook:

The site doesn't shrink on mobile; it transforms. Interactions that feel natural on a large screen find touch-native equivalents that feel equally intentional. Spatial thinking scales to any screen size.

~ full plan

RPG Local Gameplay

active

Build a local-first RPG table tool: session state, character sheets, dice, encounter runners. Everything stored in browser; shareable by copying session code. No server required.

Feature Considerations:
  • Session management: local-only state, shareable URLs, no authentication
  • Character & creature tools: sheets, quick-ref, portrait storage
  • Encounter runner: turn order, initiative, condition tracking
  • Dice & randomness: multiple dice types, roll history, grouped rolls
  • Screenshot-ready: clean UI for capturing session moments
Wonder Hook:

A table companion that never goes down, never asks for data, never locks you out. Your campaign lives in your browser and in your shared links. The tool disappears; only the play remains.

^ gameplay surface ~ full plan

Pretext & Whimsy Lab

planning

Create a space for exploring mathematics, physics, notation, and code through the lens of Spw's spatial grammar. Let other languages shine by framing them, not replacing them.

Feature Considerations:
  • Multi-language surfaces: mathematics, musical notation, code snippets framed with Spw operators
  • Discovery exercises: interactive explorations that teach through spatial play
  • Notation comparison: same concept shown in multiple notations to reveal structures
  • Whimsy affordances: typos, puns, playful examples alongside serious content
  • Physics visualization: animated diagrams that make abstract concepts tangible
Wonder Hook:

Mathematics becomes a language you can see and feel, not just read. Code exposes its own spatial structure when framed through Spw. The lab is where playfulness and rigor meet — where you can wonder and compute simultaneously.

~ full plan

Runtime Settings & Customization

foundation

Give users granular control over their experience without forcing choices. Settings for accessibility, appearance, developer tools, typography, visibility, and performance.

Feature Considerations:
  • Accessibility: reduce motion, high contrast, font size presets
  • Appearance: color mode, operator saturation, animation intensity
  • Developer: debug mode, frame metadata, verbose logging
  • Typography: font scale (80-120%), line spacing, monospace variant
  • Visibility: footer toggle, header opacity, spec pills display
  • Performance: animation throttling, lazy loading preference
Wonder Hook:

The site adapts to you, not the other way around. Whether you need a quiet interface, bold colors, fast feedback, or semantic metadata, there's a lever for it. The defaults are calm; the possibilities are rich.

@ settings ~ full plan
~"supporting_plans"{

Supporting Plans & Infrastructure

Foundational and supporting plans that strengthen other systems: media publishing, screenshot semantics, visual design, and SVG integration.

Media Publishing Register

foundation

A small publishing register that makes the site easier to discuss: current focus, featured components, and reusable topic handles are configured in JSON.

~ full plan

Screenshot Semantics

planning

Make semantic relationships visible in screenshots. Operator pairings, spatial relationships, and attention states should be visible to inspection without needing the live site.

~ full plan

CSS Progressive Ornaments

active

Visual enhancement layer that adorns and emphasizes without breaking core functionality. Ornaments reveal themselves through interaction, attention, or animation.

~ full plan

SVG Surface Integration

planning

Integrate SVG as a first-class surface for interactive diagrams, operator visualization, and spatial demonstrations.

~ full plan

PWA Experience

foundation

Progressive Web App capabilities: offline access, installability, shared links, and native-like performance.

~ full plan
?"plan_discovery"{

Plan Discovery & Relationships

What's a plan?

A plan documents a feature consideration or brand horizon for spwashi.com. It includes the goal, scope, feature considerations, key files, dependencies, and validation approach. Plans are living documents that evolve as work happens.

What are statuses?

  • Foundation: Complete conceptual work; ready to guide implementation
  • Active: Currently being developed or refined
  • Planning: Strategy is set; implementation has not started

How do I read a plan?

Each plan card shows the thesis, feature considerations, and wonder hooks. Links point to the full plan document and related surfaces. Start with the thesis, explore the considerations, and follow links for deeper dives.

How are plans related?

Plans support each other: operator-semantics-refinement provides the conceptual foundation for interaction-grammar and spw-operator-pages. Dependencies are documented in each plan's full document. The integration guide shows the full relationship map.

Can I suggest a plan?

Plans emerge from doing. If you notice something missing or something that could be better, that's the beginning of a plan. Reach out through contact, or start a plan document in the .agents/plans/ folder on GitHub.

Where are the full plans?

Full plans live in .agents/plans/{plan-name}/. Each plan has a PLAN.md with complete documentation, often supplemented with .spw files that capture semantics and integration points.