Delivery platform README

The delivery-platform module teaches the current path from change to validated artifact to environment. It starts with the actual repos instead of a vendor tour: fos-workbench publishes tutorial/docs and analytical surfaces, while the sibling fos repo validates and releases an application.

This module is tied to PRD #163. It is separate from deployment operations: deployment operations covers runtime packaging and operator targets; delivery platform covers CI, CD, gates, artifacts, environments, promotion, policy, secrets, observability, and feedback.

Boundary

Azure is not part of the current delivery-platform operating model. Azure files in this repo are deployment-target validation and historical context, not the way fos-workbench tutorial/docs or the sibling fos app currently ship.

Sandcastle is also not CI/CD. It is issue-to-PR and branch automation that feeds GitHub Actions, where validation, deployment, gates, artifacts, and smoke checks happen.

Lessons

• L00 - Current pipeline map distinguishes the fos-workbench tutorial/docs publishing path from the sibling fos staging and production application release path.
• L01 - CI/CD pipeline anatomy explains triggers, jobs, steps, gates, artifacts, secrets, environments, deployment jobs, smoke checks, and failure modes using the lab workflows as the example.
• L02 - Delivery catalog introduces a multirepo delivery catalog exercise for ownership, build/test commands, artifact contracts, environments, deploy triggers, secrets boundaries, smoke checks, and self-service CI/CD vocabulary.
• L03 - Platform patterns compares the current setup with polished delivery-platform patterns for reusable workflows, change detection, build graphs, immutable artifacts, environment promotion, deployment controllers, policy gates, observability, rollback, and self-service templates.

The source module lives in tutorial/delivery-platform/.