Seven days elapsed between the start of this build and the current public-MVP release. Before this release, the accepted-deployment count was zero.
The count is Day 07.
The earlier public page called the record Day 01. That framing erased six elapsed days and converted delay into a fresh start. It has been retired.
The corrected chronology is direct: this is Day 07. Days 01 through 06 happened. They contained work, attempts, commits, private builds and infrastructure changes. They did not produce an accepted public MVP.
Elapsed time counts even when the deployment does not.
What did not count.
The following artifacts can support a deployment, but none is a deployment by itself:
- A screenshot. It shows one rendered moment, not a public route the reader can open.
- A GitHub commit. It proves source changed, not that the custom domain serves the change.
- A private preview. It can validate protected operations, but it does not satisfy the public-site requirement.
- A partial page. A homepage without the project routes, archives, search index and sitemap is not the requested MVP.
The acceptance gate.
Deployment 01 is accepted only when the custom domain serves the complete public route inventory over HTTPS; every sitemap URL returns successfully; released articles appear in the Journal, Newsletter and RSS feed; site search finds every public module; mobile navigation works; and private records remain absent.
Those checks passed on nyfholdings.ca at 12:03:06 MDT on August 14, 2026. Deployment 01 is now the first accepted public MVP; the prior count of zero remains in the record.
What the public MVP contains.
The public layer contains the company, five project pages, two editorial series, their archives, the free Journal, the Newsletter, the Method, the public operating-system map, the build log and site search.
The private layer contains CRM contacts, body and movement notes, financial events, source evidence, private drafts and unified operational records. Making the MVP public does not require publishing those records.
The permanent log.
The public build log begins with the uncomfortable fact: zero accepted deployments across the first seven elapsed days. It then records Deployment 01 and its verification time. Its purpose is to prevent a screenshot, a commit or a private preview from being substituted for the public outcome again.