One example, the community garden, declared a little at a time. Every chapter below is a real declaration that passes its own check, opened in a real browser by scripts/progression.mjs on every push. Nothing here is a mock-up; a chapter that stops holding its claim fails the build.

Chapter one is what graview create writes. The loop from there is the whole method: declare, check, look, declare more.

Eleven packages, layered. Take the whole stack or take the parts that earn their place. layout is pure geometry with no React in it; core runs headless in a worker or a test; embed puts an app on somebody else's page.

The repository also carries example apps. They are fixtures for the harnesses and are not published.

A view further away is not drawn smaller. It is asked for less. That split carries real weight: capture runs about 0.016 ms per node up to roughly 128 live captures a frame, then falls off a cliff.

A lens binds roles, not field names. Point the timeline at plannedAt in one app and at leaveAt in another; it never learns what either one means. That is the line between a lens and a component you copied. The garden proves it twice: the coverage grid, written for requirements and tests, shows which plot nobody tends; the board, written for a seating plan, shows what grows where — and the empty bed.

Lenses are yours to make. A lens is an ordinary React component that takes the nodes, the bindings and the selection the framework hands it, and draws whatever your domain needs to see — a map, a ledger, a floor plan, a Gantt of the week. Register it over a kind with a title and it is a named place in the bar; every mark it draws is a real pick target, so selection, ties and actions land on the things themselves. Chapter thirteen is the garden drawing itself: beds as beds, a sprout per planting, and the same drawing on the home page of a pages face that replaced every surface. The core ships with three starters — the board, the coverage grid and the timeline — as the shapes most domains reach for first, and every one of them is one file you can read and copy.

Everything the scene draws that is not a view is declared on the brand: the lines, their route and their stroke, the ground's grid and lattice, the kind tags, the captions. A route is a named strategy — curve, straight, right-angled — and the next one is one case in one file. Colour and visibility are per edge kind. Try it on the garden after chapter eight: the declaration you are writing is beside it, and the checker's verdict on any colour you pick is under that.

kit: {}

Who is here is in the graph too. Users, invitations and the roles they hold are nodes and acts like everything else: judged by the policy, offered in the strip and the pages, written to the log. The seat that keeps the installation sees "Show the installation" in the bar and the people rise as districts beside the domain; nobody else ever sees them. A person's record is their profile and theirs alone to edit. Chapter fourteen is the garden with its gardeners at the keyboard, and a lens over the policy that says what each role reaches.

The declaration is a graph too. In the studio every kind, field, edge, act, rule, role and grant is a node, and a change to the declaration is an act with an author, an intent and an inverse. The checker judges what it would become before it is applied; a stored graph gets the migration it needs; the result is written back as the files graview create writes. An agent seat proposes by acting, and a person keeps or takes back its turn. Chapter fifteen is the garden's own declaration, open in the studio.