#>plans_surface
strategic direction feature horizons semantic visualization interactive verbs

Strategic Landscape

Plans & Horizons

This page tracks active and future plans for spwashi.com. Each plan is not just a topic; it is a structured action surface. The point is to make the plans easier to read, easier to connect, and easier to visualize later as a semantic field rather than a pile of notes.

For now, the strongest improvement is to make the verbs clearer. A good plan should reveal what it is trying to refine, build, map, integrate, teach, stage, publish, or adapt. That gives the page stronger structure and prepares it for later interactive or visual tooling.

?"verb_register"

Verb Register

Plans become more useful when their verbs are explicit. These are the verbs currently structuring the work. Later, each one could become interactive, filterable, or visually projected as part of a plan map.

Refine

Clarify operator meaning, naming, behavior, and conceptual precision.

Build

Create surfaces, runtimes, tools, pages, and reusable structures.

Map

Expose relationships, symmetry, spatial address, discovery routes, and asset classification.

Integrate

Make SVG, runtime settings, images, gestures, and surfaces work coherently together.

Teach

Help visitors build fluency through explanation, repetition, and experience.

Stage

Control timing, pacing, cinematic reveal, and semantic emphasis over time.

Publish

Make plans, assets, operator pages, and media legible as public artifacts.

Adapt

Support mobile runtime, accessibility, settings, and user preference without losing coherence.

^"operator_semantics_plans"{

Operator Semantics & Lore

Plans that refine how operators work, what they mean, and how they become public surfaces rather than private theory.

Operator Semantics Refinement

foundation

Refine Spw operators so they remain true to the established lore and original set while leaving room for interpretation through symmetry, priming, and operator physics.

refine map teach
Feature Considerations:
  • Document operator lineage from original meaning to current implementation.
  • Explain physics: spatial acts, priming properties, interaction semantics.
  • Map symmetry: operator pairs, coherent dynamics, mirrored functions.
  • Clarify why some sequences feel inevitable once the physics is understood.
  • Show how interpretation emerges from structure rather than arbitrary rules.
Wonder Hook:

Operators are not arbitrary symbols. They are repeatable spatial and attentional relationships. Once that becomes visible, the language stops feeling invented and starts feeling discovered.

~ full plan ^ semantics document

Spw Operator Pages

active

Create a public atlas where each operator gets a stable page before it gets richer runtime behavior. The page should teach interaction semantics, metaphysics, brace physics, and symmetry through its own structure.

build teach publish
Feature Considerations:
  • One stable page per operator.
  • Sections for interaction, metaphysics, brace physics, and symmetry.
  • Operator-aware styling so the page demonstrates the operator through the medium itself.
  • Public discovery from home, software, and route navigation.
  • Stable URLs that can be referenced from other pages and future diagrams.
Wonder Hook:

The medium should teach the message. A reference operator page should feel referential in how it stages explanation and movement, not just in what it says.

~ full plan ^ atlas
@"interaction_patterns"{

Interaction Patterns & Circuits

Plans that build satisfying circuits, reward familiarity, and make interaction semantics easier to learn over time.

Interaction Grammar

active

Develop practical interactive circuits that become satisfying and familiar over time. Rethink brace physics vocabulary toward something cognitively accessible while preserving spatial relationship practice.

build teach adapt
Feature Considerations:
  • Entry → practiced → fluent → habitual progression.
  • Brace physics vocabulary audit and accessibility review.
  • Subtle familiarity feedback that does not feel gamified.
  • Runtime recognition of repeated user circuit preferences.
  • Touch-native circuits that still honor operator priming.
Wonder Hook:

Depth should emerge from familiarity. The site becomes something a visitor can learn to play, not just inspect once.

~ full plan ^ semantics

Cinematic Handles

planning

Give page components semantic handles for timing, phases, and attention curves so interactions can be composed with intention instead of accidental motion defaults.

stage integrate adapt
Feature Considerations:
  • Named timing tokens for small, medium, and full reveals.
  • Attention curves for ambient vs. addressed components.
  • Cross-element transition composition.
  • Screenshot pause moments where semantic intent is legible.
  • User-adjustable pacing sensitivity through settings.
Wonder Hook:

Motion becomes meaningful when it has a role. Timing can communicate relation, emphasis, caution, invitation, or readiness.

~ full plan

Cognitive Navigation

active

Design navigation that builds cognitive maps. Users should understand where they are, how they got there, and how to return without depending on external breadcrumbs alone.

map build teach
Feature Considerations:
  • Spatial address and frame hierarchy.
  • Local ground as always-available return point.
  • Surface map for visual layout understanding.
  • Wayfinding affordances that do not depend on prior expertise.
  • Reduced cognitive load while still teaching structure.
Wonder Hook:

The site becomes navigable like a building: familiar rooms, repeated landmarks, and confidence that structure can be learned.

~ full plan
*"platform_horizons"{

Platform Horizons & Features

Plans that expand what the site can do operationally: assets, mobile runtime, RPG tooling, pretext lab, and settings.

Semantic Asset Management

foundation

Organize images and assets by purpose and surface with sidecar `.spw` metadata so assets become discoverable semantic participants instead of anonymous files.

map integrate publish
Feature Considerations:
  • Surface-specific organization for images and media.
  • Sidecar metadata: spirit name, mapping, optimization record.
  • Optimization pipeline with multiple output tiers.
  • Discoverable asset registry.
  • Naming system that helps images become addressable content.
Wonder Hook:

An image should not just exist on disk. It should have a name, a surface, a role, and a reason to be discoverable later.

^ conventions @ naming-magic skill

Mobile Runtime Foundation

active

Build a mobile-first runtime that keeps interaction semantics intact on small screens instead of collapsing the site into reduced desktop leftovers.

adapt build integrate
Feature Considerations:
  • Touch gestures mapped to operator interaction.
  • Viewport discipline and chrome decisions.
  • Progressive disclosure for small screens.
  • Spatial address maintained on mobile.
  • Battery and connection-aware performance defaults.
Wonder Hook:

The site should transform for mobile rather than merely shrink. Structure should survive the change in modality.

~ full plan

RPG Local Gameplay

active

Build a local-first RPG table tool with session state, character sheets, dice, and encounter handling that remains usable without a server.

build adapt publish
Feature Considerations:
  • Local-only session state.
  • Character and creature support surfaces.
  • Encounter runner and initiative logic.
  • Dice systems and roll history.
  • Screenshot-ready interaction moments.
Wonder Hook:

The tool should disappear into play. Reliability becomes part of the atmosphere.

^ gameplay surface ~ full plan

Pretext & Whimsy Lab

planning

Create a lab for mathematics, physics, notation, and code framed through Spw’s spatial grammar so other languages can shine more clearly rather than be replaced.

build teach integrate
Feature Considerations:
  • Multi-language surfaces for math, code, and notation.
  • Discovery exercises taught through spatial play.
  • Notation comparisons that reveal structure.
  • Whimsy without loss of rigor.
  • Physics visualization as explanatory support.
Wonder Hook:

The lab is where rigor and play meet. It should make formal systems feel more inhabitable.

~ full plan

Runtime Settings & Customization

foundation

Give users granular control over appearance, accessibility, visibility, developer surfaces, and performance without forcing immediate configuration burdens.

adapt integrate teach
Feature Considerations:
  • Accessibility settings.
  • Appearance and color behavior.
  • Developer/debug visibility.
  • Typography controls.
  • Performance and lazy-loading preferences.
Wonder Hook:

Defaults should be calm, but control should exist for people who want to inspect, tune, or quiet the environment.

@ settings ~ full plan
~"supporting_plans"{

Supporting Plans & Infrastructure

Foundational and support plans that strengthen the rest of the system.

Media Publishing Register

foundation

A small publishing register that makes the site easier to discuss by keeping focus, featured components, and reusable topic handles configurable.

publishmap
~ full plan

Screenshot Semantics

planning

Make semantic relationships visible in screenshots so operator pairings, attention states, and structure remain legible outside the live site.

stagepublish
~ full plan

CSS Progressive Ornaments

active

Develop a visual enhancement layer that emphasizes without breaking core function, and reveals itself through interaction, attention, or animation.

stageintegrate
~ full plan

SVG Surface Integration

planning

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

integratebuild
~ full plan

PWA Experience

foundation

Support offline access, installability, shared links, and native-like continuity through progressive web app behavior.

adaptbuild
~ full plan

Agent Optimization

active

Make the .agents/, skills, .spw bridges, validation contracts, and public plan surfaces easier for humans and agents to inspect without repeated rediscovery.

maprefine
~ full plan @ plan maintenance
*"plan_relationships"{

Plan Relationships

This is the part most worth visualizing later. A good plan page should not only list plans. It should show how one plan enables another.

Semantics first

Operator Semantics Refinement supports Spw Operator Pages, Interaction Grammar, and eventually Pretext & Whimsy Lab.

Navigation and pacing

Cognitive Navigation and Cinematic Handles support route legibility, timing, and visual learning across the whole site.

Assets and SVG

Semantic Asset Management and SVG Surface Integration together support diagrammatic and image-rich semantic surfaces.

Runtime adaptation

Mobile Runtime Foundation, Runtime Settings, and PWA Experience support portability and usable continuity.

Publishing and capture

Media Publishing Register and Screenshot Semantics support discussion, sharing, and public explanation.

Play surfaces

RPG Local Gameplay and Pretext & Whimsy Lab support applied experimentation and learning through interaction.

?"plan_discovery"{

Plan Discovery & Use

What is a plan?

A plan is a structured document for a feature consideration or brand horizon. It should be usable as guidance, not just archival prose.

What do the statuses mean?

  • Foundation: conceptually strong and ready to guide implementation
  • Active: being developed or refined now
  • Planning: the direction is set, but not yet underway

What should improve later?

The next step is visual structure: better surface styling, verb-aware filtering, plan relationship diagrams, and a more legible semantic map.

Where are the source files?

Full plan documents live in the GitHub repository under `.agents/plans/...`, and related `.spw` files live in the same repo where applicable.