Four bots and a forge
I run my week with a small crew of bots. Each has one job. Each has a name from Thor's world, so I remember the job from the name.
- Gná
- The coordinator. Frigg's messenger, who rides between the worlds. Plans for the day and the week pass through her, and she hands the work to the others.
- Nidavellir
- The motivator. He nags me to exercise. He is named for the dwarf forge world because a forge that goes cold is exactly the risk.
- Heimdall
- The seer. He watches what is coming so the week does not surprise me.
- Eitri
- The taskmaster. He keeps Renzy, my mobile game, moving.
Why a forge on this page
The bot nags. The page shows whether the nagging worked. Every workout I log feeds the fire. A hard session in the red zone fills it almost to supernova. The fire loses ten points a night, or only four when a Monday, Wednesday or Friday is close. After seven days without a session it goes cold, and one new session reignites it.
The tracker runs on my Mac. When I log a session it publishes a tiny file to this page. The file holds the charge, the date of my last session, and the rules the forge follows. It never holds calories, notes or heart rate. This page then works out how much the fire has cooled since, so it stays honest between updates.
Two Nidavellirs
This page is the forge world. The bot is the one who nags me to keep it lit. Same name, two jobs, and I liked it too much to use only once. The smith is out of frame here. What you are looking at is his workshop, and whether anyone has been working in it.
Why Grok runs the crew and Claude does not
Claude Code lives in my repos. It reads the code, changes it and runs the tests. That is a workshop. Grok runs the floor around the workshop. It plans, reminds and keeps the crew coordinated. Different jobs need different tools, so I keep them apart on purpose. The workshop never nags me, and the crew never edits code.