How the Auto-Host Chain Works

This is the second page of the auto-host verification site. Its job is to prove one specific rule: when a site gains additional pages, the workspace top menu does not gain additional entries. The menu lists sites, not pages.

The dedupe rule

Every published page triggers the same bookkeeping step. That step always records the site's root address, never the address of the individual page that was just written. The menu bridge checks the existing entries by name and address before adding anything, so a second page of a known site resolves to an entry that already exists and is skipped.

The site registry follows the same convention. The registry row for this site points at the site root, with the most recently published page kept as a sample reference. One site, one row, one menu entry, regardless of how many pages it grows.

Why this matters

The pipeline is about to be used at much higher volume, where a single client project can produce a large number of individually addressed pages. Without the site-level rule, every one of those pages would surface in the shared navigation of the team workspace and make it unusable. With the rule in place, volume changes nothing: the navigation shows each property once.

The first page of this site describes the whole chain from authoring to publication; read it at the pipeline proof home page. The main company site remains the reference for the broader system at b2bgrowth.systems.