#>home_frame

I build local-first systems for language, tooling, and knowledge.

I am a staff-level software engineer working across parser-driven systems, interface architecture, developer experience, and knowledge surfaces.

The site is becoming a small homage to a question I care about: what if Obsidian had used Spw from the start?

#>home_frame
#:layer #!pragmatics

^"focus"{
 claim: "Build local-first systems for language, tooling, and knowledge."
 targets: ["Obsidian", "interactive codeblocks", "projection surfaces"]
}

? probe ~ reference @ rotate ^ frame

^"artifact_register"{

Artifact Register

#>parser_runtime_tooling spw-workbench parser, runtime, LSP framing, and toolchain thinking #>language_docs spw.quest documentation surface for the language, grammar, and projection model #>surface_writing spwashi.ai writing about surface, structure, registry posture, and ecosystem design #>public_spec Software surface syntax-first view of Spw, interactive codeblocks, and the Obsidian homage #>public_code GitHub working repositories, active experiments, and implementation depth #>video_surface YouTube public iteration around engineering, design, and current application work

@obsidian_spw_homage

What if Obsidian used Spw from the start?

Notes as frames

Markdown remains the file format, but sections become named, queryable frames instead of anonymous blocks.

Properties as layers

Metadata stays human-readable while becoming more explicit about role, meaning, and projection.

Codeblocks as surfaces

Source, syntax, and render stay linked so codeblocks can behave like miniature tools for thought.

Plugins as projections

Extensibility would still matter, but richer structure would give plugins a stronger shared substrate.

?["surface_register"]

Surface Register

Current work

Public channels

Portals and adjacent surfaces

Flow surfaces

~"constellation"

Constellation

The visual system stays in conversation with the software system: layered, relational, and slightly alive.