Field Notes

source

Feature-driven wiki mockups

StatusStableUpdatedStands on17 sourcesSupportsnotes

Sixteen generated images from 2026-07-21, produced by running eight prompts through two image models and importing the results. The set inverts the method of Style-led wiki redesign mockups: where those explored visual style with the feature set held fixed, these were written from the wiki’s features — lifecycle states, redlinks, provenance, tags, questions, note types, the link graph, and embedded diagrams — with no reference to the interface that existed.

Each subject was rendered twice, once per model, which makes the pairs useful in a way a single image is not: where the two models agree, the agreement is a property of the prompt rather than of one model’s habits.

The provenance and citation trail mockup, tracing a claim from its note-level sources to a footnote to an archived artifact

Subject Images
Lifecycle-first note view one, two
Redlink research queue one, two
Provenance and citation trail one, two
Tag merge-candidate audit one, two
Question-note frontier one, two
Type-aware note composer one, two
Link-graph cluster explorer one, two
Diagram and chart embedded in a note one, two

Half the set describes software the wiki is not. The tag audit, the note composer, the question frontier drawn as a board, and the cluster explorer drawn as a live filtering dashboard all assume persistent state and mutating controls — merge buttons, draft saves, live filters — which a statically rendered site cannot provide, and which in this wiki are just commands run by an agent rather than screens a reader operates. They read as alternative interfaces to the maintenance workflows described in Build and rendering pipeline, not as proposals for the reading surface.

Three carried ideas that survived into the reading interface. The lifecycle view turns the working and stale states described in Note lifecycle into callouts with real content — a named gap, a named unsafe claim — rather than a badge that only encodes a word. The provenance trail distinguishes the frontmatter sources inventory from claim-level footnotes as separate visual tiers, which is exactly the distinction drawn in Linking and citation conventions, and extends it to the archived artifact behind the citation. The redlink images show the linking sentence beside an unresolved wikilink, which suggests how a redlink might carry its own context inline.

Reading interface redesign proposals records which of these ideas were adopted.

Built on 17 sources (17 archived here).

Working out connections…