A broader local structure
The August v8 work expanded the public website into a multi-page local candidate. It introduced shared navigation and styles, supporting information pages, a sitemap and robots instructions. The work also recorded a content-evidence ledger to distinguish supported public statements from material that should remain excluded.
The resulting source was mirrored into the local deployment work tree for preview. The session explicitly recorded that it was uncommitted and unpushed.
Three states to keep distinct
An authored folder, a local deployment mirror and a live website are three different states. Copying files between the first two does not make the third change. This can be easy to miss when a local preview looks complete and uses the same navigation as a public site.
The v8 record included checks of the local pages and hashes showing source-to-mirror agreement. Those checks established properties of the preview. They did not establish public availability.
Protect what the redesign does not own
The private intranet, middleware and response headers were checked as preserved during the public preview work. That was necessary because a public information-architecture experiment shared a deployment area with an operational private system.
V8’s next step remained visual review followed by an explicit publication instruction. V7 continued to be the public release. The useful lesson is simple: a release record should say where a change exists, not just that it has been built.
Evidence for this entry
This account is grounded in project records. Internal research and operational files are not published here.
What the records support
- V8 local mirrored preview; uncommitted/unpushed; protected surfaces preserved.