Example project — Frond is not real.
Authored demo content for a fictional plant-care app, rendered by the same parsers and held to the same invariants as a real project's dashboard. This is the system in use, three months in.
Structure
What the project is made of — the features, the strategy, the docs, the shipped record.
Features5What it does — one current-state spec per capability, grouped by the areas the docs declare.Strategy3What we believe — settled models, drafts, interview kits, research, each with its thesis.Docs21What we've written — every live doc by review tier. 7 working · 13 commitments · 1 bedrock.StyleguideDesign systemHow it looks — colors, type, layout, components. Derived from globals.css and the shared components on every build.
Timeline
all 3 →What shipped, newest first.
- Sep 1Room light survey (closed)
- Aug 27Onboarding v1 (closed)
- Aug 20Plant profiles (closed)
Decisions
all 6 →Why things are the way they are.
- Sep 5Reminders are a daily digest, not per-plant pushes
- Sep 1Light readings are a range, never a number
- Aug 27One plant before any account
- Aug 20Species data is licensed, not curated
The site itself: the route tree — no routes directory declared. A run's close reconciles its picture against it.
Nothing starts settled — docs sink toward bedrock by surviving contact; reopening a settled one takes a structured challenge.