Runtime observatory
Settings
Preferences are saved in this browser. Start with a preset, adjust workflow or comfort, then inspect the runtime only when you need to.
Treat settings like reading weather: quick to scan, easy to change.
- preset
- workflow
- climate
- density
- inspect
Fast path: preset, workflow, comfort, then deeper tuning only if something still feels off. Workflow describes the writing task; climate describes the attention posture.
The page starts readable, then reveals more structure as the surface becomes familiar.
to shift comfort, workflow, and semantic visibility without changing the public shape of the site.
quick tuning first, deeper inspection later.
a calmer or richer surface, readable local state, and clearer reset paths.
Quick Start
These are the fastest useful controls. Choose a preset for an immediate baseline, then set author workflow, climate, reading comfort, or appearance before opening the deeper registers below.
Tune the Site
Use this register when the quick-start cards are not enough. The categories move from writing task and attention posture into appearance, reading comfort, accessibility, semantic detail, and diagnostics.
Current Runtime State
A readable local summary of what the site is currently expressing in this browser.
Local Notes + Reset Paths
This section is the practical cleanup shelf for both active learners (who want to save notes, inspect state, and restore precise bundles) and playful wanderers (who want a single "reset to calm" without fear). Save local notes, understand reset granularity, and choose the lightest touch that matches your curiosity level.
Local note register
Scratch notes, route ideas, and reminders can stay in this browser and come back later.
No local notes yet. The footer quick-capture seam and this register write to the same local shelf.
Reset guide
Reset model
Use the deviation register for one-setting resets. Use the form reset button for authored defaults. Use browser storage tools only when you want every local trace gone.
- Single-setting reset: available in the deviation register.
- Full settings reset:
data-site-settings-reset. - Local notes: managed separately by the local note register.
- PWA/cache state: reported below.
Saved Data + App Status
These readouts describe what this browser is doing locally.
Read this section
Start with app status, then inspect persistence
Check install, service worker, cache, and connection first. Then inspect what will remain after a refresh or return visit.
Clear safely
Use the smallest honest reset
Clear one setting first, then one register. Use browser-wide clearing only when you want every local trace gone.
Inspect next
Follow the local-state trail
Browser-local registers
Persistence register
These registries persist beyond the current page. Each one shows its key, writer, scope, and clear path.
Runtime Map
Settings are not isolated form fields. They flow into datasets, CSS variables, event bus diagnostics, and progressively enhanced modules.
1. Normalize
Stored values are merged with defaults and checked against allowed options.
normalizeSiteSettings(storage.get())
2. Derive
Settings become author, climate, typography, motion, grain, ecology, semantic, field, and wonder modifiers.
deriveArchitecturalModifiers(settings)
3. Apply
Datasets and CSS variables are written to the document root and body.
document.documentElement.dataset.spw*
4. Emit
Canonical bus events announce settings, author mode, development shifts, and deviations.
bus.emit("settings:changed", settings)
Query recipes
These links use the same query contract as the runtime. Reader mode keeps the native CSS defaults quiet; builder mode is a precise low-theatrics audit surface; inspect and lab mode add progressively more visible resonance for practice, screenshots, and comparison.
When this site is discovered out of context, these recipes are intended to act as landing modes: a calm reader surface for casual browsing, a precision surface for debugging what mounted, and resonant lab surfaces for hobbyists, QA, narrators, and language models that need a page with a clear console story.
Current query:
?view=inspect&meaning=inspect&debug=css,layout&diagnostics=basic&log=site-settings,layout-shift&log-level=debug&module-audit=on&module-visuals=on
Underlying Data Structures
The page is backed by registries and derived structures, not isolated form fields.
Defaults
Canonical fallback values for the full runtime settings model.
DEFAULT_SITE_SETTINGS
Options Registry
Allowed values per setting, used to normalize and reject invalid state.
SETTING_OPTIONS
Presets
Named bundles like Hearth, Loom, Workshop, and Access.
PRESETS
Author Workflows
Draft, Revise, Polish, Publish, and Archive. These describe the writer’s task and drive author-facing tokens.
AUTHOR_WORKFLOW_DEFINITIONS
Developmental Climates
Orient, Anchor, Weave, Rehearse, and Offer. These describe the attention posture around the work.
DEVELOPMENTAL_CLIMATES
Derived Modifiers
Typography, motion, grain, author workflow, climate, ecology, and semantic multipliers.
deriveArchitecturalModifiers(settings)
Document State
Normalized datasets and CSS variables applied to document.documentElement.
root.dataset.spw*
Curriculum Management
Manage your Consideration Register. You can save your current progress as a checkpoint or reset the substrate to its default un-popped state.
Spell Board
Gathered curriculum ingredients appear here as a technical spell.
?gesture_charge { input: "hover | focus | hold" return: "semantic preview" }
#>gesture_project { cue: "? | Alt+Enter | long hold" return: "region menu" }
@gesture_settle { cue: "Escape" return: "focused prose" }
If you are imagining RPG Wednesday enchantments, think of these as three small spell families: charge to inspect a sigil without commitment, project to open the brace or region menu on purpose, and settle to close the layer cleanly and keep the story moving.
Cognitive Web Trace
A transparent interpretation of your technical resonance. As you develop care and focus through the technical substrate, your subjective frame settles into this operable spell.
^"cognitive/web"{
nodes: 0
history: []
resonance: "substrate_definition"
}Support Card Payment Options
Choose which payment methods appear on the support card. One must always remain active.