Target time: < 20 minutes
Frequency: When new chains appear, projects change status, or content needs updating.
- A new handoff chain completed in agent-brain (new roots or delegations in chain-registry.json)
- A project changed status (new project, phase complete, production launch)
- Content on a page needs a factual correction
- After a major agent system milestone worth documenting
cd /mnt/c/Users/eabfd/agent-brain
git pullCheck for new roots in watcher/chain-registry.json. If nothing changed and you're only updating content, skip to step 3.
cd /mnt/c/Users/eabfd/griffithee.github.io
python3 scripts/refresh-chains.pyThis reads agent-brain/watcher/chain-registry.json and regenerates data/chains.json.
Source discipline: See agent-brain/projects/autonomous-goal-execution/OPERATING-DISCIPLINE.md (Public visibility decision) and agent-brain/watcher/README.md (Public Chain Visualizer Curation). The registry is intentionally curated — not every handoff is added.
Verify: open data/chains.json and confirm the root count and descriptions look right.
If the registry path differs from the default (/mnt/c/Users/eabfd/agent-brain):
python3 scripts/refresh-chains.py --registry /path/to/chain-registry.jsonThe visualizer toolbar snapshot label now auto-updates from data/chains.json metadata.
If it looks wrong, fix the data refresh step instead of hand-editing the HTML label.
Edit data/projects.json to reflect current project state:
- Change
statusfield:"production","active","prototype","scaffolded" - Add new projects (follow the existing object schema)
- Update
"updated"field to today's date - Update
"desc"if the one-liner has changed
Corresponding long-form pages:
projects.html— SaveWisdom, Enough, agent-brain, tax-autofill, gene-toolbox detail sectionsexperiments.html— autonomy timeline, learnings, open questions
Common edit targets:
experiments.htmltimeline — add adoneitem for completed milestones, update theactiveitemexperiments.htmllearnings — add a new card for a non-obvious findingexperiments.htmlopen questions — move resolved questions to learnings; add new onesabout.html"Current focus" callout — update if focus has shiftedprojects.htmlprogress card for Enough — update prompt count, phase status
cd /mnt/c/Users/eabfd/griffithee.github.io
git diff --checkOpen the changed HTML files in a browser locally if you want to spot-check layout.
cd /mnt/c/Users/eabfd/griffithee.github.io
git add data/chains.json data/projects.json experiments.html projects.html about.html
git commit -m "Claude Code: refresh chains snapshot + project status"
git pushAdjust the git add list to only include files you actually changed.
GitHub Pages deploys automatically on push to master. Usually live within 1–2 minutes.
Check:
- https://griffithee.github.io/experiments.html — chain visualizer shows updated data
- https://griffithee.github.io/experiments.html#projects-browser — projects browser reflects changes
- No broken links or missing assets (quick scan is enough)
| What you're updating | File |
|---|---|
| Chain visualizer data | data/chains.json (run the script, don't hand-edit) |
| Projects browser data | data/projects.json |
| Long-form project write-ups | projects.html |
| Timeline, learnings, open questions | experiments.html |
| About / agent system narrative | about.html |
| Home hero / featured projects | index.html |
| Design system, global styles | css/style.css |
| Chain refresh script | scripts/refresh-chains.py |
If you want to hand the update ritual to Claude Code as a handoff:
From: Grok (or user)
To: Claude Code
Task: Run the update ritual for griffithee.github.io
1. git pull agent-brain
2. python3 scripts/refresh-chains.py
3. Update data/projects.json if any project status changed
4. git add changed files, commit, push
5. Verify GitHub Pages deployed
Claude Code can run this end-to-end via the watcher dispatch system.
Last tested: 2026-05-31 (Phase 3 deploy)