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 — the registry as a product map: the funnel, the identity backbone, the demo layer.Strategy3What we believe — settled models, drafts, interview kits, research, each with its thesis.Docs19What we've written — every live doc by review tier. 1 surface · 6 working · 11 commitments · 1 bedrock.StyleguideDesign systemHow it looks — colors, type, tokens, components. Hand-authored today; its derive-from-globals.css refresh is queued.

Timeline

all 3 →

What shipped, newest first.

  • Jul 14Room light survey (closed)
  • Jul 9Onboarding v1 (closed)
  • Jul 2Plant profiles (closed)

Decisions

all 6 →

Why things are the way they are.

  • Jul 18Reminders are a daily digest, not per-plant pushes
  • Jul 14Light readings are a range, never a number
  • Jul 9One plant before any account
  • Jul 2Species data is licensed, not curated

Nothing starts settled — docs sink toward bedrock by surviving contact; reopening a settled one takes a structured challenge.