L7 — Multi-cloud / multi-platform solution

Status: Vision (grade a) — policy defined; max − 1 on the ladder; no implementation today. L7 stays flat — no sub-levels are defined for vision-stage levels, and no delivery at this scope is claimed or promised.

Updated

Level at a glance

Autonomous unit A whole engineered solution spanning clouds/platforms
What stays fixed Business framing
Human gate Strategic checkpoints

Canonical policy: Autonomy levels (Blueprints).


Building blocks at this level (planned)

Building block Planned role at L7 Handbook link
forge-platform Cross-product contracts; ecosystem_reference graph Ecosystem reference
forge-lenses Portfolio-level ForgeRun visibility Platform reference architecture §4
Forge Campaign Orchestrated campaigns across platform boundaries Forge Campaign
forge-fleet Execution on infrastructure you own per cloud Platform reference architecture §6
blueprints PDLC P1–P6; strategic checkpoints PDLC
Multiple product repos Lenses, Fleet, LCDL, KS, consumer sites Intersection map

Reference architecture flow (planned)

L7 multi-platform solution flow

How fixed business framing governs a whole engineered solution across clouds and platforms with strategic human checkpoints.

  1. [Business framing + strategic checkpoints]Business framing stays fixed while strategic checkpoints anchor executive gates.
  2. forge-platformecosystem_reference.v1 and cross-product contracts govern the portfolio graph.
  3. [cloud A]Fleet runners execute bounded jobs on the first cloud boundary.
  4. [cloud B]Fleet runners execute bounded jobs on the second cloud boundary.
  5. [on-prem]Fleet runners execute bounded jobs on owned on-prem infrastructure.
  6. Campaign stackForge Campaign coordinates L6 product increments across platform boundaries.
  7. Strategic review gatesHuman checkpoints review portfolio evidence beyond single-repo Assay.

Gates and evidence (vision)

Inherits L6 gates, plus:

  • Strategic checkpoints at platform/cloud boundaries
  • Business framing documented and unchanged without executive gate
  • No single-repo Assay suffices — portfolio evidence required

Implemented vs planned

Implemented Policy table row; ecosystem_reference JSON sample; multi-repo topology docs
Not implemented L7 autonomous delivery; cross-cloud orchestration
Planned Portfolio ForgeRun views; strategic checkpoint ceremony in blueprints