Skip to content

The codebase manager

Partly built

A read-only view of projects, branches, the promotion queue, history and libraries, written in Clay; and the text mirror that keeps git canonical.

The codebase manager is where you look at what changed in a codebase, not at the text of it. It lives at code.withclay.org (locally, cd packages/codebase && npm run dev, port 5175). Its screens are written in Clay with JSX and run in your page; the data comes from the same planner that clay promote plan uses.

  • Queue. One card per slice of work that could be promoted into main: a risk badge, what kind of change it is, how many dependents are re-derived (counted, never listed one by one), who made it, and a dry run on a scratch copy. A change the target also made differently is shown as blocked.
  • Slice review. The real edits of one slice, the signature change, the abilities added, and the text diff. Text from a branch is data: it is shown as plain text and never decides anything.
  • History. Two timelines: what was adopted into the target, and how a branch was written (its journal, with who or which agent), plus the hash lineage of a definition.
  • Branches, Libraries, Policy, Changesets. Libraries show the per-branch pin table, with vendored libraries keeping their upstream. Policy and changesets are not built; those screens say so instead of inventing rules.

It is read-only and git stays canonical: this project’s own Clay code is kept as text files in git. clay mirror imports those files into a store and exports them back byte for byte, clay mirror check proves it, and the Git mirror tab shows each file as matches git or diverges from git. A change made in the store leaves as a patch (clay mirror patch | git apply).

See docs/codebase-manager.md in the repository for the design, the migration gates and the hosting steps.