Working register
Plans & Horizons
I'm planning the next surfaces so you can enter, inspect, and keep going. A plan earns its place when it opens a door on this site — a route, a lab, or a setting — not when it names a folder.
Start with what is moving now. Owners live in the buckets. Verbs say what the work does. Relationships show what enables the next move.
Plan Buckets
Pick a bucket, then open a live surface. GitHub is the ledger; the site is the proof.
Semantic Rails & Editor Operations
activeMeaning that survives a route change. Use this when you need one name in HTML, CSS, JS, and `.spw`.
CSS, Layout & Interaction
activeHow a page sits still, then deepens. Open the CSS lab to see who wins; first paint is who arrives.
Runtime, JS & Validation
activeWhen scripts mount, and what they may not delay. CSS delivery is a sibling schedule, not a later layer.
Media, Image & Sensory Material
activePictures and motion that belong to the page they sit on. Tune color after the type already reads.
Public Route, Proof & Genre Systems
activeRoutes that prove the system in public. Walk the design hub, then play, then come back here.
Templates, Tooling & Archive
activeWhat to copy, what to leave, and what already finished. The archive is a citation, not a queue: on September 17, 2026, fifty-seven finished or merged plans moved there with their citations retargeted, and the live tree is what remains.
Now
Three things moved the week of . The runtime measures once per frame instead of whenever a module asks. A folio can be asked for before it can be bought. And the edges that nearly agree are now a list, not a feeling.
Measure once per frame
landedEvery lane that reads geometry now reads in one pass after the browser's own style pass, reads first and writes after. On a phone, the boot forced half as many full recalculations. The stylesheet's weight per recalculation is the next cut.
Order a folio
landedA screenshot of a filled card is an order. The card on the folio worktable takes a piece, a form, a story, a range, and a way to reach you, then copies itself as a Spw block, downloads as text, or screenshots.
Edges that nearly agree
activeAn audit now asks every box how it sits in its container and reports only the edges that miss by a few pixels, because nobody chooses a three-pixel inset. The blog toplines were the first fix; the home panels are next.
What a New Production Needs
A plan earns more when it can start a show. Three ingredients keep coming back: a seed you can hold, a frame where people already talk, and an anchor the group can dress. The site already has beats for them — prepare on Monday, play on Wednesday, close on the 13th and 26th — the days the Dregg community releases, too — reflect the day after, celebrate a streak.
A folio series as the seed
activeOne laminated folio from a set is enough to start: it has a picture, a material history, and a scan that can travel. A series is a bed the studio adds to each season, so the seed keeps its lineage when the production grows past it.
A group chat as the frame
activeA TikTok group with a streak is already a room with a clock — 314 days on September 17, pet in outfits. Use it as the common frame: the seed goes in on Monday, the table plays it Wednesday, and each beat can be a small, otherwise inconsequential wonder that still survives a screenshot. Dialogue becomes show beats when the room agrees on the calendar.
A popcorn streak pet as the anchor
planningA streak needs a face. The live TikTok pet has popped and wears outfits. The site pet stays a small customizable mascot the group names and dresses, grown by return rather than by points, and it can stand for a team or a single scene. Proposed as a card: fill it in, screenshot it, send it. Share one incremental wonder, not a thesis.
Verb Register
A verb is a next action. Refine a meaning, build a surface, teach a route.
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 & Lore
Plans that refine how operators work, what they mean, and how they become public surfaces rather than private theory.
Operator Semantics Refinement
foundationRefine Spw operators so they remain true to the established lore and original set while leaving room for interpretation through symmetry, priming, and operator physics.
- 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.
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.
Spw Operator Pages
activeCreate 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.
- 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.
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.
Interaction Patterns & Circuits
Plans that build satisfying circuits, reward familiarity, and make interaction semantics easier to learn over time.
Interaction Grammar
activeCircuits should stay familiar: a tap on text selects, swipe only where the host names a cycle, and leftover is shared after the finger lifts. Cross-session fluency is still open.
- 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.
Depth should emerge from familiarity. The site becomes something a visitor can learn to play, not just inspect once.
Cinematic Handles
merged referenceResearch reference for semantic timing; active motion and timing work routes through Color & Motion.
- 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.
Motion becomes meaningful when it has a role. Timing can communicate relation, emphasis, caution, invitation, or readiness.
Cognitive Navigation
split referenceDesign 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.
- 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.
The site becomes navigable like a building: familiar rooms, repeated landmarks, and confidence that structure can be learned.
Platform Horizons & Features
Plans that expand what the site can do operationally: assets, mobile runtime, RPG tooling, pretext lab, and settings.
Semantic Asset Management
foundationOrganize images and assets by purpose and surface with sidecar `.spw` metadata so assets become discoverable semantic participants instead of anonymous files.
- 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.
An image should not just exist on disk. It should have a name, a surface, a role, and a reason to be discoverable later.
Mobile Runtime Foundation
split referenceBuild a mobile-first runtime that keeps interaction semantics intact on small screens instead of collapsing the site into reduced desktop leftovers.
- 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.
The site should transform for mobile rather than merely shrink. Structure should survive the change in modality.
RPG Local Gameplay
activeBuild a local-first RPG table tool with session state, character sheets, dice, and encounter handling that remains usable without a server.
- Local-only session state.
- Character and creature support surfaces.
- Encounter runner and initiative logic.
- Dice systems and roll history.
- Screenshot-ready interaction moments.
The tool should disappear into play. Reliability becomes part of the atmosphere.
Pretext & Whimsy Lab
planningCreate 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.
- 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.
The lab is where rigor and play meet. It should make formal systems feel more inhabitable.
Runtime Settings & Customization
foundationGive users granular control over appearance, accessibility, visibility, developer surfaces, and performance without forcing immediate configuration burdens. Equal settings rest: a control that is already true should not rewrite the page.
- Accessibility settings.
- Appearance and color behavior.
- Developer/debug visibility.
- Typography controls.
- Performance and lazy-loading preferences.
Defaults should be calm, but control should exist for people who want to inspect, tune, or quiet the environment.
Supporting Plans
Foundations that stay useful after the current cut. Open a route when the plan names one.
Media Publishing Register
foundationWhat this week is about, in public. Use it when a conversation needs one featured surface.
Screenshot Semantics
planningA still frame should still explain itself. Capture from settings when you need a shareable proof.
SVG Surface Integration
planningA diagram should carry the same tokens as type. Open the SVG lab when a picture needs an address.
PWA Experience
foundationThe page should remain after the tab closes. Install is a courtesy, not the product.
Agent Optimization
activeThe next session should cost less discovery than the last. The PLAN is a gate, not a diary; always-on word budgets fail in check:agents.
Plan Relationships
One plan should open another. Follow the link, not the folder name.
Semantics first
Operator meaning supports public operator pages. Read the lore, then try a chip on the Spw topic.
Navigation and pacing
How a route teaches its own next step. Timing work lives in now; motion tokens stay in color-motion.
Assets and SVG
Pictures that can be addressed. Open the SVG lab when a diagram should carry the same tokens as type.
Runtime adaptation
The page should stay usable when the network is thin. Tune in settings; install is a later courtesy.
Cascade is not delivery
The CSS rail owns who wins. The spend-cut owns who arrives. JS mount is a sibling. Reordering @layer does not shrink the bundle. See now.
Spend only on change
Equal settings rest, and the runtime now measures once per frame. Follow that to settings and the runtime lab. The next write is one that does not say the same thing twice.
Copy as a place
A sentence you can collect should have an address on the page. Follow home and about. Folio invitations live on those rooms and on folios.
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 & 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
- Merged reference: source context is retained; active work routes to the named owner
- Implemented reference: a landed contract retained for citations, not an active queue
- Split reference: the umbrella is retained; concrete work routes to narrower owners
What should improve later?
Now should rotate when the commit trajectory moves. The next write on the site is one that does not restate what it already wrote — not a new filtering chrome for this register.
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.