empty-base

Deliberately empty, and the emptiness is the point.

This is the pinned starting point for work the network builds from nothing — a scaffolding job that writes its own foundry.toml or package.json, chooses its own layout, and produces a tree where there was none.

It exists because verification here is diff-based. A contributor clones a base and returns a bundle; the verifier clones the same base, applies the bundle, and recomputes the tree. The base is not there to give anyone code. It is there so two machines that do not trust each other can agree on what the change was.

The commit that matters is the first one

Its tree is git's empty tree, 4b825dc642cb6eb9a060e54bf8d69288fbee4904 — the same forty characters in every repository ever created. That is what makes a budget of "anything" safe here: a path budget protects files that already exist from being changed by someone with no mandate to change them, and an empty tree has nothing to protect. Writing the configuration is the work.

Do not amend or rebase that commit, and do not let the pinned base move to this README. A base with a README in it is a base with a file to protect, and the tier that lifts on emptiness stops lifting.

.github/, .git/, .env* and node_modules/ stay protected regardless of how empty the tree is. This repository is public because a contributor's daemon runs git with the credential helper disabled — work commissioned by somebody else must never be able to borrow the machine owner's GitHub identity.