The Forest Floor Laboratory
A whole Grove can choose the ground in which its idea lives.
- Forest Floor Ground
- One coordinated token set
- Zero separate dark components
This Grove is authored ground: forest-floor in its manifest. Everything below — the front door, this local navigation, the prose, the links, the rules, the feature-band, the quote-panels, the reels, the D3 chart and its interaction states, the Mermaid diagram, the images, and the footer — renders from the same motif components a Soil Grove uses. Nothing here is a dark-mode variant; the Ground is a coordinated set of tokens the whole environment reads.
What Forest Floor Is
Forest Floor is an earthy inverse analytical environment — charcoal soil, warm ivory, moss, seed, mineral.
It is not browser dark mode, not a user preference, and not a global Musewoods theme. It is an authored editorial property of this one Grove, and it is bounded to it: the Story, Journal, and Viewgraphs surfaces, and every Soil Grove, are untouched. Its palette is Musewoods Palette v1 — the Inverse analytical surface that already renders dark Viewgraph diagrams, promoted here to a full editorial ground.
How the Ground Resolves
A Grove's manifest carries a ground block. Adding mode: forest-floor to it is the only authored change; omitting it, as every existing Grove does, resolves to soil and looks exactly as it does today. The resolver in lib/groves/ground.mjs normalises that value on the server, so the correct Ground is already in the first byte of HTML — there is no flash from Soil to Forest Floor on load.
Beneath the data-ground="forest-floor" boundary on the Grove root, one CSS block re-tones the shell contract, the section tokens the shared chart and Mermaid engine reads, and the warm-paper editorial aliases. Components never branch on the Ground name; they read semantic tokens and follow. A component that needed a separate Forest Floor version would be using the wrong abstraction.
The Processing Pipeline
The authored SVG keeps its own identity on Forest Floor. Musewoods governs presentation — the caption tone, the safe area, the rule above the figure — but it never darkens, inverts, or filters an authored artifact. Only system-owned marks consume Ground tokens.
How the Motifs Relate
resolver
resolveGroveGroundturnsmanifest.groundinto a normalized Ground id and is the only place that decision is made.Relates to tokens, shell
tokens
One coordinated set — foreground, surface, rule, accent — re-toned under the
data-groundboundary. Foreground and surface always move together.Relates to resolver, motifs
shell
The Grove shell carries
data-groundon its bounded root; the front door, navigation, and footer all read the Ground contract.Relates to resolver, motifs
motifs
feature-band, quote-panel, reel, chart, and the native Grove motifs all consume the semantic tokens. None of them know which Ground they are in.
Relates to tokens, shell
analytical
D3 and Mermaid render on a paired analytical surface — foreground and surface bound together — so a label is never light-on-light or dark-on-dark.
Relates to tokens
A Diagram, In the Ground
A Mermaid diagram inside a Forest Floor Grove renders on the canonical Inverse analytical surface — the same dark-forest node, warm ivory label, and mineral rule a Viewgraph uses. It is not a second Mermaid dark theme.
Figure 1
Rendering diagram…
An Update, As a Feature Band
The shared motif layer is Ground-aware
feature-band, quote-panel, and reel now read the Ground contract. On Forest Floor the surrounding text, rule, and link environment is re-toned; the authored image is never placed in a glowing card or inverted.
A Founder Voice, Attributed
The point was never a darker website. It was a place inside Musewoods where dense analytical work feels like it belongs.
A Grove authorMusewoods PressA Field Statement, Unattributed
A Ground is chosen, not toggled. It says where the idea lives, and the whole local site lives there with it.
Field Observations, As an Image Reel
A bounded sequence of authored studies. The reel viewport, the controls, the position counter, and the captions are Forest Floor; the authored images are not recoloured.
First observation.
A Referenced Viewgraph, As a Reel
Reel reference
Where the pattern begins
A title frame, reused whole inside a Reel viewport.
Three canonical frames from an existing Viewgraph. The Reel viewport and controls are Forest Floor; the referenced Viewgraph frame keeps its own presentation contract — Ground stops at the viewport.
From the Journal
- Ana: When Retrieval Was No Longer EnoughA development Fieldnote tracing Ana from its GraphRAG-oriented beginnings through governed knowledge formation, memory, Knowledge Spaces, Domain Packs, Workbench, canonical reference integrity, and cross-canon contracts.
- Context Is Part of the RuntimeAn engineering Fieldnote on what Codex operating practices reveal about context entropy, working memory, tool exposure, handoffs, skills, and the emerging discipline of engineering the runtime around an intelligent agent.
- The Executive Becomes a Systems ComposerA Fieldnote prompted by Bob Morse's experiment with Claude Code, examining what happens when deep domain judgment can increasingly become executable and what that may mean for the RPM Machine.