The same corpus, read three different ways.

A lens is a descriptor, and the descriptor is data.

Not a fork, not a mode flag threaded through the codebase. A serializable object that the server hands to the client, to the agent API, and to the MCP server — one source of truth for what a domain is called and what it can do.

Vocabulary

Tree sections and document-type labels. The same underlying type is a “Thread” in the Novel lens and a “Quest” in the Campaign lens — one engine concept, two domain words.

Interface

The sidebar tree, type pickers, “add” and “upload as” menus and document-browser facets all render from the served descriptor rather than from a table baked into the client.

Generation stages

Staged, dependency-ordered build plans — each stage declaring what it depends on, so a builder can render itself and refuse to run out of order.

Commands

The chat command set, and the /help listing rendered from it.

Parameter forms

The guided pre-generation form — which also writes the prose of the Parameters document, so the form and the document can't drift.

Facets and metrics

Facets are what the document browser filters on. Metrics are what charts plot. Deliberately different lists: a number you can chart is not automatically a number you should filter by.

Retrieval barriers

Every document carries a lens setting, or is left unscoped. The barrier strips out-of-lens material before context assembly. It is generic — it supports twenty lenses with no code change.