Build, publish and roll back

A private workspace holds files, code and analysis. Publishing is a separate capability with an explicit destination and data classification.

Inspect the existing project. Build a scoped change. Run tests and scan generated files for private data and secrets. Commit an immutable revision, pass the release gate and publish through the registered path.

Verify the canonical URL, access policy and expected content. Record revision, deployment and rollback target. A preview URL is not automatically the finished company surface.

Public releases need a privacy review of source, assets and downloads. Internal tools need protected URLs. Test recovery before relying on it. Withdraw old public deployments when they expose deliberately removed material.