#>home_frame

A working site for language tools, readable systems, and play.

I build parser systems, interfaces, and knowledge tools that keep structure visible.

The site is both portfolio and workbench: static HTML, installable routes, Spw language notes, RPG utilities, and small components for inspecting how pages are organized.

The current throughline is an Obsidian application centered on Spw, a readable plain-text format for navigable semantics, LSP tooling, and learning materials.

#>home_frame
#:layer #!pragmatics

^"focus"{
 claim: "Build local-first systems where readable files and helpful tools stay connected."
 targets: ["Obsidian application", "plain-text semantics", "LSP clients", "learning surfaces"]
}

? probe ~ reference @ apply ^ frame $ inspect ~ craft > blog * focus

$"cognitive_machine_map"

How To Read The Site

Start with the page in front of you, then follow the handles when you want more. The main paths introduce the site mechanics, the language work, and the play tools one layer at a time.

#>machine_register How the site works A field guide to frames, navigation, the console, the PWA shell, and the accessibility baseline. ?[operators] Every operator has semantics Read the symbols as a small vocabulary for structure, action, reference, and inspection. >pretext_physics Whimsy from measurement Try a live text layout probe where line wrapping becomes measurable and visible. @capture_frames Local media staging See how RPG notes can become private table tools for scenes, screenshots, and prompts. ^"motifs"{ Exploration rewards Motifs add optional texture after the core reading path is already clear.

*"media_focus"

Signal Register

Start here when you want the current thread. The weekly and daily cards point to a route that is worth attention without turning the whole site into a dashboard.

Weekly focus

$

Quiet controls, open doors

The controls stay close enough to use, but quiet enough that the page can still read like a page.

Set the threshold

Daily focus

?

Follow a live thread

One route stays warm each day so exploration has a simple first step.

Walk the ring

!threshold Quiet switchboard Adjust how visible the map, console, and scroll behavior should be in this browser. $dispatch Table brief Keep scene state, turns, clocks, notes, and session seeds close during play.

^"artifact_register"{

Artifact Register

These are the main entry points. Each one should give you a usable next step, not just another label.

#>craft_surface Craft Making web pages by hand. HTML, CSS, and SVG as creative materials for authors, illustrators, and anyone who treats files as play. #>public_spec Software surface Start here for Spw syntax, operator grammar, interactive codeblocks, and the Obsidian application context. #>rpg_wednesday RPG Wednesday A recurring tabletop session with a log, world notes, cast references, and local play tools. #>parser_runtime_tooling spw-workbench The TypeScript repository where the parser, runtime, LSP, and tooling ideas are developed. #>operator_atlas Spw operator atlas Use the atlas to learn each operator as syntax, interaction primitive, and future UI contract. #>website_field_guide Website field guide A reader-friendly tour of the site as an installable, inspectable publishing surface. #>author_craft Author craft Fragments, SVG motifs, file traditions, and screenshot prompts for writers exploring web pages. #>blog_input_interpreter Blog interpreter Turn Spw fragments, wonder notes, and rough drafts into local questions, outlines, and readable language seeds. #>language_docs spw.quest Language documentation for the grammar, examples, and projection model. >pretext_field_lab Pretext field lab A live probe for measuring text layout once and projecting it at multiple widths. #>surface_writing spwashi.ai Writing about surfaces, structure, registries, and ecosystem design.

@obsidian_application_context

Applying to Obsidian with Spw in mind

Plain text stays central

Readable files are the trust surface. Spw explores how sections can become named and queryable while the source stays plain.

LSP-aware semantics

Operators, layers, and references can be indexed by LSP servers and clients, so the same structure helps both people and tools.

Codeblocks as surfaces

Source, syntax, and render stay linked, which lets a codeblock become a small tool without losing its original text.

Literate curricula

The same grammar can support learning materials where reading, annotating, projecting, and reflecting stay connected.

?["surface_register"]

Surface Register

Use this as the directory view after the main routes make sense: local pages first, then external work, domains, and ways to reach me.

On this site

craft — author ramps for fragments, SVG motifs, file traditions, and book-site prompts
software — Spw syntax, grammar, interactive codeblocks
pretext lab — text layout without DOM reflow
website field guide — media-oriented tour of the site's PWA, frame, and Spw features
blog — local synthesis surface for Spw, wonder, rough notes, and future posts
rpg wednesday — recurring session log
about — systems, surfaces, direction