Reference architecture overview
This site is the public operating reference for new MNPPI projects. It explains the choices that affect design, delivery, and support.
The source standards remain in the internal org-standards repository.
This site presents those standards in a task-focused form.
Find the right section
Section titled “Find the right section”ArchitectureSelect a project profile and apply the Cloudflare platform baseline.
DeliverySeparate merge authority from production build and deployment.
OperationsUse isolated runners, useful telemetry, and tested recovery.
GovernanceReview the standard, record exceptions, and remove obsolete rules.
The default delivery model
Section titled “The default delivery model”| Stage | System | Required result |
|---|---|---|
| Pull request | GitHub Actions | Repository checks pass on the designated runner. |
| Merge | GitHub rulesets | Failed or missing required checks block the merge. |
| Production build | Cloudflare Workers Builds | Cloudflare builds the merged default branch. |
| Production deploy | Cloudflare | Cloudflare deploys only after its build passes. |
No default branch requires another person’s approval. The repository owner can merge after all required checks pass.
How to use the reference
Section titled “How to use the reference”Start with the adoption checklist. Select an application profile. Then review the applicable delivery and operations controls.
Record any necessary deviation through the exception process.