A shared rule reaches the project
The 20 September deployment protocol in the project’s operating instructions records the shared website standard: edit the authoring version first, mirror through the controlled tool, then use the established deployment route for an authorised release.
The standard also makes clear that the deployment mirror is not a second authoring workspace. A fix made there must be brought back into the source, or a later mirror can silently replace it with an older version.
Asset changes need visible identities
The mirroring process assigns local CSS and JavaScript references a version derived from their content. This connects an asset’s browser-facing address to the bytes being released. It avoids relying on a manually chosen version token that may not change when the underlying file does.
Revert and deletion checks serve a different purpose: they make unexpected replacement or removal visible before publication. This matters particularly where a public site shares a deployment with protected operational content.
A standard is not a site release
This entry records a change in the required release process. It does not claim that the Vox Liberata public website was redeployed on 20 September. The project’s current release state and any explicit review hold still determine whether publication is appropriate.
The economic value is reduced repetition and fewer opportunities for drift. A documented, verified path from source to public content makes routine updates easier to audit, while preserving the ability to hold a candidate for review.
Evidence for this entry
This account is grounded in project records. Internal research and operational files are not published here.
What the records support
- Source-first authoring, mirror tool, automatic cache busting and authorised deploy route.
- 20 September standard; read together with explicit local-only project hold.