Musewoods publishes through four fields. They are not themes layered over one generic page model; each field owns a clear editorial purpose, content root, normalization boundary, validation contract, and renderer. What they share is platform infrastructure: global navigation, the Palette, common parsing primitives, the chart engine, and deliberately shared motif families.

The field decision should be made from the job the work must do. Stories tell by carrying a reader through a narrative argument. Journals examine through durable long-form prose and editorial annotation. Viewgraphs reveal through a fixed visual frame and presentation rhythm. Groves grow by turning a bounded body of work into a navigable place with its own identity and local structure.

Clearing, the Navigation System, and Resonance deliberately sit outside that choice. Clearing can assemble typed meaning and context across all four fields without owning the canonical editorial work. Trailheads can author journeys across the same fields, and Venture Trailmaps can represent the innovation field in which canonical objects, derived Waymarkers, evidence, contradictions, Trails, and Horizons relate. Resonance can circulate selected journeys and maintain explicit Follow relationships without turning circulation into another field root. These are system-layer responsibilities placed across the published objects below rather than additional publishing fields.

The specimens below are not screenshots of another implementation. Each uses the production parser and renderer for the field it represents, which makes the comparison useful both editorially and as a regression surface. The point is not that the four fields should look alike; it is that the same underlying platform discipline should remain visible through four different editorial jobs.

Purpose

An opening paragraph that can carry a drop cap — a Story setting a scene.

Authoring

### Intro
**Render:** lede
The opening paragraph of an act can take a drop cap.

Live Result

Contract & Implementation

Renders as ordinary prose with one typographic difference; no required fields.

• lib/render/motifs.mjs
• components/render/Motifs.tsx

Purpose

A `[!highlight]` callout — the Journal pausing to mark one passage as worth a second look.

Authoring

> [!highlight]
> A short passage the Journal wants the reader to notice.

Live Result

Contract & Implementation

Wraps ordinary prose/list content; no required fields beyond the marker itself.

• lib/journal/sidecars.mjs
• components/render/ContentBlocks.tsx

Musewoods shares parsing infrastructure without pretending that every field is the same document. Stories, Viewgraphs, and Groves use the Storyboard parser as their structural entry point and then normalize into different models. Journals use the more permissive Markdown-document path because Journal authors control prose structure directly. The commonality is therefore a parsing substrate and validation discipline; the editorial model becomes field-specific as soon as meaning requires it. Navigation and Resonance begin after canonical ownership is established. Trailheads can resolve canonical objects into a semantic journey, Trailmaps can reference them inside a graph-native innovation field, and Resonance can circulate selected work without importing field parsers or renderers into those system-layer models.

The same small subject — how authored source becomes a rendered page — exists in the Field Manual's unlisted demo content in all four field forms. The Story specimen turns it into a narrative with a movement spine; the Journal specimen examines it through prose and editorial markers; the Viewgraph specimen reveals it as a sequence of fixed-frame compositions; and this Grove turns the subject into a navigable reference place. Reading them side by side makes the field boundary concrete: the subject can remain the same while the editorial responsibility changes completely.