A Grove is a small, bounded, navigable website inside Musewoods. It can hold an idea, a venture, an institution, a research field, or another body of work that needs more structure than one article but less machinery than a separate application. Each Grove owns its identity, namespace, navigation, pages, visibility, and local assets while remaining inside the common Musewoods publishing system. This Field Manual is one such Grove, rendered on Soil.

The Guide's canopy mark belongs to that Grove identity and is declared in the manifest as both logo and identity.mark. It is therefore a masthead and navigation mark, not a decorative hero image attached to this page. The wider canopy.svg asset remains available later in this page only as authored media inside a feature-band specimen.

Grove publishing is governed by two different manifests that answer two different questions. The field-level content/groves/manifest.yaml owns the front door to the Groves field: its collection identity, entry presentation, and the explicit order of listed Groves. The manifest.yaml inside an individual Grove owns that Grove's local identity and behavior: its name, navigation, visibility, Ground, footer, logo, and related metadata.

The distinction prevents filesystem discovery from becoming accidental publishing policy. A Grove can exist and remain directly routable without being admitted to the /groves front door when its individual manifest sets visibility: unlisted. The Musewoods Resonance Grove uses that path intentionally. The separate content/resonance/manifest.yaml is not a third Grove manifest; it belongs to the cross-field Resonance circulation layer and must not be folded into Grove discovery or field navigation.

The field-level front door (/groves) is not a single view of the field — it holds four distinct jobs, each answering a different question about the same underlying entries (lib/groves/field-entry.mjs, lib/groves/woods-model.mjs):

• The Woods — What lives here? The canonical, identity-oriented

presentation: one spacious entry per Grove, its own title, description, and Now Growing. The default view.

• Terrain — What territory do they share? Groves grouped by the

shared territory they opt into (field.terrain, validated against the GROVE_TERRAINS registry in lib/groves/terrain.mjs). A Grove may inhabit more than one terrain, or none.

• Directory — Where is the Grove I need? The complete, compact,

retrieval-oriented index — the original field-entry presentation, unchanged, now one of three arrival views.

• The Canopy — What is alive right now? Not a fourth listing mode. A

quiet, present-tense read of the Woods, rendered server-side directly in the route (canopyModel, app/groves/[[...slug]]/page.tsx): a real Grove count, held as quiet contextual metadata, and a bounded slice of the Woods' current Now Growing — its principal, most visually emphasized content.

Search the Woods (searchGroveEntries) is one shared query that filters The Woods, Terrain, and Directory consistently — it is not a fifth view, and it shares one compositional region with the view switcher (GrovesArrival.tsx, [data-groves-controls]) rather than living as a separate toolbar.

Now Growing is the living-edge primitive this front door depends on. A Grove's own manifest may declare field.grow: { title, status } — its current inquiry, not a description of what the Grove is. Every surface that shows Now Growing (a Grove's own field-entry, The Woods, Terrain, and The Canopy) reads the same field.grow value through the same model; none of them derive or hardcode their own copy. A Grove with no field.grow simply contributes nothing to Now Growing anywhere — never a fabricated inquiry.

An artifact gives an authored image spatial authority while keeping ownership clear. Musewoods controls the caption, safe area, and surrounding rule, but the asset itself remains authored media: the renderer does not darken, invert, or recolor an SVG simply because the Grove is on Forest Floor. System-owned marks and interface surfaces consume Ground tokens; authored imagery keeps its own visual identity.

A Grove's directory is its local authoring boundary. Relative references stay inside that boundary, which makes the package portable and prevents one Grove from depending accidentally on another Grove's private asset tree.

content/groves/musewoods-field-manual/
├── manifest.yaml
├── index.md
├── publishing-fields.md
├── trailheads.md
├── trailmaps.md
├── ...one Markdown file per page
├── images/
│   ├── logo.png            512×512 canopy mark used by masthead/navigation
│   └── canopy.svg          authored wide media specimen
└── artifacts/
    ├── pipeline.svg
    └── reel-01.svg, reel-02.svg, reel-03.svg

A relative authored reference such as **Image:** images/logo.png passes through resolveGroveAssetRef and becomes a bounded /grove-assets/<slug>/... request served by the Grove asset route. The manifest logo contract is stricter than ordinary authored media: the identity mark must satisfy the platform's supported image-format and dimensions contract, while other local image and artifact references primarily need to resolve inside the Grove's asset boundary.