A 51,098-page directory release with a private publishing control plane

This one is a release rather than a rebuild of a product. At the recorded point the public site served 51,098 generated pages, produced 409,495 classified route outcomes, and carried 321,904 redirects tied to that observed release.

Every one of those numbers belongs to the public release. They do not describe the private control plane I built afterwards.

What changed

• I took the legacy request path out. Laravel and MariaDB stopped being in the way of a public page view; the site serves immutable output instead.
• An authoritative route and asset manifest decides what exists. A page that is not in the manifest is not served, which is what makes 409,495 route outcomes a checkable number rather than a hope.
• Media work that is bounded and restart-safe, with JPEG and WebP derivatives delivered through object storage and a CDN.

The private control plane

A separate operator application — Review, Listings, Sources, Queues, Publishing and Settings — manages the release. It has four private source adapters; at the recorded point one was approved by default and the other three failed closed until somebody configured them explicitly. A durable exact-duplicate ledger handles repeats, and similarity is only ever a hint for a reviewer.

Automatic publishing is off by default. Versioned validation, activation and rollback are required for a release to go out.

What it deliberately is not

No multi-tenancy, no user accounts, no payments and no messaging. The public release metrics say nothing about whether the later private adapters were all approved, or whether automatic publication was ever enabled, and this page does not claim either.