the anchor it drew itself, and said so

A catalog cannot prove itself. Whatever sits at the root of authority has to be named, and the honest options are to name something external — which this design cannot supply — or to name itself, which is a statement about bootstrapping rather than a proof.

The tension is that the design needs a layer above dispute, while every candidate for that layer either regresses or is merely a convention. Making the catalog the arbiter of every reference is sound only until somebody asks who arbitrates the catalog.

The answer given is a self-reference: the first entry in the catalog always describes the catalog, and its recorded identity must match the actual one. The record states plainly that this self-reference is the root of trust, and then, rather than dressing it as a proof, keeps the unresolved part unresolved. The same record shows what happens when the catalog outgrows its own definition: it emits a handoff and a successor begins from a snapshot. That relocates the anchor instead of grounding it, and the decision log does not pretend otherwise.

What it costs is that participants must still accept one starting point by convention, and the record makes choosing that convention their visible problem rather than hiding it inside a proof. What it proves is that the team can document the step its own argument cannot take, and leave that step where reviewers can see it, alongside an open-questions list that still has entries in it.