Griffin Boneckberkeley
Berkeley’s sky · right now

Griffin Boneck — About

Builder-operator in Berkeley — landscape work on the hills, AI consulting, and software built solo.

Berkeley, California
What I do

The work

On the ground

Landscape work in the Berkeley hills — walls, patios, beds — slower builds at home in brick and concrete, and native plants.

At the keyboard

AI consulting, the digital side of a rights campaign, and software built because I wanted it to exist.

The direction

More of the week goes to software and consulting than a year ago. It is tracked as a share of hours, and the record below is the scoreboard.

Live · read from the log as this page loads

The record

From the ledger

Where the hours went

Loading…

Counted on the phone

Pushups & pullups

Weighed every morning

Putting on thirty pounds

Logged on the phone

Eating for it

Logged on the phone

Training

From the phone

Movement

From git

What got built

From the done list

Things finished

How these are counted

Things finished are the lines of the done list, counted when the site was last built. Hours come from a ledger and are round figures. Pushups are counted on the phone — the camera’s video never leaves it, only the number of reps; the counter was built on Sep 19, 2026 and there is no history before it. Pullups are typed in. The bulk is a weigh-in every morning, published only as pounds gained — a seven-day average against a straight line of 1.15 lb a week; the weight itself isn’t on this page. Calories and protein are each day’s totals as logged, or just whether the day made it. Commits are counted from local git history, filtered to one author, and from GitHub’s contribution calendar for the days this machine has no history for — where both know a day, the larger count is used, never the sum.

The rules

How I work

The machine

How the site works

01Three things a week
The week's page has three slots. A fourth gets questioned.
02One assignment per project
One text file per project, with one line in it for the thing that moves it.
03Log as you go
One CSV, one line per block of work. The record above is that file, drawn.
04Capture now, decide weekly
One inbox file. The weekly review empties it, every time.
05Active means touched in fourteen days
The build flags anything older until it is parked or done.
06Keep what you stopped
Stopped and finished projects stay listed, dimmed. The full list is at the bottom.

All of it is plain text: 28 markdown files and one CSV of hours. 22,400 lines of Python with no packages installed turn that into these pages, 27 hand-built scenes included. Most edits are made by telling an AI agent what happened. The view across the Bay is drawn in code and lit by Berkeley's real sky — no photograph, no map file, no tracker.

Live elsewhere — Come By ↗ Ledger · Citizen ↗ Signal Blueprint (consulting) ↗ Unite for Rights ↗ UNSEEN ↗ YAW · Drift Brain ↗

Everything, by area28 projects, counted from the project files

Every project is here, including what is parked and what was stopped. Each name opens its page.