pihme / hermetarium / marginalia / jigsaw

Jigsaw

Hermetarium is one piece of a growing family of projects, big and small. Here is how the pieces fit together, as seen from this one.

Fregoligrok-budget-mcpclaude-budget-mcpGit Wardenroom for the next pieceHermetarium▼ you are here
Part of HobelbankHow do you build software in the age of AI?

Hermetarium you are here

The world an agent wakes up in: an OCI image it may use freely as root, behind a wall with Squid as the only, logged way out.

Fregoli inhabitant

A web application an agent can rewrite while it is running: capabilities are Cordis plugins mounted and unmounted in a live Node process.

A would-be tenant from next door. Fregoli is a self-evolving web app whose own Docker image serves HTTP on port 8080 directly, no porter needed, and its docs name Hermetarium as the recommended, though optional, place to run it. It has not moved in yet: its image now listens on all interfaces and carries the ip tool, but running it inside a habitat end to end is still open work (hermetarium#10).

Git Warden possible guard post

Guard posts between AI agents and their Git remote: a Push Guard that checks every push with deterministic rules, and a Backup Guard that keeps an append-only backup of every branch and tag.

A guard post that could stand on this wall. Git Warden’s Push Guard is meant to run outside the agent’s environment, hold the only write credential for the Git remote and check every push with deterministic rules, while the agent pushes only to it; its spec names Hermetarium as one such environment. Like the keys Squid adds on the way out, the Git credential would then never enter the habitat. None of this is built or tested together yet.

grok-budget-mcp possible budget gauge

A small local MCP server that tells a Grok Build agent how much of its weekly usage pool is left, the same figure as /usage. Read-only, unofficial endpoint.

A small gauge that could serve this house in two ways; neither is built or tested yet. An inhabitant running Grok Build could load it as an MCP server and ask how much of the weekly pool is left. The image would hold only a placeholder auth.json, and Squid would add the operator’s short-lived grok login token from the ACL, as it does with vendor keys today. Or a watching agent on the host, next to the supervisor, could use it to decide when to put a habitat to sleep and when to wake it once the pool resets. The supervisor cannot do that yet: it has create and destroy, and keeping a changed world is not implemented (the spec leaves it open).

claude-budget-mcp kin

A small local MCP server that tells a Claude Code agent how much of its 5-hour and weekly usage limits is left, the same figures as /usage. Read-only, unofficial endpoint.

A fellow piece of the same puzzle; no direct connection yet.