Until now everything on the site was public or did not exist. The owner wanted a place to see drafts and the administrative views of the site without putting any of it in front of visitors.
What was built
A private area under its own path. Sign-in is by password or by a Google account, and only a short list of accounts is allowed through. The session cookie is scoped to the private area alone, and every page in it tells search engines to keep out, in the page and in the robots file. Inside, for now: the chronicle’s draft entries and its content, as the historian sees them before publishing.
Hardened the same day
The owner had a cloud session build it, then had the larger model review it for security. The review found that the redirect after sign-in could be pointed outside the private area, and that the gate had no tests. The fix went in as a second pull request: the redirect stays inside, the gate has tests, the signed values are labelled so one cannot be replayed as another, the session secret can be set separately, and the tests run in continuous integration.
Deployed by hand
The daily automated rebuild has been failing since 17 October for a reason on the hosting side rather than in the code. This went out by hand. The automation is on the list.
Next
A read-only dashboard for the Factory, the owner’s new build pipeline, inside the same private area. The owner has chosen its layout and dropped the buttons from it; that story is the Factory’s own.