THE AGENT STRUCT
How the machines are wired
— autonomous or semi-autonomous systems run in this studio, across — projects and — repositories. This page is the structure. The full reasoning lives in the brain — an Obsidian vault you can read right here in the browser.
Every project, agent, system, technology and repository as a linked markdown note — with backlinks, tags, full-text search and a live link graph. A real Obsidian vault, rendered in the page.
ENTER THE BRAIN →Three tiers
SORTED BY HOW MUCH SUPERVISION EACH ONE NEEDSLOADING THE STRUCTURE…
What every agent here has in common
-
01
An isolation boundary
A git worktree, a container, a local model, a committed file. Nothing shares mutable state with anything else. The hard part of running several agents is not reasoning — it is write conflicts, and isolation deletes the problem rather than managing it.
WORKTREE WORKFLOW → -
02
A gate before consequence
Compile before write. Allowlist before call. Human before push. It turns "the model is usually right" into "the output is always valid", which is a different product entirely.
TOOL SAFETY → -
03
A written trail
Committed JSON, audit logs, git history. Every scheduled run in this studio ends as a diffable commit, so a regression is bisectable and an unrecorded action did not happen.
CRON LEDGER →
The shape that keeps repeating
THREE UNRELATED PRODUCTS, ONE MECHANISMcron (21:00 UTC) ──► stdlib python ──► JSON in /data ──► git commit [skip ci] ──► Pages redeploy
That is the entire studio backend. No server to keep alive, no database to back up, no bill when nobody visits — and every run is a commit you can diff, bisect and roll back. The daily AI signal, the daily One Piece character, the footy suite and this brain all run on it.
Everything built
ALL PUBLIC REPOS ↗Every project in the index, with the repository metadata behind it — swept from the GitHub API, not typed by hand.
| PROJECT | CATEGORY | STACK | AGENTS | REPO | LAST PUSH | STATUS |
|---|---|---|---|---|---|---|
| LOADING… | ||||||