# Case study: a bounded static deployment path

The historical workflow connected dependency installation, project validation, a static build, a dist plus index.html output gate, an OIDC login step, and an authenticated upload to the static web container. The archive also contains page smoke-test evidence for the home page, About page, Projects page, Privacy page, and a custom 404 page.

The deployment is presented as a student portfolio and cloud-experiment implementation. The archived result is not an enterprise production claim and does not establish future run reliability, high-concurrency behavior, disaster recovery, WAF, CDN, custom-domain behavior, or continuous monitoring.

The useful engineering pattern is the separation of build validation from upload authorization. The workflow checks that a build exists and that its entry file is present before the upload step. Authentication is represented as an OIDC flow with a user-assigned managed identity and scoped role-based access.

The package uses only a previously saved local archive. It does not access GitHub, Azure, or an online site. Every screenshot derivative is a static display artifact; it does not independently prove configuration details that are not visible in that image.