← Back to Reactor Programs

Phase 7 • Release Certification & Production Integration

Reactor Programs Release Certification

Phase 7 freezes the branch for deployment as a publication-controlled release candidate. It verifies branch structure, routing, metadata, maturity labels, terminology authority, accessibility essentials, asset references, release traceability, and the production boundary between Reactor Programs and the parent Aurora website.

Important: certification does not mean the public website has already been replaced. The release candidate must still be uploaded into the production webroot and the live URLs checked after deployment.
Release Gate

Certification matrix

GateStatusRelease requirement
Branch routingPASSAll internal Reactor Programs links and branch assets resolve inside the release candidate.
Legacy aliasesPASSindex1/index2/index3 remain noindex compatibility redirects to Fission, Fusion, and Specialized gateways.
Publication authorityPASSPhase 6 source hierarchy, terminology lock, maturity controls, and canonical metadata retained.
Accessibility essentialsPASSViewport metadata, image alt text, skip links, headings, and nonempty href/src references checked.
Visual architecturePASSApproved full-width hero renderings and three-card desktop hierarchy retained.
Production dependenciesPASS / EXTERNALParent-site CSS, global navigation/search targets, and Aurora logo are intentionally not duplicated in this branch overlay.
Live deploymentPOST-UPLOAD CHECKProduction URL, canonical, cache, responsive rendering, and live navigation must be rechecked after upload.
Release Architecture

What is frozen in Phase 7

Information architecture

Reactor Programs → Fission / Fusion / Specialized → daughter technology pages, supported by comparison, glossary, safety, publication authority, and release certification pages.

Technical publication controls

Phase 4 terminology and education, Phase 5 lifecycle/safety claims discipline, and Phase 6 evidence hierarchy remain controlling.

Deployment boundary

This ZIP is an overlay rooted at /sustainability-infrastructure/. Shared global site assets remain owned by the parent website and are referenced rather than copied.

Deployment Procedure

Production integration sequence

  1. Back up the existing production /sustainability-infrastructure/neighborhood-reactor/ branch.
  2. Overlay the Phase 7 /sustainability-infrastructure/ folder at the website root without deleting unrelated parent-site assets.
  3. Preserve existing global CSS, search, navigation, logo, and sitewide assets outside this release package.
  4. Clear host/CDN caches as appropriate.
  5. Verify the Reactor Programs main URL, Fission/Fusion/Specialized gateways, representative daughter pages, glossary, safety, publication authority, and this release page at desktop/tablet/mobile widths.
  6. Confirm canonical URLs, images, and external evidence links from the live host.
Authority Links

Release references