Knowledge Bases

This hub is for tools and methods that treat notes as working memory rather than as a single final document. The useful distinction is not just "editor" versus "not editor." It is whether the system supports retrieval, cross-reference, staged drafting, and long-lived accumulation in a way that changes how you think and write.

Spw is the knowledge base I actually keep: readable source, named stems, and routes that project the same notes into HTML. Other local-first writing tools exist; they are neighbors, not the substrate this site is built from.

This site is itself a public knowledge surface: routes carry data-spw-* semantics, the runtime can snapshot topical payloads for handoff, and Spw stays readable beside HTML. Compare private notes with how this field guide exposes inspectable contracts.

Knowledge Base Value Model

Knowledge bases matter when they reduce rediscovery cost. A good one turns scattered work into durable recall, gives future collaborators a route into the material, and keeps private notes close enough to become public artifacts when the time is right.

What this page should help answer

Use this route when the question is practical: what makes a tool a knowledge base, which kinds of structure matter, and where the category overlaps with writing, research, and publication. The point is not generic productivity advice. It is to understand which properties actually change author workflow. Returning learners can treat this as the junction point between note-taking, Markdown, and publication surfaces.

Spw as a knowledge base

A knowledge base is useful when a later reader — human or model — can find a claim, follow a link, and tell source from projection. Spw is that layer here: .spw files and route HTML stay dual-readable; operators and topics are retrieval handles; the atlas and the literal parser show what the marks actually parse.

In spring 2026 I saw a small-team role on a local-first writing tool and said so in public instead of spraying silent applications. I have since sat with that product’s principles and community: keep the files, put rare features in plugins, teach agents the open formats rather than replacing the notebook with a chat window. The work that remained mine was to make this site a knowledge base that those principles can still recognize.

The four months after that declaration were mostly infrastructure that a knowledge base needs in order to stay honest: a page template so routes share a shell, a browser parser that is the same kernel as the workbench, operator names aligned with that parser, a module catalog that can unmount as well as mount, and site search that can find a stem. Copy still has to earn its keep as facts a reader can use, not as a plea to imagine more blends.

What Dregg already asks of this practice

The Dregg codebase includes a concrete content-authoring spec written for this name: it names three tracks, what is built, and what still needs a surface. Read it in the repo: CONTENT-AND-ASSET-SPEC.md. Hand-drawn or generated stills have a shorter sibling: CONTRIBUTING-ASSETS.md.

The tracks are useful when a crew can share them: the same seed, the same scene, the same table version. A stranger should be able to re-run what you held. That is group behavior, not a portfolio ask. lore.land is where long-form from those scenes can become public without pretending the vault and the game are the same room.

Some Dregg repos also keep .spw as sidecar curriculum — notes a crew can hold beside the code, not the Descent’s .scene grammar. dragons-clutch/.spw is one of those trees: canon, index, mount. This site is a different consumer, and a place to challenge how those notes parse.

Holdings, not a single ticker

Token talk stays abstract when it pretends value is one coin. Three holdings a crew can share — identity, boundary, ledger — are already named. Other systems can reuse the policy without copying a brand.

Keep the three in relation. Collapsing them into one price is the singular-currency move. Five boonhonk voices work the same way: you do not spend all at once. Count the dummy, then return to a region.

Other coins that need “the same object stays the same across a season” can use these primitives. This page does not sell a token. Color and emphasis change how a holding is seen; they do not mint it.

Spween .scene marks

Track B is handwritten text. The Descent compiles it to executor teeth; the no-cheat board re-runs the same teeth. This is Dregg’s grammar, not Spw. A site (scene) can later project onto $scene — it is not this file format.

---
id: salt-vault
title: The Salt Vault
tags: [descent]
---
=== entrance
The vault door hangs open.
* [Force it] { strength >= 5 }
  ~ noise += 1
  -> hall
* [Pick the lock] { gold >= "$price" }
  ~ gold -= 10
  -> hall
=== hall
* [Take the crown] { hands < 1 }
  ~ hands = 1
  -> END

Starting references

Related routes