Merge pull request 'feat: every Operational requirement verified by a Check; eval spread, report and published runs' (#1) from feat/eval-coverage-and-spread into main

Reviewed-on: #1
This commit was merged in pull request #1.
This commit is contained in:
2026-10-23 17:30:05 +00:00
206 changed files with 41449 additions and 25 deletions

View File

@@ -29,3 +29,4 @@
| T12 | The rate card Skill's format and checks | built (`steps/step-1.md`) |
| T13 | Staffing and cost in code | built (`steps/step-1.md`) |
| T14 | Evaluation with real models | built; two cases passed (`steps/step-2.md`) |
| T15 | Every Operational requirement verified by a Check; the spread of repeated runs; a report to publish | A requirement no Check verifies is refused; three runs of each case report their spread | built (`steps/step-4.md`); run 2026-10-21: five of six passed, every requirement verified; through the Orchestration engine from the solution architecture agent, completed |

View File

@@ -65,3 +65,14 @@ It also filed a gap in its own model as a finding: service continuity staffed on
- **The architect is told** what a finding is and is not.
177 tests pass. Not yet run with real models.
## Case 02 after findings were kept to the solution, 2026-10-14 16:28
Recorded 2026-10-21 from `eval/results/20261014T162852Z/`. Case 02 passed every check in 15.1 minutes: 9 Items, 16 Operational requirements, 21 Capabilities, 11 Roles, 13 Checks, 33 of 33 scenarios, no findings, 3 business outcomes and 6 Measures, 12.8 people at 92,903 GBP a month, one Revision of the operating model.
Read against the runs before it, two things the checks did not show:
- **Cost moved 55% between two runs of the same case** (59,997 GBP at 13:26, 92,903 GBP at 16:28), with 6 Roles against 11. Staffing and cost are computed, so the spread is the model's design, not the arithmetic. Nothing measured it.
- **Three Operational requirements were verified by no Check** (OR-14 the sourcing model, OR-15 the delivery countries, OR-16 the tooling), each served by a Capability. Six of the nine runs of 2026-10-13 and 14 left at least one so. The design required each requirement to be served by a Capability, not verified by a Check, and Checks fell from 31 to 36 a run to 13 or 14 once business outcomes came in.
Both are taken up in step 4.

View File

@@ -0,0 +1,43 @@
# Step 4: every requirement verified, and the spread of repeated runs
Built 2026-10-21 on `feat/eval-coverage-and-spread`, at the owner's request, after reading the run of 2026-10-14 16:28 (`step-3.md`).
## What was built
- **Every Operational requirement is verified by a Check** (`graph.py`): one whose `source` is the requirement, or a Condition it comes from. A Target operating model that leaves one unverified is refused, naming it. The architect's instructions say so, with how organisation and tooling requirements are verified; the `operating-chain` Skill lists the refusal. The test fixture had the same gap (OR-4, OR-5) and gained the two Checks.
- **The evaluation:**
- a check that every Operational requirement is verified, naming those that are not, and `requirements_unverified` among the figures;
- `--repeat N`: each case run N times under its own Execution, `<case>-r<n>`;
- `spread.json`: for each case run more than once, least, most, mean and range of the mean, of people, cost a month, Roles, Checks and Capabilities. Reported, not failed;
- `report.md`: the run as a report that can be published, with each run's result, the checks that failed and the spread;
- each result's folder relative to the run's: results are published, and hold no path of the machine they ran on.
## Verified
184 tests pass; `ruff` and `mypy` clean. With no model: the benchmark architecture from the fixture, with case 02's operating fields, starts a pre-approved Execution.
## The runs, 2026-10-21
### Both cases three times (`eval/results/20261021T203624Z/`)
| Case | Run | Result | Minutes | Revisions | Requirements verified | Roles | People | Cost a month |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 01, written spec | 1 | pass | 18.8 | 1 | 10 of 10 | 5 | 6.8 | 46,252 GBP |
| 01 | 2 | pass | 17.1 | 1 | 9 of 9 | 7 | 11.0 | 44,720 GBP |
| 01 | 3 | pass | 20.2 | 1 | 10 of 10 | 6 | 11.4 | 47,603 GBP |
| 02, digested architecture | 1 | **fail** | 50.4 | 5 | 17 of 17 | 8 | 11.7 | 73,863 GBP |
| 02 | 2 | pass | 20.9 | 1 | 15 of 15 | 6 | 10.8 | 83,846 GBP |
| 02 | 3 | pass | 24.4 | 2 | 15 of 15 | 8 | 16.9 | 116,409 GBP |
- **Every requirement was verified in every run.** Checks rose to 15 to 20 a run, from 13 or 14.
- **Case 02, run 1 ended with warnings** at the operating model's revision limit. The validator failed five Checks whose words the Capability they are on does not bear out: "continuously maintained" and "continuously reviewed" on Capabilities staffed in business hours, a 10-week validation on the Capability that manages the roadmap rather than the one that delivers, sign-off the Capability does not mention, and alignment with DORA, PCI DSS and ISO 27001 on a Capability covering PCI DSS alone. Four of the five come from Conditions, not requirements: the weakness of step 3 ("a Check whose hours or Capability did not fit"), not the new rule.
- **The spread:** case 01's cost moved 6.2% across its runs while its people moved 47.3%: more people, cheaper. Case 02's cost moved 46.6% (73,863 to 116,409 GBP) and its people 46.4%; Roles 27 to 33%, Checks 17 to 25%; Capabilities not at all (21 each time).
### Through the Orchestration engine from the solution architecture agent (`eval/results/20261021T203623Z-handoff/`)
One pre-approved request for `architecture_and_operating_model`, Customer case `case-08-landing-zone`, from the benchmark landing-zone spec, with case 02's operating fields under `operating_model`. Completed in 74.9 minutes: the architecture in about 50, its 15 kept files given to this agent as `sources`, which digested them (`metadata.source: architecture:6c316f05…`) and completed: 24 Operational requirements, all verified, 21 Capabilities, 8 Roles, 26 Checks, 44 of 44 scenarios, 12.2 people at 87,959 GBP a month. Both Executions' files are kept in the Orchestration engine's store (MinIO, 28 objects) and were fetched through their links. The signatures were taken off the links in the results before publishing.
## What remains
- **The spread is the larger finding.** The same architecture costs between 74 and 116 thousand GBP a month across three runs. The figures are computed; the design is not stable. What moves is the Roles and how work is shared between them.
- **Checks that the Capability they are on cannot bear out** end a run at its revision limit about one time in three for case 02. A data check that refuses a "continuous" or 24x7 Check on a Capability whose hours are narrower would catch the commonest of them before validation.

9
.gitignore vendored
View File

@@ -19,8 +19,13 @@ venv/
# name people, teams and suppliers
deliverables/
# Evaluation run outputs
eval/results/
# Evaluation run outputs, but for the runs published (they hold fictional benchmark
# data only, and links without their signatures)
eval/results/*
!eval/results/20261021T203624Z/
!eval/results/20261021T203623Z-handoff/
!eval/results/20261021T203624Z/deliverables/
!eval/results/20261021T203624Z/deliverables/**/deliverables/
# Lesson candidates captured from Executions (may quote user feedback)
lessons/candidates/

View File

@@ -62,6 +62,7 @@ Checks:
- A Check is a condition that can be shown to hold or not, on a Capability, a Role or a Responsibility. Its `source` is the Operational requirement or the Condition it comes from.
- Every Condition in `scope.stated.solution.conditions` must be carried by at least one Check whose `source` is that Condition's id.
- Every Operational requirement must be verified by at least one Check: one whose `source` is the requirement's id, or the id of a Condition the requirement comes from. Organisation and tooling requirements need one too: a requirement that staff work only from certain countries is verified by a Check on the Roles' countries, one that tooling is integrated by a Check on the Capability that runs it.
- Start from the catalogue's `typical_checks` and rewrite each for this solution, with the customer's own numbers.
- Put a Check on the Capability that does the work it describes. A Check that service is restored within four hours is on the Capability that restores it, not on the one that reports service levels.

View File

@@ -18,7 +18,8 @@
The Capabilities are the capability model's, by id. A submission is refused while
the graph does not hold together, so what the customer approves is complete: every
Capability has one Role answerable for it and someone to do it at the hours it is
needed, and everything the customer said must be kept true is carried by a Check.
needed, everything the customer said must be kept true is carried by a Check, and
every Operational requirement is verified by one.
The responsibility matrix, the organisation chart and the staffing and cost are
written from the graph by code, as views of it.
@@ -301,6 +302,21 @@ def check(card: RateCard, frameworks: Collection[str] = ()) -> chain.DataCheck:
for identifier in conditions
if identifier not in carried
]
# Every Operational requirement is verified: by a Check from it, or from a
# Condition it comes from. Serving it with a Capability says who does the
# work; a Check says how anyone would know it is done.
for requirement in chain.requirements(upstream):
identifier = str(requirement["id"])
named = requirement.get("source") or []
named = [named] if isinstance(named, str) else named
if identifier not in carried and not any(
str(source) in carried and str(source) in conditions for source in named
):
problems.append(
f"{name}: Operational requirement {identifier} is verified by no "
"Check: give it one, from the requirement or from a Condition "
"it comes from"
)
problems += check_measures(
graph, scope, capabilities, by_capability, roles, frameworks, name
)

View File

@@ -6,12 +6,14 @@ It costs model usage: run it deliberately.
Usage:
GOOGLE_GENAI_USE_ENTERPRISE=true GOOGLE_CLOUD_PROJECT=<project> GOOGLE_CLOUD_LOCATION=global \\
.venv/bin/python -m eval.operating_model_eval [case-id ...]
.venv/bin/python -m eval.operating_model_eval [--repeat N] [case-id ...]
The model settings are read from the environment or from `.env`. With no case named,
every case in eval/datasets/cases.json runs, one after another. Results are written
under eval/results/<time>/: each Execution's files, and results.json. The exit code
is non-zero when a case fails a check or runs over its time.
every case in eval/datasets/cases.json runs, one after another; `--repeat N` runs each
N times, so the spread of what is staffed and priced can be seen. Results are written
under eval/results/<time>/: each Execution's files, results.json, spread.json, and
report.md, which holds no path of the machine it ran on and can be published. The
exit code is non-zero when a case fails a check or runs over its time.
"""
from __future__ import annotations
@@ -19,6 +21,7 @@ from __future__ import annotations
import asyncio
import json
import logging
import statistics
import sys
import time
from collections.abc import Mapping, Sequence
@@ -78,15 +81,24 @@ def _tokens(runtime: Any) -> dict[str, dict[str, int]]:
return by_role
def execution_ids(case: Mapping[str, Any], repeat: int) -> list[str]:
"""The Execution of each run of a case: the case's id, or one per repeat."""
if repeat <= 1:
return [str(case["id"])]
return [f"{case['id']}-r{n}" for n in range(1, repeat + 1)]
async def run_case(
case: Mapping[str, Any],
output_root: Path,
*,
settings: Settings | None = None,
runtime: AgentRuntime | None = None,
execution_id: str | None = None,
) -> CaseResult:
"""Run one case to the end and score it. `runtime` replaces the real one, for a
scripted run of the harness itself."""
execution_id = execution_id or str(case["id"])
settings = settings or get_settings()
workflow = build(ROOT)
started = time.monotonic()
@@ -105,7 +117,7 @@ async def run_case(
try:
interaction = await asyncio.wait_for(
assembly.engine.start(
"", pre_approved=True, execution_id=case["id"], **inputs(case)
"", pre_approved=True, execution_id=execution_id, **inputs(case)
),
timeout=limit * 60,
)
@@ -150,17 +162,140 @@ async def run_case(
tokens=_tokens(used),
figures=figures,
warnings=list(state.get("warnings") or []),
folder=str(
output_root
/ "deliverables"
# Relative to the run's folder: results are published, and the machine
# they ran on is no part of them.
folder=(
Path("deliverables")
/ "cases"
/ str(state.get("customer_case"))
/ "executions"
/ case["id"]
),
/ execution_id
).as_posix(),
)
# The figures whose spread across repeated runs is reported.
SPREAD = ("people", "cost_per_month", "roles", "checks", "capabilities")
def spread(results: Sequence[CaseResult]) -> dict[str, dict[str, Any]]:
"""For each case run more than once, how far its figures moved: least, most,
mean, and the range as a share of the mean."""
by_case: dict[str, list[CaseResult]] = {}
for result in results:
by_case.setdefault(result.case, []).append(result)
found: dict[str, dict[str, Any]] = {}
for case, runs in by_case.items():
if len(runs) < 2:
continue
figures: dict[str, Any] = {"runs": len(runs)}
for name in SPREAD:
values = [
r.figures[name]
for r in runs
if isinstance(r.figures.get(name), (int, float))
]
if len(values) < 2:
continue
mean = statistics.fmean(values)
figures[name] = {
"min": min(values),
"max": max(values),
"mean": round(mean, 1),
"range_pct": round((max(values) - min(values)) / mean * 100, 1)
if mean
else 0.0,
}
found[case] = figures
return found
def markdown(
results: Sequence[CaseResult], spreads: Mapping[str, Mapping[str, Any]], stamp: str
) -> str:
"""The run, as a report that can be published."""
lines = [
"# Target operating model agent: evaluation",
"",
(
f"Run `{stamp}`. Each run is one pre-approved Execution with real models "
"on a benchmark case. Every case is fictional; no customer's data is in it."
),
"",
"## Results",
"",
(
"| Case | Run | Result | Status | Minutes | Revisions "
"| Requirements verified | Roles | People | Cost a month |"
),
"|---|---|---|---|---|---|---|---|---|---|",
]
seen: dict[str, int] = {}
for result in results:
seen[result.case] = seen.get(result.case, 0) + 1
figures = result.figures
coverage = next(
(
c.detail.split(";")[0]
for c in result.checks
if c.name.startswith("every Operational")
),
"",
)
cost = figures.get("cost_per_month")
lines.append(
f"| {result.case} | {seen[result.case]} | "
f"{'PASS' if result.passed else 'FAIL'} | {result.status} | "
f"{result.minutes} | {sum(result.revisions.values())} | {coverage} | "
f"{figures.get('roles', '')} | {figures.get('people', '')} | "
+ (
f"{cost:,} {figures.get('currency', '')} |"
if isinstance(cost, (int, float))
else " |"
)
)
failed = [(r, c) for r in results for c in r.checks if not c.passed]
lines += ["", "## Checks that failed", ""]
if failed:
lines += [
f"- **{r.case}**: {c.name}" + (f" ({c.detail})" if c.detail else "")
for r, c in failed
]
else:
lines.append("None: every run passed every check.")
if spreads:
lines += [
"",
"## Spread across repeated runs",
"",
"The same case and inputs, run again: how far the operating model moved.",
"",
"| Case | Figure | Least | Most | Mean | Range of the mean |",
"|---|---|---|---|---|---|",
]
for case, measured in spreads.items():
for name in SPREAD:
if name in measured:
f = measured[name]
lines.append(
f"| {case} | {name} | {f['min']} | {f['max']} | {f['mean']} | "
f"{f['range_pct']}% |"
)
return "\n".join(lines) + "\n"
def parse_arguments(arguments: Sequence[str]) -> tuple[list[str], int]:
"""The cases named, and how many times each is to run."""
names, repeat, rest = [], 1, list(arguments)
while rest:
argument = rest.pop(0)
if argument == "--repeat":
repeat = int(rest.pop(0))
else:
names.append(argument)
return names, repeat
def report(results: Sequence[CaseResult]) -> str:
lines = []
for result in results:
@@ -183,7 +318,8 @@ def report(results: Sequence[CaseResult]) -> str:
async def main(arguments: Sequence[str]) -> int:
logging.basicConfig(level=logging.INFO, format="%(asctime)s %(name)s %(message)s")
cases = load_cases(arguments)
wanted, repeat = parse_arguments(arguments)
cases = load_cases(wanted)
stamp = datetime.now(UTC).strftime("%Y%m%dT%H%M%SZ")
output_root = RESULTS / stamp
output_root.mkdir(parents=True, exist_ok=True)
@@ -193,12 +329,24 @@ async def main(arguments: Sequence[str]) -> int:
)
results = []
for case in cases:
logger.info("Running %s", case["id"])
results.append(await run_case(case, output_root, settings=settings))
(output_root / "results.json").write_text(
json.dumps([result.as_dict() for result in results], indent=2),
encoding="utf-8",
)
for execution_id in execution_ids(case, repeat):
logger.info("Running %s as %s", case["id"], execution_id)
results.append(
await run_case(
case, output_root, settings=settings, execution_id=execution_id
)
)
spreads = spread(results)
(output_root / "results.json").write_text(
json.dumps([result.as_dict() for result in results], indent=2),
encoding="utf-8",
)
(output_root / "spread.json").write_text(
json.dumps(spreads, indent=2), encoding="utf-8"
)
(output_root / "report.md").write_text(
markdown(results, spreads, stamp), encoding="utf-8"
)
print(report(results))
print(f"\nWritten to {output_root}")
return 0 if all(result.passed for result in results) else 1

View File

@@ -0,0 +1,470 @@
[
{
"id": "C-1",
"catalogue": "incident-management",
"serves": [
"OR-1"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "24x7",
"effort_hours_per_month": 40,
"basis": "Estimated 5 serious incidents per month across the foundation, taking 8 hours each to resolve and review."
},
{
"id": "C-2",
"catalogue": "monitoring-and-alerting",
"serves": [
"OR-1",
"OR-5",
"OR-15"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "24x7",
"effort_hours_per_month": 60,
"basis": "Continuous triage of alerts across 11 platform components, averaging 2 hours per day."
},
{
"id": "C-3",
"catalogue": "problem-management",
"serves": [
"OR-2"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Root cause analysis for 2 major recurring issues per month, taking 10 hours each."
},
{
"id": "C-4",
"catalogue": "service-request-fulfilment",
"serves": [
"OR-13",
"OR-14"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 30,
"basis": "Processing 15 complex service requests per month at 2 hours each."
},
{
"id": "C-5",
"catalogue": "change-enablement",
"serves": [
"OR-7"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Reviewing and approving 40 infrastructure pull requests per month at 0.5 hours each."
},
{
"id": "C-6",
"catalogue": "release-and-deployment",
"serves": [
"OR-7"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Managing CI/CD pipeline deployments and troubleshooting failed releases, estimated at 20 hours per month."
},
{
"id": "C-7",
"catalogue": "configuration-management",
"serves": [
"OR-4",
"OR-17",
"OR-18"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 15,
"basis": "Monthly audits of declarative state against deployed resources."
},
{
"id": "C-8",
"catalogue": "backup-and-recovery",
"serves": [
"OR-4"
],
"items": [
"S-7",
"S-8",
"S-10"
],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Monthly testing of restores for Cloud KMS, Audit Logs, and Terraform State buckets."
},
{
"id": "C-9",
"catalogue": "service-continuity",
"serves": [
"OR-3",
"OR-11"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 16,
"basis": "Bi-monthly DR failover rehearsals, averaging 16 hours of preparation and execution per month."
},
{
"id": "C-10",
"catalogue": "capacity-and-performance",
"serves": [
"OR-2",
"OR-5",
"OR-6",
"OR-10"
],
"items": [
"S-2",
"S-3",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Reviewing network throughput, interconnect capacity, and NVA scaling metrics monthly."
},
{
"id": "C-11",
"catalogue": "access-management",
"serves": [
"OR-9",
"OR-14",
"OR-21"
],
"items": [
"S-5",
"S-6",
"S-7"
],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Fulfilling 20 access grants/revocations per month and conducting monthly access reviews."
},
{
"id": "C-12",
"catalogue": "vulnerability-and-patch-management",
"serves": [
"OR-20"
],
"items": [
"S-3"
],
"hours": "business",
"effort_hours_per_month": 25,
"basis": "Weekly vulnerability scanning review and patching of the Network Virtual Appliances (NVAs)."
},
{
"id": "C-13",
"catalogue": "security-monitoring-and-response",
"serves": [
"OR-8",
"OR-17",
"OR-22"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "24x7",
"effort_hours_per_month": 60,
"basis": "Triage and response to security events across the platform 24x7, averaging 2 hours per day."
},
{
"id": "C-14",
"catalogue": "cost-management",
"serves": [
"OR-10"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 8,
"basis": "Monthly budget variance reporting and anomaly review."
},
{
"id": "C-15",
"catalogue": "service-level-management",
"serves": [
"OR-2"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 8,
"basis": "Monthly aggregation and reporting of service level objectives."
},
{
"id": "C-16",
"catalogue": "platform-product-management",
"serves": [
"OR-12"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 40,
"basis": "Backlog grooming, roadmap planning, and measuring adoption for the platform foundation."
},
{
"id": "C-17",
"catalogue": "self-service-and-golden-paths",
"serves": [
"OR-12"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 40,
"basis": "Developing and maintaining automated self-service modules and golden path documentation."
},
{
"id": "C-18",
"catalogue": "enablement",
"serves": [
"OR-12"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 40,
"basis": "Pairing and onboarding sessions with application teams to adopt the landing zone."
},
{
"id": "C-19",
"catalogue": "delivery-and-developer-experience-measurement",
"serves": [
"OR-12"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Monthly compilation of DORA metrics, SPACE surveys, and DevEx feedback."
},
{
"id": "C-20",
"catalogue": "supplier-management",
"serves": [
"OR-13",
"OR-19"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Monthly service reviews with Google Cloud and hybrid interconnect carrier."
},
{
"id": "C-21",
"catalogue": "regulatory-evidence",
"serves": [
"OR-16",
"OR-19",
"OR-20",
"OR-22",
"OR-23",
"OR-24"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4",
"S-5",
"S-6",
"S-7",
"S-8",
"S-9",
"S-10",
"S-11"
],
"hours": "business",
"effort_hours_per_month": 30,
"basis": "Continuous collation of evidence for DORA, ISO 27001, and PCI-DSS v4.0 audits."
}
]

View File

@@ -0,0 +1,23 @@
[
{
"id": "AF-1",
"about": ["S-3"],
"needed_by": ["C-1"],
"lacks": "The solution lacks a secure remote access mechanism (such as a bastion host or Identity-Aware Proxy) as a way in for responders to the Centralised Egress Traffic Inspection Gateway.",
"proposed": "Add Identity-Aware Proxy or a secure bastion host to allow responders to securely access instances."
},
{
"id": "AF-2",
"about": ["S-11"],
"needed_by": ["C-14"],
"lacks": "The solution lacks automated budget anomaly alerts to ensure the warm standby environment maintains a minimal pilot light footprint.",
"proposed": "Configure Google Cloud Billing Budgets and alerts tied to the standby environment."
},
{
"id": "AF-3",
"about": ["S-2", "S-4"],
"needed_by": ["C-7"],
"lacks": "The solution lacks an automated backup service or vault to ensure state and configuration achieve the maximum data loss window (RPO) of 1 hour.",
"proposed": "Implement Google Cloud Backup and DR service or enable automated object versioning with lifecycle policies."
}
]

View File

@@ -0,0 +1,331 @@
# Operating model guide: Google Cloud Landing Zone for Core Payments Engine
## Summary
This operating model guide governs the enterprise-grade Google Cloud platform foundation landing zone supporting the core payments engine, spanning multi-tier environment isolation, dedicated hybrid network interconnect, transit network fabric, centralised egress traffic inspection gateways, corporate identity federation, pipeline identity brokering, cryptographic key management, centralised immutable audit logging, governance guardrails, declarative infrastructure provisioning, and operational telemetry. The Managed Service Provider operates the platform foundation under a provider-operated model, holding operational accountability for infrastructure reliability, platform engineering, security monitoring, and regulatory evidence collation. The customer maintains workload governance and consumes foundation services autonomously via self-service, serving as a consulted stakeholder for architecture reviews and release approvals.
Operational fault response, telemetry triage, and security monitoring are maintained on a continuous 24x7 basis, while platform engineering changes, release deployments, enablement, and compliance governance operate during standard business hours. The reader should look first at the architectural findings and the operational checks that wait on them, where missing capabilities in the solution design—specifically automated backup tooling to meet the recovery point objective, automated budget anomaly alerts for the warm standby environment, and secure remote access for egress inspection appliances—require design resolution before full operational verification can be achieved.
### Key figures
- Operated: 11 Items, with 21 Conditions to keep true.
- Faults responded to: 24x7 hours.
- Capabilities: 21.
- People: 12.2. Cost a month: 87,959 GBP, from rate card version `draft-2026-10-13` (placeholder prices: an illustration).
- Scenario walk-throughs: 44 of 44 pass.
- Business outcomes: 3, 3 shown by a Measure.
- Findings for whoever owns the design: 3.
## Business outcomes
**BO-1: Continuous and resilient payment processing with high availability and low-latency hybrid connectivity**
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Platform Availability | service level | | 99.9% | Service level management | Platform Reliability Lead |
| Incident Response Time | service level | | Under 30 minutes | Service level management | Platform Reliability Lead |
**BO-2: Sustained regulatory compliance with DORA and PCI-DSS v4.0 security and resilience standards**
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Compliance Audit Pass Rate | service level | | 100% | Regulatory evidence and reporting | Compliance Officer |
**BO-3: Rapid and secure platform change releases through automated CI/CD delivery pipelines**
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Deployment frequency | outcome | dora-metrics | Multiple times a day | Delivery and developer experience measurement | Product Manager |
| Satisfaction and well-being | guardrail | space-framework | Positive trend | Delivery and developer experience measurement | Product Manager |
| Feedback loops | leading | devex-framework | Minimal friction | Delivery and developer experience measurement | Product Manager |
## What is operated
| Item | What it is | Kind | Product | From |
| --- | --- | --- | --- | --- |
| S-1 | Multi-Tier Environment Hierarchy & Isolation Boundary | governance | Resource Manager | C-1 |
| S-2 | Dedicated Hybrid Network Interconnect Gateway | network | Cloud Interconnect | C-2 |
| S-3 | Centralised Egress Traffic Inspection Gateway | compute | Compute Engine | C-3 |
| S-4 | Transit Network Fabric & Routing Controller | service | Virtual Private Cloud | C-4 |
| S-5 | Corporate Identity Federation Gateway | identity | Cloud Identity | C-5 |
| S-6 | Automated Delivery Pipeline Identity Broker | identity | Workload Identity Federation | C-6 |
| S-7 | Cryptographic Key Management & Rotation Service | keys | Cloud KMS | C-7 |
| S-8 | Centralised Immutable Audit Log Repository | storage | Cloud Storage | C-8 |
| S-9 | Platform Compliance & Governance Guardrail Controller | governance | Organization Policy Service | C-9 |
| S-10 | Declarative Infrastructure Provisioning & State Engine | storage | Cloud Storage | C-10 |
| S-11 | Centralised Operational Telemetry & Alerting Engine | observability | Cloud Monitoring | C-11 |
What must be kept true while it is run:
| Condition | On | What must hold | From |
| --- | --- | --- | --- |
| K-1 | S-1, S-7, S-9 | Customer data and payment processing remain within United Kingdom and European Union legal jurisdictions. | NFR-1 |
| K-2 | S-1, S-7, S-9 | Warm standby environment operates with reduced capacity until activated during a disaster recovery failover. | NFR-1 |
| K-3 | S-1, S-9 | PCI-regulated production environment is isolated from non-PCI scopes according to PCI-DSS v4.0 network segmentation requirements. | NFR-2 |
| K-4 | S-3, S-4 | Workload APIs and payment services are accessible exclusively through private corporate network paths. | NFR-3 |
| K-5 | S-2 | Hybrid connection maintains low-latency, SLA-backed private data transmission between on-premises and Google Cloud. | NFR-4 |
| K-6 | S-3 | Centralised inspection appliances perform next-generation stateful packet inspection, URL filtering, and threat detection on outbound internet sessions. | NFR-5 |
| K-7 | S-2, S-4 | Platform foundation failover to europe-west1 can be completed within 4 hours during a primary region outage. | NFR-6 |
| K-8 | S-2, S-4 | Configuration drift and backup state achieve a maximum data loss window (RPO) of 1 hour. | NFR-6 |
| K-9 | S-5, S-6 | Corporate user lifecycle management and MFA enforcement are governed centrally by Entra ID conditional access policies. | NFR-7 |
| K-10 | S-1, S-9 | Platform governance and resilience architecture comply with DORA regulatory testing and third-party risk management frameworks. | NFR-8 |
| K-11 | S-1, S-9 | Production cardholder data environment satisfies PCI-DSS v4.0 isolation and security control requirements. | NFR-8 |
| K-12 | S-7 | Confidential payment data is secured against unauthorized platform-level access or data exposure. | NFR-9 |
| K-13 | S-8 | Audit logs cannot be modified, deleted, or shortened by any identity or administrator prior to retention expiration. | NFR-10 |
| K-14 | S-2, S-4, S-11 | Monthly availability of the core platform landing zone and network routing meets or exceeds 99.9%. | NFR-11 |
| K-15 | S-9 | Primary and secondary regions leverage Google Cloud data centres with published carbon-free energy (CFE) performance metrics. | NFR-12 |
| K-16 | S-6, S-10 | Platform foundation delivery and workload ingestion readiness are achieved within 10 weeks of project commencement. | NFR-13 |
| K-17 | S-8, S-10, S-11 | Central platform team operates 24/7 support for infrastructure incidents and availability alerts. | NFR-14 |
| K-18 | S-8, S-10, S-11 | Pull request workflows require automated CI/CD linting, validation, and peer approval prior to merge and deployment. | NFR-14 |
| K-19 | S-3 | NVA instances use machine families that support high bandwidth networking. | DR-3 |
| K-20 | S-3 | The warm standby environment operates at a minimal pilot light footprint during normal operations. | DR-11 |
| K-21 | S-3 | Automated disaster recovery scripts scale the standby environment to full capacity only during a failover event. | DR-11 |
## Operational requirements
| Requirement | Kind | What must be achieved | From |
| --- | --- | --- | --- |
| OR-1 | service_level | Priority 1 incidents on core platform foundation components are acknowledged within 30 minutes (assumed under service_levels.priority_1_response_minutes), supported continuously 24 hours a day, 7 days a week. | operations.support_hours, service_levels.priority_1_response_minutes, K-17 |
| OR-2 | service_level | The core platform landing zone and network routing maintain at least 99.9% monthly availability, operating 24 hours a day, 7 days a week. | K-14, operations.availability_hours |
| OR-3 | service_level | Platform foundation failover to the secondary recovery region is completed within 4 hours (assumed under service_levels.recovery_time_hours) in the event of a primary region outage. | K-7, service_levels.recovery_time_hours |
| OR-4 | service_level | Platform infrastructure configuration drift and backup state maintain a recovery point objective (RPO) of no more than 1 hour of data loss. | K-8 |
| OR-5 | service_level | Dedicated hybrid connectivity between on-premises environments and the cloud platform maintains SLA-backed, low-latency private data transmission. | K-5 |
| OR-6 | service_level | Centralised inspection appliances maintain high-bandwidth network throughput capacity to prevent traffic constraints during peak transaction flows. | K-19 |
| OR-7 | process | All infrastructure changes require automated pipeline validation, linting, and peer approval via pull requests prior to merge and release (assumed under operations.change_process). | K-18, operations.change_process |
| OR-8 | process | Outbound internet traffic is inspected through centralised stateful packet inspection, URL filtering, and threat detection before leaving the environment. | K-6 |
| OR-9 | process | User lifecycle management and multi-factor authentication enforcement are governed through centralised identity provider conditional access policies. | K-9 |
| OR-10 | process | The warm standby environment operates at a minimal pilot light footprint with reduced capacity during normal operations until activated for failover. | K-2, K-20 |
| OR-11 | process | Standby disaster recovery infrastructure is scaled to full operational capacity automatically only upon invocation of a disaster recovery failover. | K-21 |
| OR-12 | process | Platform foundation operational readiness and workload ingestion readiness are achieved within 10 weeks (assumed as 50 working days under solution.build.duration_days) from commencement. | K-16, solution.build.duration_days |
| OR-13 | organisation | Platform foundation operations and support are delivered under a service-provider operating model. | sourcing.model |
| OR-14 | organisation | Operational activities and support delivery are conducted solely from within the United Kingdom, Poland, and India. | sourcing.delivery_countries |
| OR-15 | tooling | Operational telemetry, metrics, and incident logging are integrated into the centralised platform operations suite (assumed under service_management.tooling). | service_management.tooling |
| OR-16 | compliance | All customer data and payment processing activities remain strictly within United Kingdom and European Union legal jurisdictions. | K-1 |
| OR-17 | compliance | The PCI-regulated production environment is isolated from non-PCI scopes according to PCI-DSS v4.0 network segmentation requirements. | K-3 |
| OR-18 | compliance | Workload application programming interfaces and payment services are accessible exclusively through private corporate network paths. | K-4 |
| OR-19 | compliance | Platform governance and resilience architecture comply with DORA regulatory testing and third-party risk management frameworks. | K-10 |
| OR-20 | compliance | The production cardholder data environment satisfies PCI-DSS v4.0 isolation and security control requirements. | K-11 |
| OR-21 | compliance | Confidential payment data is secured using customer-controlled cryptographic keys against unauthorized platform-level access or data exposure. | K-12 |
| OR-22 | compliance | Audit logs are immutably retained and protected against modification, deletion, or truncation by any identity prior to retention expiration. | K-13 |
| OR-23 | compliance | Cloud data centres supporting primary and secondary regions have published carbon-free energy (CFE) performance metrics. | K-15 |
| OR-24 | compliance | Platform foundation operations maintain continuous compliance and audit evidence across DORA, ISO 27001, and PCI-DSS v4.0 frameworks. | compliance.frameworks |
## Capabilities
| Capability | What it is | Serves | Covers | Hours | Effort a month |
| --- | --- | --- | --- | --- | --- |
| C-1 | Incident management | OR-1 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | 24x7 | 40 h |
| C-2 | Monitoring and alerting | OR-1, OR-5, OR-15 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | 24x7 | 60 h |
| C-3 | Problem management | OR-2 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 20 h |
| C-4 | Service request fulfilment | OR-13, OR-14 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 30 h |
| C-5 | Change enablement | OR-7 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 20 h |
| C-6 | Release and deployment | OR-7 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 20 h |
| C-7 | Configuration management | OR-4, OR-17, OR-18 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 15 h |
| C-8 | Backup and recovery | OR-4 | S-7, S-8, S-10 | business | 10 h |
| C-9 | Service continuity | OR-3, OR-11 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 16 h |
| C-10 | Capacity and performance management | OR-2, OR-5, OR-6, OR-10 | S-2, S-3, S-4 | business | 10 h |
| C-11 | Access management | OR-9, OR-14, OR-21 | S-5, S-6, S-7 | business | 20 h |
| C-12 | Vulnerability and patch management | OR-20 | S-3 | business | 25 h |
| C-13 | Security monitoring and response | OR-8, OR-17, OR-22 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | 24x7 | 60 h |
| C-14 | Cost management | OR-10 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 8 h |
| C-15 | Service level management | OR-2 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 8 h |
| C-16 | Platform product management | OR-12 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 40 h |
| C-17 | Self-service and golden paths | OR-12 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 40 h |
| C-18 | Enablement | OR-12 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 40 h |
| C-19 | Delivery and developer experience measurement | OR-12 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 10 h |
| C-20 | Supplier management | OR-13, OR-19 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 10 h |
| C-21 | Regulatory evidence and reporting | OR-16, OR-19, OR-20, OR-22, OR-23, OR-24 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 | business | 30 h |
## Who does what
| Role | Party | Country | Level | Hours |
| --- | --- | --- | --- | --- |
| Platform Reliability Lead | Managed Service Provider (provider) | GB | lead | business |
| Platform SRE | Managed Service Provider (provider) | PL | senior | 24x7 |
| Security Analyst | Managed Service Provider (provider) | IN | senior | 24x7 |
| Platform Engineer | Managed Service Provider (provider) | PL | senior | business |
| Enablement Specialist | Managed Service Provider (provider) | GB | senior | business |
| Compliance Officer | Managed Service Provider (provider) | GB | lead | business |
| Product Manager | Managed Service Provider (provider) | GB | lead | business |
| Customer Service Owner | Customer Organization (customer) | GB | lead | business |
The teams, as Team Topologies names their kinds:
| Team | Kind | Party | Roles | Purpose |
| --- | --- | --- | --- | --- |
| Platform Engineering Team | platform | Managed Service Provider | Platform Reliability Lead, Platform Engineer, Compliance Officer, Product Manager | |
| Platform Operations Team | platform | Managed Service Provider | Platform SRE | |
| Security Operations Team | platform | Managed Service Provider | Security Analyst | 24x7 Security Monitoring and Response |
| Developer Enablement Team | enabling | Managed Service Provider | Enablement Specialist | |
| Customer Governance and App Squads | stream-aligned | Customer Organization | Customer Service Owner | |
How the teams work together:
| From | To | Mode | Until | Purpose |
| --- | --- | --- | --- | --- |
| Customer Governance and App Squads | Platform Engineering Team | x-as-a-service | | Application teams consume platform services through the self-service portal. |
| Developer Enablement Team | Customer Governance and App Squads | facilitating | | Enablement specialists help application teams adopt golden paths and DORA metrics. |
| Developer Enablement Team | Customer Governance and App Squads | collaboration | End of the 10-week foundation build period, returning to a facilitating mode. | Enablement team pairs with application teams for initial workload ingestion. |
| Capability | Platform Reliability Lead | Platform SRE | Security Analyst | Platform Engineer | Enablement Specialist | Compliance Officer | Product Manager | Customer Service Owner |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Incident management (C-1) | A | R | | | | | | C |
| Monitoring and alerting (C-2) | A | R | | | | | | C |
| Problem management (C-3) | A | | | R | | | | C |
| Service request fulfilment (C-4) | A | R | | | | | | C |
| Change enablement (C-5) | A | | | R | | | | C |
| Release and deployment (C-6) | A | | | R | | | | C |
| Configuration management (C-7) | A | | | R | | | | C |
| Backup and recovery (C-8) | A | | | R | | | | C |
| Service continuity (C-9) | A | | | R | | | | C |
| Capacity and performance management (C-10) | A | | | R | | | | C |
| Access management (C-11) | | | | R | | A | | C |
| Vulnerability and patch management (C-12) | | | R | | | A | | C |
| Security monitoring and response (C-13) | | | R | | | A | | C |
| Cost management (C-14) | R | | | | | | A | C |
| Service level management (C-15) | A | R | | | | | | C |
| Platform product management (C-16) | | | | | | | A/R | C |
| Self-service and golden paths (C-17) | | | | R | | | A | C |
| Enablement (C-18) | | | | | R | | A | C |
| Delivery and developer experience measurement (C-19) | | | | | R | | A | C |
| Supplier management (C-20) | A/R | | | | | | | C |
| Regulatory evidence and reporting (C-21) | | | | | | A/R | | C |
A accountable, R responsible, C consulted, I informed.
## Staffing and cost
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Platform Reliability Lead | Managed Service Provider | GB | lead | business | 18.0 h | 0.1 | 1,991 GBP |
| Platform SRE | Managed Service Provider | PL | senior | 24x7 | 138.0 h | 5.0 | 41,640 GBP |
| Security Analyst | Managed Service Provider | IN | senior | 24x7 | 85.0 h | 5.0 | 24,605 GBP |
| Platform Engineer | Managed Service Provider | PL | senior | business | 171.0 h | 1.2 | 7,768 GBP |
| Enablement Specialist | Managed Service Provider | GB | senior | business | 50.0 h | 0.4 | 4,213 GBP |
| Compliance Officer | Managed Service Provider | GB | lead | business | 30.0 h | 0.2 | 3,318 GBP |
| Product Manager | Managed Service Provider | GB | lead | business | 40.0 h | 0.3 | 4,424 GBP |
| Customer Service Owner | Customer Organization | GB | lead | business | 0.0 h | 0.0 | not priced |
12.2 people in all. Cost a month: 87,959 GBP.
Worked from rate card `rate-card`, version `draft-2026-10-13`. **Its figures are placeholders: no price has been set, and this cost is an illustration.**
Converted from USD at 0.79, a rate set on 2026-10-13.
The customer's own staff are counted and not priced. A Role that covers hours wider than a working day is never smaller than the team that can cover them.
## Validation
| Check | What must hold | Verdict | Evidence |
| --- | --- | --- | --- |
| OC-1 | Declarative infrastructure configurations restrict data location to UK and EU regions. | pass | Capability C-7 handles declarative state and configuration management, covering all required items. Platform Engineer (R-4) is responsible during business hours. |
| OC-2 | Warm standby capacity limits on identity, encryption, and governance components are maintained through DR automation. | pass | Capability C-9 manages service continuity and DR failover rehearsals, covering items S-1, S-7, and S-9. Platform Engineer (R-4) is responsible. |
| OC-3 | PCI-regulated production network configurations enforce isolation from non-PCI scopes. | pass | Capability C-7 manages configuration state and audits, ensuring isolation configurations are maintained. Platform Engineer (R-4) is responsible. |
| OC-4 | Workload APIs are confirmed to be routable only via private corporate network paths. | pass | Capability C-7 audits configuration state for workload APIs, and Platform Engineer (R-4) is responsible. |
| OC-5 | Hybrid interconnect capacity metrics demonstrate SLA-backed low latency. | pass | Capability C-10 reviews capacity and performance metrics, including the dedicated hybrid network interconnect. Platform Engineer (R-4) is responsible. |
| OC-6 | Centralised inspection appliances actively perform stateful packet inspection on all egress traffic. | pass | Capability C-13 provides security monitoring and response, analyzing egress traffic inspection data 24x7 via Security Analyst (R-3). |
| OC-7 | Service continuity rehearsals demonstrate secondary region failover in under 4 hours. | pass | Capability C-9 conducts bi-monthly DR failover rehearsals to ensure the 4-hour RTO is achievable. Platform Engineer (R-4) is responsible. |
| OC-8 | Backup validation ensures an RPO of at most 1 hour. | waits on finding (AF-3) | AF-3: The solution lacks an automated backup service or vault to ensure state and configuration achieve the maximum data loss window (RPO) of 1 hour. |
| OC-9 | Identity access policies require Entra ID multi-factor authentication for corporate users. | pass | Capability C-11 covers access management and policy reviews for corporate identity gateways. Platform Engineer (R-4) is responsible. |
| OC-10 | Third-party supplier reviews include DORA risk assessments. | pass | Capability C-20 conducts supplier management and service reviews, incorporating DORA risk assessments. Platform Reliability Lead (R-1) is responsible. |
| OC-11 | Production cardholder data environments maintain PCI-DSS v4.0 network isolation control compliance. | pass | Capability C-21 continuously collates regulatory evidence for PCI-DSS v4.0. Compliance Officer (R-6) is responsible. |
| OC-12 | Confidential payment data storage systems ensure unauthorized access protection via customer-controlled keys. | pass | Capability C-11 governs access management for the cryptographic key management service (S-7). Platform Engineer (R-4) is responsible. |
| OC-13 | Audit logs are actively monitored for modifications and deletions. | pass | Capability C-13 provides 24x7 security monitoring and response for audit logs (S-8). Security Analyst (R-3) is responsible. |
| OC-14 | Monthly availability of network routing components is tracked and meets the 99.9% target. | pass | Capability C-15 aggregates and reports on service level objectives, including availability targets. Platform SRE (R-2) is responsible. |
| OC-15 | Data centres supporting operations provide publicly validated carbon-free energy (CFE) metrics. | pass | Capability C-21 collates regulatory and compliance evidence, including carbon-free energy metrics. Compliance Officer (R-6) is responsible. |
| OC-16 | Workload ingestion metrics confirm operational readiness within the initial 10-week build. | pass | Capability C-16 manages the platform backlog and adoption roadmap to confirm workload ingestion readiness. Product Manager (R-7) is responsible. |
| OC-17 | A 24/7 service desk is resourced to actively log and respond to infrastructure priority incidents. | pass | Capability C-1 handles 24x7 incident management, and Platform SRE (R-2) provides 24x7 coverage to log and respond to incidents. |
| OC-18 | CI/CD pipeline hooks enforce pull request approvals, validation, and linting before merge. | pass | Capability C-5 manages change enablement and pull request approvals. Platform Engineer (R-4) is responsible. |
| OC-19 | NVA capacity tracking confirms instances utilize high-bandwidth machine families. | pass | Capability C-10 reviews capacity and performance for network virtual appliances. Platform Engineer (R-4) is responsible. |
| OC-20 | Platform budget anomaly alerts check that the warm standby uses minimal infrastructure footprint. | waits on finding (AF-2) | AF-2: The solution lacks automated budget anomaly alerts out-of-the-box to track the minimal pilot light footprint of the warm standby region. |
| OC-21 | Disaster recovery infrastructure automation limits full-capacity scaling strictly to failover occurrences. | pass | Capability C-9 conducts service continuity failovers, managing the DR infrastructure automation. Platform Engineer (R-4) is responsible. |
| OC-22 | Operations and support delivery are provided solely under the agreed service-provider framework. | pass | Role R-1 (Platform Reliability Lead) is part of the Managed Service Provider party, fulfilling the agreed service-provider framework. |
| OC-23 | Staff are located solely in authorized delivery countries. | pass | Role R-1 is located in GB, which is an authorized delivery country. |
| OC-24 | Operational telemetry and incident logging are fully integrated into the operations suite. | pass | Capability C-2 performs continuous monitoring and alerting using the integrated operations suite. Platform SRE (R-2) is responsible 24x7. |
| OC-25 | Compliance audits consistently certify continuous adherence across DORA, ISO 27001, and PCI-DSS v4.0 frameworks. | pass | Capability C-21 continuously collates audit evidence across DORA, ISO 27001, and PCI-DSS v4.0. Compliance Officer (R-6) is responsible. |
| OC-26 | Incident responders use a secure remote access mechanism to troubleshoot Centralised Egress Traffic Inspection Gateways. | waits on finding (AF-1) | AF-1: The solution lacks a secure remote access mechanism (such as a bastion host or Identity-Aware Proxy) as a way in for responders to the Centralised Egress Traffic Inspection Gateway. |
Each scenario is generated from the operating model and traced through it by code.
| Scenario | Result | Path |
| --- | --- | --- |
| Multi-Tier Environment Hierarchy & Isolation Boundary (S-1) fails at an hour faults are responded to (24x7). | pass | Platform SRE responds under C-1, and Platform Reliability Lead is answerable. |
| Multi-Tier Environment Hierarchy & Isolation Boundary (S-1) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Dedicated Hybrid Network Interconnect Gateway (S-2) fails at an hour faults are responded to (24x7). | pass | Platform SRE responds under C-1, and Platform Reliability Lead is answerable. |
| Dedicated Hybrid Network Interconnect Gateway (S-2) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Centralised Egress Traffic Inspection Gateway (S-3) fails at an hour faults are responded to (24x7). | pass | Platform SRE responds under C-1, and Platform Reliability Lead is answerable. |
| Centralised Egress Traffic Inspection Gateway (S-3) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Transit Network Fabric & Routing Controller (S-4) fails at an hour faults are responded to (24x7). | pass | Platform SRE responds under C-1, and Platform Reliability Lead is answerable. |
| Transit Network Fabric & Routing Controller (S-4) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Corporate Identity Federation Gateway (S-5) fails at an hour faults are responded to (24x7). | pass | Platform SRE responds under C-1, and Platform Reliability Lead is answerable. |
| Corporate Identity Federation Gateway (S-5) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Automated Delivery Pipeline Identity Broker (S-6) fails at an hour faults are responded to (24x7). | pass | Platform SRE responds under C-1, and Platform Reliability Lead is answerable. |
| Automated Delivery Pipeline Identity Broker (S-6) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Cryptographic Key Management & Rotation Service (S-7) fails at an hour faults are responded to (24x7). | pass | Platform SRE responds under C-1, and Platform Reliability Lead is answerable. |
| Cryptographic Key Management & Rotation Service (S-7) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Centralised Immutable Audit Log Repository (S-8) fails at an hour faults are responded to (24x7). | pass | Platform SRE responds under C-1, and Platform Reliability Lead is answerable. |
| Centralised Immutable Audit Log Repository (S-8) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Platform Compliance & Governance Guardrail Controller (S-9) fails at an hour faults are responded to (24x7). | pass | Platform SRE responds under C-1, and Platform Reliability Lead is answerable. |
| Platform Compliance & Governance Guardrail Controller (S-9) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Declarative Infrastructure Provisioning & State Engine (S-10) fails at an hour faults are responded to (24x7). | pass | Platform SRE responds under C-1, and Platform Reliability Lead is answerable. |
| Declarative Infrastructure Provisioning & State Engine (S-10) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Centralised Operational Telemetry & Alerting Engine (S-11) fails at an hour faults are responded to (24x7). | pass | Platform SRE responds under C-1, and Platform Reliability Lead is answerable. |
| Centralised Operational Telemetry & Alerting Engine (S-11) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Condition K-1 must be shown to hold: Customer data and payment processing remain within United Kingdom and European Union legal jurisdictions. | pass | Check OC-1 on C-7 keeps it true. |
| Condition K-2 must be shown to hold: Warm standby environment operates with reduced capacity until activated during a disaster recovery failover. | pass | Check OC-2 on C-9 keeps it true. |
| Condition K-3 must be shown to hold: PCI-regulated production environment is isolated from non-PCI scopes according to PCI-DSS v4.0 network segmentation requirements. | pass | Check OC-3 on C-7 keeps it true. |
| Condition K-4 must be shown to hold: Workload APIs and payment services are accessible exclusively through private corporate network paths. | pass | Check OC-4 on C-7 keeps it true. |
| Condition K-5 must be shown to hold: Hybrid connection maintains low-latency, SLA-backed private data transmission between on-premises and Google Cloud. | pass | Check OC-5 on C-10 keeps it true. |
| Condition K-6 must be shown to hold: Centralised inspection appliances perform next-generation stateful packet inspection, URL filtering, and threat detection on outbound internet sessions. | pass | Check OC-6 on C-13 keeps it true. |
| Condition K-7 must be shown to hold: Platform foundation failover to europe-west1 can be completed within 4 hours during a primary region outage. | pass | Check OC-7 on C-9 keeps it true. |
| Condition K-8 must be shown to hold: Configuration drift and backup state achieve a maximum data loss window (RPO) of 1 hour. | pass | Check OC-8 on C-7 keeps it true. |
| Condition K-9 must be shown to hold: Corporate user lifecycle management and MFA enforcement are governed centrally by Entra ID conditional access policies. | pass | Check OC-9 on C-11 keeps it true. |
| Condition K-10 must be shown to hold: Platform governance and resilience architecture comply with DORA regulatory testing and third-party risk management frameworks. | pass | Check OC-10 on C-20 keeps it true. |
| Condition K-11 must be shown to hold: Production cardholder data environment satisfies PCI-DSS v4.0 isolation and security control requirements. | pass | Check OC-11 on C-21 keeps it true. |
| Condition K-12 must be shown to hold: Confidential payment data is secured against unauthorized platform-level access or data exposure. | pass | Check OC-12 on C-11 keeps it true. |
| Condition K-13 must be shown to hold: Audit logs cannot be modified, deleted, or shortened by any identity or administrator prior to retention expiration. | pass | Check OC-13 on C-13 keeps it true. |
| Condition K-14 must be shown to hold: Monthly availability of the core platform landing zone and network routing meets or exceeds 99.9%. | pass | Check OC-14 on C-15 keeps it true. |
| Condition K-15 must be shown to hold: Primary and secondary regions leverage Google Cloud data centres with published carbon-free energy (CFE) performance metrics. | pass | Check OC-15 on C-21 keeps it true. |
| Condition K-16 must be shown to hold: Platform foundation delivery and workload ingestion readiness are achieved within 10 weeks of project commencement. | pass | Check OC-16 on C-16 keeps it true. |
| Condition K-17 must be shown to hold: Central platform team operates 24/7 support for infrastructure incidents and availability alerts. | pass | Check OC-17 on C-1 keeps it true. |
| Condition K-18 must be shown to hold: Pull request workflows require automated CI/CD linting, validation, and peer approval prior to merge and deployment. | pass | Check OC-18 on C-5 keeps it true. |
| Condition K-19 must be shown to hold: NVA instances use machine families that support high bandwidth networking. | pass | Check OC-19 on C-10 keeps it true. |
| Condition K-20 must be shown to hold: The warm standby environment operates at a minimal pilot light footprint during normal operations. | pass | Check OC-20 on C-14 keeps it true. |
| Condition K-21 must be shown to hold: Automated disaster recovery scripts scale the standby environment to full capacity only during a failover event. | pass | Check OC-21 on C-9 keeps it true. |
| Managed Service Provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
## Findings and open questions
What operating this solution needs that the solution, as described, does not provide. Nothing here was designed around: each is for whoever owns the design.
- **AF-1** (S-3): The solution lacks a secure remote access mechanism (such as a bastion host or Identity-Aware Proxy) as a way in for responders to the Centralised Egress Traffic Inspection Gateway. Proposed: Add Identity-Aware Proxy or a secure bastion host to allow responders to securely access instances.
- **AF-2** (S-11): The solution lacks automated budget anomaly alerts to ensure the warm standby environment maintains a minimal pilot light footprint. Proposed: Configure Google Cloud Billing Budgets and alerts tied to the standby environment.
- **AF-3** (S-2, S-4): The solution lacks an automated backup service or vault to ensure state and configuration achieve the maximum data loss window (RPO) of 1 hour. Proposed: Implement Google Cloud Backup and DR service or enable automated object versioning with lifecycle policies.
Assumed for the customer, and open to change when they answer:
- `intent.business_outcomes`: {'outcome': 'Continuous and resilient payment processing with high availability and low-latency hybrid connectivity', 'id': 'BO-1'}, {'outcome': 'Sustained regulatory compliance with DORA and PCI-DSS v4.0 security and resilience standards', 'id': 'BO-2'}, {'id': 'BO-3', 'outcome': 'Rapid and secure platform change releases through automated CI/CD delivery pipelines'}. Derived from customer request for a UK-regulated payment platform requiring high resilience, continuous compliance, and automated delivery.
- `intent.exclusions`: Application container deployment and runtime microservices managed by application squads, Active-active secondary region in phase 1 (warm standby adopted). Derived from workload scope boundaries where application workloads are managed by application squads, and secondary region is warm standby rather than active-active.
- `solution.build.duration_days`: 50. Derived from 10-week delivery window at 5 working days per week.
- `operations.change_process`: Infrastructure changes managed via pull requests with required approvals and automated GitHub Actions CI/CD pipelines. Derived from request and scope specification indicating pull-request driven changes with peer review and GitHub Actions CI/CD automation.
- `organisation.existing_teams`: . Catalogue default: no existing operational teams assumed; roles to be provisioned under provider-operated model.
- `service_management.tooling`: Google Cloud Operations Suite (Cloud Monitoring and Cloud Logging). Catalogue default: Google Cloud Operations Suite (Cloud Monitoring and Cloud Logging) with no separate third-party ticketing system mandated.
- `service_levels.priority_1_response_minutes`: 30. Catalogue default for Priority 1 incident response acknowledgement.
- `service_levels.recovery_time_hours`: 4. Catalogue default and aligned with target 4-hour RTO for warm standby disaster recovery in secondary region.
## Sources
The Capabilities are from our own capability catalogue, which draws on these frameworks. It cites them and certifies nothing against them.
- ITIL 4: Incident management practice; Monitoring and event management practice; Problem management practice; Service request management practice; Change enablement practice; Release management and Deployment management practices; Service configuration management practice; Service continuity management practice; Capacity and performance management practice; Service level management practice; Supplier management practice
- Site Reliability Engineering: How Google Runs Production Systems: Managing Incidents; Monitoring Distributed Systems; Postmortem Culture: Learning from Failure; Release Engineering; Service Level Objectives
- ISO/IEC 20000-1: Incident management; Service request management; Change management; Service continuity management; Capacity management; Service level management; Supplier management
- Regulation (EU) 2022/2554, the Digital Operational Resilience Act: Article 17, ICT-related incident management process; Article 10, Detection; Article 12, Backup policies and procedures, restoration and recovery procedures and methods; Article 11, Response and recovery; Article 9, Protection and prevention; Article 28, General principles on ICT third-party risk; Article 19, Reporting of major ICT-related incidents
- NIST Cybersecurity Framework: Detect: Continuous Monitoring; Identify: Asset Management; Recover: Incident Recovery Plan Execution; Protect: Identity Management, Authentication, and Access Control; Protect: Platform Security; Detect: Adverse Event Analysis; Respond: Incident Management
- DevOps Research and Assessment (DORA) software delivery metrics: Change failure rate; Deployment frequency and lead time for changes; Deployment frequency; Lead time for changes; Change failure rate; Time to restore service
- ISO/IEC 27001: Access control; Management of technical vulnerabilities; Information security incident management; Compliance with legal and contractual requirements
- FinOps Framework: Allocation; Budgeting; Forecasting; Anomaly Management
- CNCF Platforms White Paper (platform as a product): Platform as a product; Measuring platform success; Platform capabilities; Self-service; Platform as a product
- Team Topologies: Organizing Business and Technology Teams for Fast Flow: Platform team; Thinnest viable platform; X-as-a-Service interaction mode; Enabling team; Facilitating interaction mode
- The SPACE of Developer Productivity: Satisfaction and well-being; Performance; Activity; Communication and collaboration; Efficiency and flow
- DevEx: What Actually Drives Productivity: Feedback loops; Cognitive load; Flow state
**These references have not been checked against the frameworks by a person.** Treat each as a pointer to where to look.

View File

@@ -0,0 +1,201 @@
[
{
"id": "OR-1",
"kind": "service_level",
"statement": "Priority 1 incidents on core platform foundation components are acknowledged within 30 minutes (assumed under service_levels.priority_1_response_minutes), supported continuously 24 hours a day, 7 days a week.",
"source": [
"operations.support_hours",
"service_levels.priority_1_response_minutes",
"K-17"
]
},
{
"id": "OR-2",
"kind": "service_level",
"statement": "The core platform landing zone and network routing maintain at least 99.9% monthly availability, operating 24 hours a day, 7 days a week.",
"source": [
"K-14",
"operations.availability_hours"
]
},
{
"id": "OR-3",
"kind": "service_level",
"statement": "Platform foundation failover to the secondary recovery region is completed within 4 hours (assumed under service_levels.recovery_time_hours) in the event of a primary region outage.",
"source": [
"K-7",
"service_levels.recovery_time_hours"
]
},
{
"id": "OR-4",
"kind": "service_level",
"statement": "Platform infrastructure configuration drift and backup state maintain a recovery point objective (RPO) of no more than 1 hour of data loss.",
"source": [
"K-8"
]
},
{
"id": "OR-5",
"kind": "service_level",
"statement": "Dedicated hybrid connectivity between on-premises environments and the cloud platform maintains SLA-backed, low-latency private data transmission.",
"source": [
"K-5"
]
},
{
"id": "OR-6",
"kind": "service_level",
"statement": "Centralised inspection appliances maintain high-bandwidth network throughput capacity to prevent traffic constraints during peak transaction flows.",
"source": [
"K-19"
]
},
{
"id": "OR-7",
"kind": "process",
"statement": "All infrastructure changes require automated pipeline validation, linting, and peer approval via pull requests prior to merge and release (assumed under operations.change_process).",
"source": [
"K-18",
"operations.change_process"
]
},
{
"id": "OR-8",
"kind": "process",
"statement": "Outbound internet traffic is inspected through centralised stateful packet inspection, URL filtering, and threat detection before leaving the environment.",
"source": [
"K-6"
]
},
{
"id": "OR-9",
"kind": "process",
"statement": "User lifecycle management and multi-factor authentication enforcement are governed through centralised identity provider conditional access policies.",
"source": [
"K-9"
]
},
{
"id": "OR-10",
"kind": "process",
"statement": "The warm standby environment operates at a minimal pilot light footprint with reduced capacity during normal operations until activated for failover.",
"source": [
"K-2",
"K-20"
]
},
{
"id": "OR-11",
"kind": "process",
"statement": "Standby disaster recovery infrastructure is scaled to full operational capacity automatically only upon invocation of a disaster recovery failover.",
"source": [
"K-21"
]
},
{
"id": "OR-12",
"kind": "process",
"statement": "Platform foundation operational readiness and workload ingestion readiness are achieved within 10 weeks (assumed as 50 working days under solution.build.duration_days) from commencement.",
"source": [
"K-16",
"solution.build.duration_days"
]
},
{
"id": "OR-13",
"kind": "organisation",
"statement": "Platform foundation operations and support are delivered under a service-provider operating model.",
"source": [
"sourcing.model"
]
},
{
"id": "OR-14",
"kind": "organisation",
"statement": "Operational activities and support delivery are conducted solely from within the United Kingdom, Poland, and India.",
"source": [
"sourcing.delivery_countries"
]
},
{
"id": "OR-15",
"kind": "tooling",
"statement": "Operational telemetry, metrics, and incident logging are integrated into the centralised platform operations suite (assumed under service_management.tooling).",
"source": [
"service_management.tooling"
]
},
{
"id": "OR-16",
"kind": "compliance",
"statement": "All customer data and payment processing activities remain strictly within United Kingdom and European Union legal jurisdictions.",
"source": [
"K-1"
]
},
{
"id": "OR-17",
"kind": "compliance",
"statement": "The PCI-regulated production environment is isolated from non-PCI scopes according to PCI-DSS v4.0 network segmentation requirements.",
"source": [
"K-3"
]
},
{
"id": "OR-18",
"kind": "compliance",
"statement": "Workload application programming interfaces and payment services are accessible exclusively through private corporate network paths.",
"source": [
"K-4"
]
},
{
"id": "OR-19",
"kind": "compliance",
"statement": "Platform governance and resilience architecture comply with DORA regulatory testing and third-party risk management frameworks.",
"source": [
"K-10"
]
},
{
"id": "OR-20",
"kind": "compliance",
"statement": "The production cardholder data environment satisfies PCI-DSS v4.0 isolation and security control requirements.",
"source": [
"K-11"
]
},
{
"id": "OR-21",
"kind": "compliance",
"statement": "Confidential payment data is secured using customer-controlled cryptographic keys against unauthorized platform-level access or data exposure.",
"source": [
"K-12"
]
},
{
"id": "OR-22",
"kind": "compliance",
"statement": "Audit logs are immutably retained and protected against modification, deletion, or truncation by any identity prior to retention expiration.",
"source": [
"K-13"
]
},
{
"id": "OR-23",
"kind": "compliance",
"statement": "Cloud data centres supporting primary and secondary regions have published carbon-free energy (CFE) performance metrics.",
"source": [
"K-15"
]
},
{
"id": "OR-24",
"kind": "compliance",
"statement": "Platform foundation operations maintain continuous compliance and audit evidence across DORA, ISO 27001, and PCI-DSS v4.0 frameworks.",
"source": [
"compliance.frameworks"
]
}
]

View File

@@ -0,0 +1,26 @@
flowchart TB
subgraph P_1["Managed Service Provider (provider)"]
subgraph T_1["Platform Engineering Team (platform team)"]
R_1["Platform Reliability Lead<br/>GB, lead, business"]
R_4["Platform Engineer<br/>PL, senior, business"]
R_6["Compliance Officer<br/>GB, lead, business"]
R_7["Product Manager<br/>GB, lead, business"]
end
subgraph T_2["Platform Operations Team (platform team)"]
R_2["Platform SRE<br/>PL, senior, 24x7"]
end
subgraph T_3["Security Operations Team (platform team)"]
R_3["Security Analyst<br/>IN, senior, 24x7"]
end
subgraph T_4["Developer Enablement Team (enabling team)"]
R_5["Enablement Specialist<br/>GB, senior, business"]
end
end
subgraph P_2["Customer Organization (customer)"]
subgraph T_5["Customer Governance and App Squads (stream-aligned team)"]
R_8["Customer Service Owner<br/>GB, lead, business"]
end
end
T_5 -- "x-as-a-service" --> T_1
T_4 -- "facilitating" --> T_5
T_4 -- "collaboration until End of the 10-week foundation build period, returning to a facilitating mode." --> T_5

View File

@@ -0,0 +1 @@
{"tenant":"local","customer_case":"case-08-landing-zone","execution_id":"1f8f30a1-7b74-4d23-9fb0-aec58089c506","work":"operating_model","status":"completed","request":"We are a UK-regulated payment platform expanding into Google Cloud. We need an enterprise-grade landing zone ready in under 10 weeks to support our core payments engine. All payment processing must comply with DORA and PCI-DSS v4.0. We have existing on-premises systems that require private, low-latency connectivity over a 10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and GitHub Actions for our delivery pipelines. Security requires that all egress traffic flows through centralised inspection appliances before touching the public internet, and customer data must be encrypted with keys we control.","project_id":null,"guide":"operating-model-guide.md","files":["capabilities.json","findings.json","operating-model-guide.md","operational-requirements.json","organisation.mmd","scenarios.json","scope.json","scope.yaml","staffing.json","target-operating-model.json","verdicts.json"],"kept_at":"2026-10-21T21:51:17.306367+00:00","links":{"record":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506","guide":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/operating-model-guide.md","files":{"capabilities.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/capabilities.json","findings.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/findings.json","operating-model-guide.md":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/operating-model-guide.md","operational-requirements.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/operational-requirements.json","organisation.mmd":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/organisation.mmd","scenarios.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/scenarios.json","scope.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/scope.json","scope.yaml":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/scope.yaml","staffing.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/staffing.json","target-operating-model.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/target-operating-model.json","verdicts.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/verdicts.json"},"latest":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/latest/operating_model","case":"http://localhost:10030/tenants/local/cases/case-08-landing-zone"}}

View File

@@ -0,0 +1,310 @@
[
{
"id": "SC-fault-S-1",
"scenario": "Multi-Tier Environment Hierarchy & Isolation Boundary (S-1) fails at an hour faults are responded to (24x7).",
"about": "S-1",
"passes": true,
"path": "Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"id": "SC-change-S-1",
"scenario": "Multi-Tier Environment Hierarchy & Isolation Boundary (S-1) must be changed.",
"about": "S-1",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-2",
"scenario": "Dedicated Hybrid Network Interconnect Gateway (S-2) fails at an hour faults are responded to (24x7).",
"about": "S-2",
"passes": true,
"path": "Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"id": "SC-change-S-2",
"scenario": "Dedicated Hybrid Network Interconnect Gateway (S-2) must be changed.",
"about": "S-2",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-3",
"scenario": "Centralised Egress Traffic Inspection Gateway (S-3) fails at an hour faults are responded to (24x7).",
"about": "S-3",
"passes": true,
"path": "Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"id": "SC-change-S-3",
"scenario": "Centralised Egress Traffic Inspection Gateway (S-3) must be changed.",
"about": "S-3",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-4",
"scenario": "Transit Network Fabric & Routing Controller (S-4) fails at an hour faults are responded to (24x7).",
"about": "S-4",
"passes": true,
"path": "Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"id": "SC-change-S-4",
"scenario": "Transit Network Fabric & Routing Controller (S-4) must be changed.",
"about": "S-4",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-5",
"scenario": "Corporate Identity Federation Gateway (S-5) fails at an hour faults are responded to (24x7).",
"about": "S-5",
"passes": true,
"path": "Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"id": "SC-change-S-5",
"scenario": "Corporate Identity Federation Gateway (S-5) must be changed.",
"about": "S-5",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-6",
"scenario": "Automated Delivery Pipeline Identity Broker (S-6) fails at an hour faults are responded to (24x7).",
"about": "S-6",
"passes": true,
"path": "Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"id": "SC-change-S-6",
"scenario": "Automated Delivery Pipeline Identity Broker (S-6) must be changed.",
"about": "S-6",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-7",
"scenario": "Cryptographic Key Management & Rotation Service (S-7) fails at an hour faults are responded to (24x7).",
"about": "S-7",
"passes": true,
"path": "Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"id": "SC-change-S-7",
"scenario": "Cryptographic Key Management & Rotation Service (S-7) must be changed.",
"about": "S-7",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-8",
"scenario": "Centralised Immutable Audit Log Repository (S-8) fails at an hour faults are responded to (24x7).",
"about": "S-8",
"passes": true,
"path": "Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"id": "SC-change-S-8",
"scenario": "Centralised Immutable Audit Log Repository (S-8) must be changed.",
"about": "S-8",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-9",
"scenario": "Platform Compliance & Governance Guardrail Controller (S-9) fails at an hour faults are responded to (24x7).",
"about": "S-9",
"passes": true,
"path": "Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"id": "SC-change-S-9",
"scenario": "Platform Compliance & Governance Guardrail Controller (S-9) must be changed.",
"about": "S-9",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-10",
"scenario": "Declarative Infrastructure Provisioning & State Engine (S-10) fails at an hour faults are responded to (24x7).",
"about": "S-10",
"passes": true,
"path": "Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"id": "SC-change-S-10",
"scenario": "Declarative Infrastructure Provisioning & State Engine (S-10) must be changed.",
"about": "S-10",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-11",
"scenario": "Centralised Operational Telemetry & Alerting Engine (S-11) fails at an hour faults are responded to (24x7).",
"about": "S-11",
"passes": true,
"path": "Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"id": "SC-change-S-11",
"scenario": "Centralised Operational Telemetry & Alerting Engine (S-11) must be changed.",
"about": "S-11",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-condition-K-1",
"scenario": "Condition K-1 must be shown to hold: Customer data and payment processing remain within United Kingdom and European Union legal jurisdictions.",
"about": "K-1",
"passes": true,
"path": "Check OC-1 on C-7 keeps it true."
},
{
"id": "SC-condition-K-2",
"scenario": "Condition K-2 must be shown to hold: Warm standby environment operates with reduced capacity until activated during a disaster recovery failover.",
"about": "K-2",
"passes": true,
"path": "Check OC-2 on C-9 keeps it true."
},
{
"id": "SC-condition-K-3",
"scenario": "Condition K-3 must be shown to hold: PCI-regulated production environment is isolated from non-PCI scopes according to PCI-DSS v4.0 network segmentation requirements.",
"about": "K-3",
"passes": true,
"path": "Check OC-3 on C-7 keeps it true."
},
{
"id": "SC-condition-K-4",
"scenario": "Condition K-4 must be shown to hold: Workload APIs and payment services are accessible exclusively through private corporate network paths.",
"about": "K-4",
"passes": true,
"path": "Check OC-4 on C-7 keeps it true."
},
{
"id": "SC-condition-K-5",
"scenario": "Condition K-5 must be shown to hold: Hybrid connection maintains low-latency, SLA-backed private data transmission between on-premises and Google Cloud.",
"about": "K-5",
"passes": true,
"path": "Check OC-5 on C-10 keeps it true."
},
{
"id": "SC-condition-K-6",
"scenario": "Condition K-6 must be shown to hold: Centralised inspection appliances perform next-generation stateful packet inspection, URL filtering, and threat detection on outbound internet sessions.",
"about": "K-6",
"passes": true,
"path": "Check OC-6 on C-13 keeps it true."
},
{
"id": "SC-condition-K-7",
"scenario": "Condition K-7 must be shown to hold: Platform foundation failover to europe-west1 can be completed within 4 hours during a primary region outage.",
"about": "K-7",
"passes": true,
"path": "Check OC-7 on C-9 keeps it true."
},
{
"id": "SC-condition-K-8",
"scenario": "Condition K-8 must be shown to hold: Configuration drift and backup state achieve a maximum data loss window (RPO) of 1 hour.",
"about": "K-8",
"passes": true,
"path": "Check OC-8 on C-7 keeps it true."
},
{
"id": "SC-condition-K-9",
"scenario": "Condition K-9 must be shown to hold: Corporate user lifecycle management and MFA enforcement are governed centrally by Entra ID conditional access policies.",
"about": "K-9",
"passes": true,
"path": "Check OC-9 on C-11 keeps it true."
},
{
"id": "SC-condition-K-10",
"scenario": "Condition K-10 must be shown to hold: Platform governance and resilience architecture comply with DORA regulatory testing and third-party risk management frameworks.",
"about": "K-10",
"passes": true,
"path": "Check OC-10 on C-20 keeps it true."
},
{
"id": "SC-condition-K-11",
"scenario": "Condition K-11 must be shown to hold: Production cardholder data environment satisfies PCI-DSS v4.0 isolation and security control requirements.",
"about": "K-11",
"passes": true,
"path": "Check OC-11 on C-21 keeps it true."
},
{
"id": "SC-condition-K-12",
"scenario": "Condition K-12 must be shown to hold: Confidential payment data is secured against unauthorized platform-level access or data exposure.",
"about": "K-12",
"passes": true,
"path": "Check OC-12 on C-11 keeps it true."
},
{
"id": "SC-condition-K-13",
"scenario": "Condition K-13 must be shown to hold: Audit logs cannot be modified, deleted, or shortened by any identity or administrator prior to retention expiration.",
"about": "K-13",
"passes": true,
"path": "Check OC-13 on C-13 keeps it true."
},
{
"id": "SC-condition-K-14",
"scenario": "Condition K-14 must be shown to hold: Monthly availability of the core platform landing zone and network routing meets or exceeds 99.9%.",
"about": "K-14",
"passes": true,
"path": "Check OC-14 on C-15 keeps it true."
},
{
"id": "SC-condition-K-15",
"scenario": "Condition K-15 must be shown to hold: Primary and secondary regions leverage Google Cloud data centres with published carbon-free energy (CFE) performance metrics.",
"about": "K-15",
"passes": true,
"path": "Check OC-15 on C-21 keeps it true."
},
{
"id": "SC-condition-K-16",
"scenario": "Condition K-16 must be shown to hold: Platform foundation delivery and workload ingestion readiness are achieved within 10 weeks of project commencement.",
"about": "K-16",
"passes": true,
"path": "Check OC-16 on C-16 keeps it true."
},
{
"id": "SC-condition-K-17",
"scenario": "Condition K-17 must be shown to hold: Central platform team operates 24/7 support for infrastructure incidents and availability alerts.",
"about": "K-17",
"passes": true,
"path": "Check OC-17 on C-1 keeps it true."
},
{
"id": "SC-condition-K-18",
"scenario": "Condition K-18 must be shown to hold: Pull request workflows require automated CI/CD linting, validation, and peer approval prior to merge and deployment.",
"about": "K-18",
"passes": true,
"path": "Check OC-18 on C-5 keeps it true."
},
{
"id": "SC-condition-K-19",
"scenario": "Condition K-19 must be shown to hold: NVA instances use machine families that support high bandwidth networking.",
"about": "K-19",
"passes": true,
"path": "Check OC-19 on C-10 keeps it true."
},
{
"id": "SC-condition-K-20",
"scenario": "Condition K-20 must be shown to hold: The warm standby environment operates at a minimal pilot light footprint during normal operations.",
"about": "K-20",
"passes": true,
"path": "Check OC-20 on C-14 keeps it true."
},
{
"id": "SC-condition-K-21",
"scenario": "Condition K-21 must be shown to hold: Automated disaster recovery scripts scale the standby environment to full capacity only during a failover event.",
"about": "K-21",
"passes": true,
"path": "Check OC-21 on C-9 keeps it true."
},
{
"id": "SC-party-P-1",
"scenario": "Managed Service Provider cannot be reached.",
"about": "P-1",
"passes": true,
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
}
]

View File

@@ -0,0 +1,495 @@
{
"kind": "platform_foundation",
"stated": {
"engagement": {
"kind": "platform_foundation"
},
"intent": {
"statement": "We are a UK-regulated payment platform expanding into Google Cloud. We need an enterprise-grade landing zone ready in under 10 weeks to support our core payments engine. All payment processing must comply with DORA and PCI-DSS v4.0. We have existing on-premises systems that require private, low-latency connectivity over a 10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and GitHub Actions for our delivery pipelines. Security requires that all egress traffic flows through centralised inspection appliances before touching the public internet, and customer data must be encrypted with keys we control."
},
"solution": {
"cloud_provider": "gcp",
"items": [
{
"id": "S-1",
"name": "Multi-Tier Environment Hierarchy & Isolation Boundary",
"kind": "governance",
"product": "Resource Manager",
"source_ref": "C-1",
"elements": [
"E-1",
"E-2",
"E-3"
]
},
{
"id": "S-2",
"name": "Dedicated Hybrid Network Interconnect Gateway",
"kind": "network",
"product": "Cloud Interconnect",
"source_ref": "C-2",
"elements": [
"E-9",
"E-10",
"E-11",
"E-12",
"E-35",
"E-36"
]
},
{
"id": "S-3",
"name": "Centralised Egress Traffic Inspection Gateway",
"kind": "compute",
"product": "Compute Engine",
"source_ref": "C-3",
"elements": [
"E-13",
"E-14",
"E-15",
"E-16",
"E-17"
]
},
{
"id": "S-4",
"name": "Transit Network Fabric & Routing Controller",
"kind": "service",
"product": "Virtual Private Cloud",
"source_ref": "C-4",
"elements": [
"E-4",
"E-5",
"E-40",
"E-41",
"E-42",
"E-6",
"E-7",
"E-8",
"E-43",
"E-44",
"E-45",
"E-37",
"E-47",
"E-51",
"E-52",
"E-53"
]
},
{
"id": "S-5",
"name": "Corporate Identity Federation Gateway",
"kind": "identity",
"product": "Cloud Identity",
"source_ref": "C-5",
"elements": [
"E-18"
]
},
{
"id": "S-6",
"name": "Automated Delivery Pipeline Identity Broker",
"kind": "identity",
"product": "Workload Identity Federation",
"source_ref": "C-6",
"elements": [
"E-19",
"E-20",
"E-54",
"E-55"
]
},
{
"id": "S-7",
"name": "Cryptographic Key Management & Rotation Service",
"kind": "keys",
"product": "Cloud KMS",
"source_ref": "C-7",
"elements": [
"E-21",
"E-22",
"E-23",
"E-24"
]
},
{
"id": "S-8",
"name": "Centralised Immutable Audit Log Repository",
"kind": "storage",
"product": "Cloud Storage",
"source_ref": "C-8",
"elements": [
"E-25",
"E-26"
]
},
{
"id": "S-9",
"name": "Platform Compliance & Governance Guardrail Controller",
"kind": "governance",
"product": "Organization Policy Service",
"source_ref": "C-9",
"elements": [
"E-27",
"E-28",
"E-29",
"E-30",
"E-38",
"E-46",
"E-56",
"E-57"
]
},
{
"id": "S-10",
"name": "Declarative Infrastructure Provisioning & State Engine",
"kind": "storage",
"product": "Cloud Storage",
"source_ref": "C-10",
"elements": [
"E-31"
]
},
{
"id": "S-11",
"name": "Centralised Operational Telemetry & Alerting Engine",
"kind": "observability",
"product": "Cloud Monitoring",
"source_ref": "C-11",
"elements": [
"E-32",
"E-33",
"E-58"
]
}
],
"conditions": [
{
"id": "K-1",
"on": [
"S-1",
"S-7",
"S-9"
],
"condition": "Customer data and payment processing remain within United Kingdom and European Union legal jurisdictions.",
"source_ref": "NFR-1"
},
{
"id": "K-2",
"on": [
"S-1",
"S-7",
"S-9"
],
"condition": "Warm standby environment operates with reduced capacity until activated during a disaster recovery failover.",
"source_ref": "NFR-1"
},
{
"id": "K-3",
"on": [
"S-1",
"S-9"
],
"condition": "PCI-regulated production environment is isolated from non-PCI scopes according to PCI-DSS v4.0 network segmentation requirements.",
"source_ref": "NFR-2"
},
{
"id": "K-4",
"on": [
"S-3",
"S-4"
],
"condition": "Workload APIs and payment services are accessible exclusively through private corporate network paths.",
"source_ref": "NFR-3"
},
{
"id": "K-5",
"on": [
"S-2"
],
"condition": "Hybrid connection maintains low-latency, SLA-backed private data transmission between on-premises and Google Cloud.",
"source_ref": "NFR-4"
},
{
"id": "K-6",
"on": [
"S-3"
],
"condition": "Centralised inspection appliances perform next-generation stateful packet inspection, URL filtering, and threat detection on outbound internet sessions.",
"source_ref": "NFR-5"
},
{
"id": "K-7",
"on": [
"S-2",
"S-4"
],
"condition": "Platform foundation failover to europe-west1 can be completed within 4 hours during a primary region outage.",
"source_ref": "NFR-6"
},
{
"id": "K-8",
"on": [
"S-2",
"S-4"
],
"condition": "Configuration drift and backup state achieve a maximum data loss window (RPO) of 1 hour.",
"source_ref": "NFR-6"
},
{
"id": "K-9",
"on": [
"S-5",
"S-6"
],
"condition": "Corporate user lifecycle management and MFA enforcement are governed centrally by Entra ID conditional access policies.",
"source_ref": "NFR-7"
},
{
"id": "K-10",
"on": [
"S-1",
"S-9"
],
"condition": "Platform governance and resilience architecture comply with DORA regulatory testing and third-party risk management frameworks.",
"source_ref": "NFR-8"
},
{
"id": "K-11",
"on": [
"S-1",
"S-9"
],
"condition": "Production cardholder data environment satisfies PCI-DSS v4.0 isolation and security control requirements.",
"source_ref": "NFR-8"
},
{
"id": "K-12",
"on": [
"S-7"
],
"condition": "Confidential payment data is secured against unauthorized platform-level access or data exposure.",
"source_ref": "NFR-9"
},
{
"id": "K-13",
"on": [
"S-8"
],
"condition": "Audit logs cannot be modified, deleted, or shortened by any identity or administrator prior to retention expiration.",
"source_ref": "NFR-10"
},
{
"id": "K-14",
"on": [
"S-2",
"S-4",
"S-11"
],
"condition": "Monthly availability of the core platform landing zone and network routing meets or exceeds 99.9%.",
"source_ref": "NFR-11"
},
{
"id": "K-15",
"on": [
"S-9"
],
"condition": "Primary and secondary regions leverage Google Cloud data centres with published carbon-free energy (CFE) performance metrics.",
"source_ref": "NFR-12"
},
{
"id": "K-16",
"on": [
"S-6",
"S-10"
],
"condition": "Platform foundation delivery and workload ingestion readiness are achieved within 10 weeks of project commencement.",
"source_ref": "NFR-13"
},
{
"id": "K-17",
"on": [
"S-8",
"S-10",
"S-11"
],
"condition": "Central platform team operates 24/7 support for infrastructure incidents and availability alerts.",
"source_ref": "NFR-14"
},
{
"id": "K-18",
"on": [
"S-8",
"S-10",
"S-11"
],
"condition": "Pull request workflows require automated CI/CD linting, validation, and peer approval prior to merge and deployment.",
"source_ref": "NFR-14"
},
{
"id": "K-19",
"on": [
"S-3"
],
"condition": "NVA instances use machine families that support high bandwidth networking.",
"source_ref": "DR-3"
},
{
"id": "K-20",
"on": [
"S-3"
],
"condition": "The warm standby environment operates at a minimal pilot light footprint during normal operations.",
"source_ref": "DR-11"
},
{
"id": "K-21",
"on": [
"S-3"
],
"condition": "Automated disaster recovery scripts scale the standby environment to full capacity only during a failover event.",
"source_ref": "DR-11"
}
],
"build": {
"customer_owned": [
"Order and provision the dedicated carrier circuit"
]
}
},
"operations": {
"support_hours": "24x7",
"availability_hours": "24x7"
},
"sourcing": {
"model": "provider_operated",
"delivery_countries": [
"GB",
"PL",
"IN"
]
},
"compliance": {
"frameworks": [
"DORA",
"ISO27001",
"PCI_DSS_v4"
]
},
"commercial": {
"currency": "GBP"
}
},
"binding": [
"operations.support_hours",
"sourcing.model",
"sourcing.delivery_countries"
],
"assumed": [
{
"field": "intent.business_outcomes",
"value": [
{
"outcome": "Continuous and resilient payment processing with high availability and low-latency hybrid connectivity",
"id": "BO-1"
},
{
"outcome": "Sustained regulatory compliance with DORA and PCI-DSS v4.0 security and resilience standards",
"id": "BO-2"
},
{
"id": "BO-3",
"outcome": "Rapid and secure platform change releases through automated CI/CD delivery pipelines"
}
],
"why": "Derived from customer request for a UK-regulated payment platform requiring high resilience, continuous compliance, and automated delivery."
},
{
"field": "intent.exclusions",
"value": [
"Application container deployment and runtime microservices managed by application squads",
"Active-active secondary region in phase 1 (warm standby adopted)"
],
"why": "Derived from workload scope boundaries where application workloads are managed by application squads, and secondary region is warm standby rather than active-active."
},
{
"field": "solution.build.duration_days",
"value": 50,
"why": "Derived from 10-week delivery window at 5 working days per week."
},
{
"field": "operations.change_process",
"value": "Infrastructure changes managed via pull requests with required approvals and automated GitHub Actions CI/CD pipelines",
"why": "Derived from request and scope specification indicating pull-request driven changes with peer review and GitHub Actions CI/CD automation."
},
{
"field": "organisation.existing_teams",
"value": [],
"why": "Catalogue default: no existing operational teams assumed; roles to be provisioned under provider-operated model."
},
{
"field": "service_management.tooling",
"value": "Google Cloud Operations Suite (Cloud Monitoring and Cloud Logging)",
"why": "Catalogue default: Google Cloud Operations Suite (Cloud Monitoring and Cloud Logging) with no separate third-party ticketing system mandated."
},
{
"field": "service_levels.priority_1_response_minutes",
"value": 30,
"why": "Catalogue default for Priority 1 incident response acknowledgement."
},
{
"field": "service_levels.recovery_time_hours",
"value": 4,
"why": "Catalogue default and aligned with target 4-hour RTO for warm standby disaster recovery in secondary region."
}
],
"to_decide": [],
"to_ask": [
{
"field": "metadata.client_name",
"prompt": "What is metadata.client_name?",
"severity": "LOW"
},
{
"field": "metadata.author",
"prompt": "What is metadata.author?",
"severity": "LOW"
},
{
"field": "metadata.revision",
"prompt": "What is metadata.revision?",
"severity": "LOW"
},
{
"field": "intent.requirements",
"prompt": "Which requirements for operations has the customer stated outright?",
"severity": "LOW"
},
{
"field": "solution.inherited_risks",
"prompt": "What is already known to be unverified or at risk in the solution?",
"severity": "LOW"
},
{
"field": "operations.monitoring",
"prompt": "Which monitoring and alerting is already in place or required?",
"severity": "LOW"
},
{
"field": "organisation.headcount_limit",
"prompt": "Is there a limit on the number of people operating this?",
"severity": "LOW"
},
{
"field": "commercial.monthly_run_budget",
"prompt": "Is there a monthly budget for operating this, in that currency?",
"severity": "LOW"
},
{
"field": "transition.go_live_date",
"prompt": "When must the solution be in operation?",
"severity": "LOW"
}
],
"not_applicable": []
}

View File

@@ -0,0 +1,466 @@
schema_version: 1
metadata:
customer_case: case-08-landing-zone
client_name: ask
author: ask
revision: ask
source: architecture:6c316f05-9643-492c-bab1-eed56e108754
status: UNDER_REVIEW
engagement:
kind: platform_foundation
intent:
statement: We are a UK-regulated payment platform expanding into Google Cloud. We
need an enterprise-grade landing zone ready in under 10 weeks to support our core
payments engine. All payment processing must comply with DORA and PCI-DSS v4.0.
We have existing on-premises systems that require private, low-latency connectivity
over a 10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on
and GitHub Actions for our delivery pipelines. Security requires that all egress
traffic flows through centralised inspection appliances before touching the public
internet, and customer data must be encrypted with keys we control.
requirements: ask
business_outcomes:
- outcome: Continuous and resilient payment processing with high availability and
low-latency hybrid connectivity
id: BO-1
- outcome: Sustained regulatory compliance with DORA and PCI-DSS v4.0 security and
resilience standards
id: BO-2
- id: BO-3
outcome: Rapid and secure platform change releases through automated CI/CD delivery
pipelines
exclusions:
- Application container deployment and runtime microservices managed by application
squads
- Active-active secondary region in phase 1 (warm standby adopted)
solution:
cloud_provider: gcp
items:
- id: S-1
name: Multi-Tier Environment Hierarchy & Isolation Boundary
kind: governance
product: Resource Manager
source_ref: C-1
elements:
- E-1
- E-2
- E-3
- id: S-2
name: Dedicated Hybrid Network Interconnect Gateway
kind: network
product: Cloud Interconnect
source_ref: C-2
elements:
- E-9
- E-10
- E-11
- E-12
- E-35
- E-36
- id: S-3
name: Centralised Egress Traffic Inspection Gateway
kind: compute
product: Compute Engine
source_ref: C-3
elements:
- E-13
- E-14
- E-15
- E-16
- E-17
- id: S-4
name: Transit Network Fabric & Routing Controller
kind: service
product: Virtual Private Cloud
source_ref: C-4
elements:
- E-4
- E-5
- E-40
- E-41
- E-42
- E-6
- E-7
- E-8
- E-43
- E-44
- E-45
- E-37
- E-47
- E-51
- E-52
- E-53
- id: S-5
name: Corporate Identity Federation Gateway
kind: identity
product: Cloud Identity
source_ref: C-5
elements:
- E-18
- id: S-6
name: Automated Delivery Pipeline Identity Broker
kind: identity
product: Workload Identity Federation
source_ref: C-6
elements:
- E-19
- E-20
- E-54
- E-55
- id: S-7
name: Cryptographic Key Management & Rotation Service
kind: keys
product: Cloud KMS
source_ref: C-7
elements:
- E-21
- E-22
- E-23
- E-24
- id: S-8
name: Centralised Immutable Audit Log Repository
kind: storage
product: Cloud Storage
source_ref: C-8
elements:
- E-25
- E-26
- id: S-9
name: Platform Compliance & Governance Guardrail Controller
kind: governance
product: Organization Policy Service
source_ref: C-9
elements:
- E-27
- E-28
- E-29
- E-30
- E-38
- E-46
- E-56
- E-57
- id: S-10
name: Declarative Infrastructure Provisioning & State Engine
kind: storage
product: Cloud Storage
source_ref: C-10
elements:
- E-31
- id: S-11
name: Centralised Operational Telemetry & Alerting Engine
kind: observability
product: Cloud Monitoring
source_ref: C-11
elements:
- E-32
- E-33
- E-58
conditions:
- id: K-1
'on':
- S-1
- S-7
- S-9
condition: Customer data and payment processing remain within United Kingdom and
European Union legal jurisdictions.
source_ref: NFR-1
- id: K-2
'on':
- S-1
- S-7
- S-9
condition: Warm standby environment operates with reduced capacity until activated
during a disaster recovery failover.
source_ref: NFR-1
- id: K-3
'on':
- S-1
- S-9
condition: PCI-regulated production environment is isolated from non-PCI scopes
according to PCI-DSS v4.0 network segmentation requirements.
source_ref: NFR-2
- id: K-4
'on':
- S-3
- S-4
condition: Workload APIs and payment services are accessible exclusively through
private corporate network paths.
source_ref: NFR-3
- id: K-5
'on':
- S-2
condition: Hybrid connection maintains low-latency, SLA-backed private data transmission
between on-premises and Google Cloud.
source_ref: NFR-4
- id: K-6
'on':
- S-3
condition: Centralised inspection appliances perform next-generation stateful
packet inspection, URL filtering, and threat detection on outbound internet
sessions.
source_ref: NFR-5
- id: K-7
'on':
- S-2
- S-4
condition: Platform foundation failover to europe-west1 can be completed within
4 hours during a primary region outage.
source_ref: NFR-6
- id: K-8
'on':
- S-2
- S-4
condition: Configuration drift and backup state achieve a maximum data loss window
(RPO) of 1 hour.
source_ref: NFR-6
- id: K-9
'on':
- S-5
- S-6
condition: Corporate user lifecycle management and MFA enforcement are governed
centrally by Entra ID conditional access policies.
source_ref: NFR-7
- id: K-10
'on':
- S-1
- S-9
condition: Platform governance and resilience architecture comply with DORA regulatory
testing and third-party risk management frameworks.
source_ref: NFR-8
- id: K-11
'on':
- S-1
- S-9
condition: Production cardholder data environment satisfies PCI-DSS v4.0 isolation
and security control requirements.
source_ref: NFR-8
- id: K-12
'on':
- S-7
condition: Confidential payment data is secured against unauthorized platform-level
access or data exposure.
source_ref: NFR-9
- id: K-13
'on':
- S-8
condition: Audit logs cannot be modified, deleted, or shortened by any identity
or administrator prior to retention expiration.
source_ref: NFR-10
- id: K-14
'on':
- S-2
- S-4
- S-11
condition: Monthly availability of the core platform landing zone and network
routing meets or exceeds 99.9%.
source_ref: NFR-11
- id: K-15
'on':
- S-9
condition: Primary and secondary regions leverage Google Cloud data centres with
published carbon-free energy (CFE) performance metrics.
source_ref: NFR-12
- id: K-16
'on':
- S-6
- S-10
condition: Platform foundation delivery and workload ingestion readiness are achieved
within 10 weeks of project commencement.
source_ref: NFR-13
- id: K-17
'on':
- S-8
- S-10
- S-11
condition: Central platform team operates 24/7 support for infrastructure incidents
and availability alerts.
source_ref: NFR-14
- id: K-18
'on':
- S-8
- S-10
- S-11
condition: Pull request workflows require automated CI/CD linting, validation,
and peer approval prior to merge and deployment.
source_ref: NFR-14
- id: K-19
'on':
- S-3
condition: NVA instances use machine families that support high bandwidth networking.
source_ref: DR-3
- id: K-20
'on':
- S-3
condition: The warm standby environment operates at a minimal pilot light footprint
during normal operations.
source_ref: DR-11
- id: K-21
'on':
- S-3
condition: Automated disaster recovery scripts scale the standby environment to
full capacity only during a failover event.
source_ref: DR-11
build:
duration_days: 50
customer_owned:
- Order and provision the dedicated carrier circuit
inherited_risks: ask
operations:
support_hours: 24x7
availability_hours: 24x7
change_process: Infrastructure changes managed via pull requests with required approvals
and automated GitHub Actions CI/CD pipelines
monitoring: ask
sourcing:
model: provider_operated
delivery_countries:
- GB
- PL
- IN
organisation:
existing_teams: []
headcount_limit: ask
service_management:
tooling: Google Cloud Operations Suite (Cloud Monitoring and Cloud Logging)
service_levels:
priority_1_response_minutes: 30
recovery_time_hours: 4
compliance:
frameworks:
- DORA
- ISO27001
- PCI_DSS_v4
commercial:
currency: GBP
monthly_run_budget: ask
transition:
go_live_date: ask
run:
pre_approved: true
overlay_skills: ask
inferred_assumptions:
- id: ASSUMP-01
field: intent.business_outcomes
statement: 'Assumed intent.business_outcomes is [{''outcome'': ''Continuous and
resilient payment processing with high availability and low-latency hybrid connectivity'',
''id'': ''BO-1''}, {''outcome'': ''Sustained regulatory compliance with DORA and
PCI-DSS v4.0 security and resilience standards'', ''id'': ''BO-2''}, {''id'':
''BO-3'', ''outcome'': ''Rapid and secure platform change releases through automated
CI/CD delivery pipelines''}]. Derived from customer request for a UK-regulated
payment platform requiring high resilience, continuous compliance, and automated
delivery.'
impact_if_invalid: Changes what is measured, and what each measure is for.
- id: ASSUMP-02
field: intent.exclusions
statement: Assumed intent.exclusions is ['Application container deployment and runtime
microservices managed by application squads', 'Active-active secondary region
in phase 1 (warm standby adopted)']. Derived from workload scope boundaries where
application workloads are managed by application squads, and secondary region
is warm standby rather than active-active.
impact_if_invalid: Changes which Capabilities are designed.
- id: ASSUMP-03
field: solution.build.duration_days
statement: Assumed solution.build.duration_days is 50. Derived from 10-week delivery
window at 5 working days per week.
impact_if_invalid: Changes when Capabilities must be ready.
- id: ASSUMP-04
field: operations.change_process
statement: Assumed operations.change_process is Infrastructure changes managed via
pull requests with required approvals and automated GitHub Actions CI/CD pipelines.
Derived from request and scope specification indicating pull-request driven changes
with peer review and GitHub Actions CI/CD automation.
impact_if_invalid: Changes change enablement and release.
- id: ASSUMP-05
field: organisation.existing_teams
statement: 'Assumed organisation.existing_teams is []. Catalogue default: no existing
operational teams assumed; roles to be provisioned under provider-operated model.'
impact_if_invalid: Changes which Roles are new and which are filled.
- id: ASSUMP-06
field: service_management.tooling
statement: 'Assumed service_management.tooling is Google Cloud Operations Suite
(Cloud Monitoring and Cloud Logging). Catalogue default: Google Cloud Operations
Suite (Cloud Monitoring and Cloud Logging) with no separate third-party ticketing
system mandated.'
impact_if_invalid: Changes tooling and the processes written for it.
- id: ASSUMP-07
field: service_levels.priority_1_response_minutes
statement: Assumed service_levels.priority_1_response_minutes is 30. Catalogue default
for Priority 1 incident response acknowledgement.
impact_if_invalid: Changes on-call arrangements and staffing.
- id: ASSUMP-08
field: service_levels.recovery_time_hours
statement: Assumed service_levels.recovery_time_hours is 4. Catalogue default and
aligned with target 4-hour RTO for warm standby disaster recovery in secondary
region.
impact_if_invalid: Changes continuity arrangements.
discovery_gaps:
- field: metadata.client_name
prompt: What is metadata.client_name?
severity: LOW
- field: metadata.author
prompt: What is metadata.author?
severity: LOW
- field: metadata.revision
prompt: What is metadata.revision?
severity: LOW
- field: intent.requirements
prompt: Which requirements for operations has the customer stated outright?
severity: LOW
- field: solution.inherited_risks
prompt: What is already known to be unverified or at risk in the solution?
severity: LOW
- field: operations.monitoring
prompt: Which monitoring and alerting is already in place or required?
severity: LOW
- field: organisation.headcount_limit
prompt: Is there a limit on the number of people operating this?
severity: LOW
- field: commercial.monthly_run_budget
prompt: Is there a monthly budget for operating this, in that currency?
severity: LOW
- field: transition.go_live_date
prompt: When must the solution be in operation?
severity: LOW
- field: run.overlay_skills
prompt: Which overlay Skills should this Execution load?
severity: LOW
provenance:
commercial.currency: digested
commercial.monthly_run_budget: unknown
compliance.frameworks: digested
engagement.kind: digested
intent.business_outcomes: assumed
intent.exclusions: assumed
intent.requirements: unknown
intent.statement: digested
metadata.author: unknown
metadata.client_name: unknown
metadata.customer_case: digested
metadata.revision: unknown
metadata.source: digested
operations.availability_hours: digested
operations.change_process: assumed
operations.monitoring: unknown
operations.support_hours: digested
organisation.existing_teams: assumed
organisation.headcount_limit: unknown
run.overlay_skills: unknown
run.pre_approved: supplied
service_levels.priority_1_response_minutes: assumed
service_levels.recovery_time_hours: assumed
service_management.tooling: assumed
solution.build.customer_owned: digested
solution.build.duration_days: assumed
solution.cloud_provider: digested
solution.conditions: digested
solution.inherited_risks: unknown
solution.items: digested
sourcing.delivery_countries: supplied
sourcing.model: supplied
transition.go_live_date: unknown
readiness:
supplied: 3
answered: 0
assumed: 8
unknown: 10
not_applicable: 0
digested: 12

View File

@@ -0,0 +1,144 @@
{
"currency": "GBP",
"rate_card": {
"name": "rate-card",
"version": "draft-2026-10-13",
"draft": true
},
"conversion": {
"from": "USD",
"rate": 0.79,
"as_of": "2026-10-13"
},
"roles": [
{
"role": "R-1",
"name": "Platform Reliability Lead",
"party": "P-1",
"party_name": "Managed Service Provider",
"country": "GB",
"level": "lead",
"hours": "business",
"effort_hours_per_month": 18.0,
"people": 0.1,
"cost_per_month": 1991
},
{
"role": "R-2",
"name": "Platform SRE",
"party": "P-1",
"party_name": "Managed Service Provider",
"country": "PL",
"level": "senior",
"hours": "24x7",
"effort_hours_per_month": 138.0,
"people": 5.0,
"cost_per_month": 41640
},
{
"role": "R-3",
"name": "Security Analyst",
"party": "P-1",
"party_name": "Managed Service Provider",
"country": "IN",
"level": "senior",
"hours": "24x7",
"effort_hours_per_month": 85.0,
"people": 5.0,
"cost_per_month": 24605
},
{
"role": "R-4",
"name": "Platform Engineer",
"party": "P-1",
"party_name": "Managed Service Provider",
"country": "PL",
"level": "senior",
"hours": "business",
"effort_hours_per_month": 171.0,
"people": 1.2,
"cost_per_month": 7768
},
{
"role": "R-5",
"name": "Enablement Specialist",
"party": "P-1",
"party_name": "Managed Service Provider",
"country": "GB",
"level": "senior",
"hours": "business",
"effort_hours_per_month": 50.0,
"people": 0.4,
"cost_per_month": 4213
},
{
"role": "R-6",
"name": "Compliance Officer",
"party": "P-1",
"party_name": "Managed Service Provider",
"country": "GB",
"level": "lead",
"hours": "business",
"effort_hours_per_month": 30.0,
"people": 0.2,
"cost_per_month": 3318
},
{
"role": "R-7",
"name": "Product Manager",
"party": "P-1",
"party_name": "Managed Service Provider",
"country": "GB",
"level": "lead",
"hours": "business",
"effort_hours_per_month": 40.0,
"people": 0.3,
"cost_per_month": 4424
},
{
"role": "R-8",
"name": "Customer Service Owner",
"party": "P-2",
"party_name": "Customer Organization",
"country": "GB",
"level": "lead",
"hours": "business",
"effort_hours_per_month": 0.0,
"people": 0.0,
"cost_per_month": null
}
],
"people": 12.2,
"cost_per_month": 87959,
"by_party": {
"P-1": 87959
},
"by_country": {
"GB": 13946,
"PL": 49408,
"IN": 24605
},
"by_capability": {
"C-14": 885,
"C-20": 1106,
"C-1": 12069,
"C-2": 18104,
"C-4": 9052,
"C-15": 2414,
"C-12": 7237,
"C-13": 17368,
"C-3": 909,
"C-5": 909,
"C-6": 909,
"C-7": 681,
"C-8": 454,
"C-9": 727,
"C-10": 454,
"C-11": 909,
"C-17": 1817,
"C-18": 3371,
"C-19": 843,
"C-21": 3318,
"C-16": 4424
}
}

View File

@@ -0,0 +1,742 @@
{
"parties": [
{
"name": "Managed Service Provider",
"kind": "provider",
"id": "P-1"
},
{
"name": "Customer Organization",
"id": "P-2",
"kind": "customer"
}
],
"teams": [
{
"name": "Platform Engineering Team",
"type": "platform",
"id": "T-1",
"party": "P-1"
},
{
"id": "T-2",
"type": "platform",
"party": "P-1",
"name": "Platform Operations Team"
},
{
"type": "platform",
"id": "T-3",
"name": "Security Operations Team",
"purpose": "24x7 Security Monitoring and Response",
"party": "P-1"
},
{
"type": "enabling",
"id": "T-4",
"name": "Developer Enablement Team",
"party": "P-1"
},
{
"id": "T-5",
"name": "Customer Governance and App Squads",
"party": "P-2",
"type": "stream_aligned"
}
],
"roles": [
{
"party": "P-1",
"team": "T-1",
"level": "lead",
"name": "Platform Reliability Lead",
"country": "GB",
"id": "R-1",
"hours": "business"
},
{
"id": "R-2",
"level": "senior",
"party": "P-1",
"country": "PL",
"hours": "24x7",
"name": "Platform SRE",
"team": "T-2"
},
{
"country": "IN",
"id": "R-3",
"level": "senior",
"party": "P-1",
"hours": "24x7",
"name": "Security Analyst",
"team": "T-3"
},
{
"level": "senior",
"party": "P-1",
"name": "Platform Engineer",
"hours": "business",
"country": "PL",
"id": "R-4",
"team": "T-1"
},
{
"level": "senior",
"party": "P-1",
"id": "R-5",
"hours": "business",
"name": "Enablement Specialist",
"country": "GB",
"team": "T-4"
},
{
"team": "T-1",
"id": "R-6",
"country": "GB",
"hours": "business",
"name": "Compliance Officer",
"party": "P-1",
"level": "lead"
},
{
"id": "R-7",
"country": "GB",
"party": "P-1",
"level": "lead",
"team": "T-1",
"hours": "business",
"name": "Product Manager"
},
{
"country": "GB",
"party": "P-2",
"id": "R-8",
"level": "lead",
"team": "T-5",
"hours": "business",
"name": "Customer Service Owner"
}
],
"interactions": [
{
"mode": "x_as_a_service",
"purpose": "Application teams consume platform services through the self-service portal.",
"id": "I-1",
"from": "T-5",
"to": "T-1"
},
{
"id": "I-2",
"from": "T-4",
"to": "T-5",
"purpose": "Enablement specialists help application teams adopt golden paths and DORA metrics.",
"mode": "facilitating"
},
{
"until": "End of the 10-week foundation build period, returning to a facilitating mode.",
"mode": "collaboration",
"id": "I-3",
"to": "T-5",
"purpose": "Enablement team pairs with application teams for initial workload ingestion.",
"from": "T-4"
}
],
"measures": [
{
"layer": "outcome",
"name": "Deployment frequency",
"framework": "dora-metrics",
"measured_by": "C-19",
"target": "Multiple times a day",
"id": "M-1",
"outcome": "BO-3"
},
{
"target": "Positive trend",
"outcome": "BO-3",
"framework": "space-framework",
"measured_by": "C-19",
"name": "Satisfaction and well-being",
"id": "M-2",
"layer": "guardrail"
},
{
"framework": "devex-framework",
"name": "Feedback loops",
"target": "Minimal friction",
"measured_by": "C-19",
"id": "M-3",
"layer": "leading",
"outcome": "BO-3"
},
{
"target": "99.9%",
"id": "M-4",
"layer": "service_level",
"outcome": "BO-1",
"name": "Platform Availability",
"measured_by": "C-15"
},
{
"layer": "service_level",
"id": "M-5",
"target": "Under 30 minutes",
"name": "Incident Response Time",
"measured_by": "C-15",
"outcome": "BO-1"
},
{
"outcome": "BO-2",
"name": "Compliance Audit Pass Rate",
"measured_by": "C-21",
"layer": "service_level",
"id": "M-6",
"target": "100%"
}
],
"responsibilities": [
{
"role": "R-1",
"capability": "C-1",
"kind": "accountable",
"id": "RS-1"
},
{
"id": "RS-2",
"capability": "C-2",
"kind": "accountable",
"role": "R-1"
},
{
"role": "R-1",
"capability": "C-3",
"id": "RS-3",
"kind": "accountable"
},
{
"role": "R-1",
"capability": "C-4",
"id": "RS-4",
"kind": "accountable"
},
{
"role": "R-1",
"capability": "C-5",
"id": "RS-5",
"kind": "accountable"
},
{
"capability": "C-6",
"id": "RS-6",
"role": "R-1",
"kind": "accountable"
},
{
"role": "R-1",
"kind": "accountable",
"capability": "C-7",
"id": "RS-7"
},
{
"kind": "accountable",
"role": "R-1",
"id": "RS-8",
"capability": "C-8"
},
{
"kind": "accountable",
"capability": "C-9",
"id": "RS-9",
"role": "R-1"
},
{
"kind": "accountable",
"id": "RS-10",
"capability": "C-10",
"role": "R-1"
},
{
"id": "RS-11",
"kind": "accountable",
"capability": "C-11",
"role": "R-6"
},
{
"capability": "C-12",
"role": "R-6",
"id": "RS-12",
"kind": "accountable"
},
{
"id": "RS-13",
"kind": "accountable",
"capability": "C-13",
"role": "R-6"
},
{
"capability": "C-14",
"kind": "accountable",
"id": "RS-14",
"role": "R-7"
},
{
"kind": "accountable",
"role": "R-1",
"capability": "C-15",
"id": "RS-15"
},
{
"role": "R-7",
"capability": "C-16",
"kind": "accountable",
"id": "RS-16"
},
{
"role": "R-7",
"capability": "C-17",
"kind": "accountable",
"id": "RS-17"
},
{
"capability": "C-18",
"role": "R-7",
"id": "RS-18",
"kind": "accountable"
},
{
"id": "RS-19",
"kind": "accountable",
"capability": "C-19",
"role": "R-7"
},
{
"id": "RS-20",
"capability": "C-20",
"kind": "accountable",
"role": "R-1"
},
{
"role": "R-6",
"capability": "C-21",
"id": "RS-21",
"kind": "accountable"
},
{
"capability": "C-1",
"kind": "responsible",
"role": "R-2",
"id": "RS-22"
},
{
"id": "RS-23",
"role": "R-2",
"capability": "C-2",
"kind": "responsible"
},
{
"kind": "responsible",
"role": "R-4",
"capability": "C-3",
"id": "RS-24"
},
{
"role": "R-2",
"id": "RS-25",
"kind": "responsible",
"capability": "C-4"
},
{
"kind": "responsible",
"id": "RS-26",
"capability": "C-5",
"role": "R-4"
},
{
"role": "R-4",
"kind": "responsible",
"id": "RS-27",
"capability": "C-6"
},
{
"id": "RS-28",
"kind": "responsible",
"role": "R-4",
"capability": "C-7"
},
{
"id": "RS-29",
"role": "R-4",
"capability": "C-8",
"kind": "responsible"
},
{
"capability": "C-9",
"role": "R-4",
"kind": "responsible",
"id": "RS-30"
},
{
"capability": "C-10",
"id": "RS-31",
"role": "R-4",
"kind": "responsible"
},
{
"capability": "C-11",
"role": "R-4",
"id": "RS-32",
"kind": "responsible"
},
{
"capability": "C-12",
"kind": "responsible",
"id": "RS-33",
"role": "R-3"
},
{
"kind": "responsible",
"id": "RS-34",
"capability": "C-13",
"role": "R-3"
},
{
"role": "R-1",
"kind": "responsible",
"capability": "C-14",
"id": "RS-35"
},
{
"id": "RS-36",
"kind": "responsible",
"capability": "C-15",
"role": "R-2"
},
{
"kind": "responsible",
"capability": "C-16",
"role": "R-7",
"id": "RS-37"
},
{
"id": "RS-38",
"capability": "C-17",
"role": "R-4",
"kind": "responsible"
},
{
"role": "R-5",
"id": "RS-39",
"kind": "responsible",
"capability": "C-18"
},
{
"id": "RS-40",
"role": "R-5",
"kind": "responsible",
"capability": "C-19"
},
{
"kind": "responsible",
"id": "RS-41",
"role": "R-1",
"capability": "C-20"
},
{
"kind": "responsible",
"role": "R-6",
"id": "RS-42",
"capability": "C-21"
},
{
"role": "R-8",
"id": "RS-43",
"kind": "consulted",
"capability": "C-1"
},
{
"kind": "consulted",
"role": "R-8",
"id": "RS-44",
"capability": "C-2"
},
{
"id": "RS-45",
"kind": "consulted",
"capability": "C-3",
"role": "R-8"
},
{
"capability": "C-4",
"role": "R-8",
"kind": "consulted",
"id": "RS-46"
},
{
"capability": "C-5",
"kind": "consulted",
"role": "R-8",
"id": "RS-47"
},
{
"kind": "consulted",
"capability": "C-6",
"role": "R-8",
"id": "RS-48"
},
{
"id": "RS-49",
"capability": "C-7",
"role": "R-8",
"kind": "consulted"
},
{
"role": "R-8",
"kind": "consulted",
"capability": "C-8",
"id": "RS-50"
},
{
"id": "RS-51",
"capability": "C-9",
"role": "R-8",
"kind": "consulted"
},
{
"id": "RS-52",
"capability": "C-10",
"role": "R-8",
"kind": "consulted"
},
{
"capability": "C-11",
"id": "RS-53",
"role": "R-8",
"kind": "consulted"
},
{
"capability": "C-12",
"role": "R-8",
"kind": "consulted",
"id": "RS-54"
},
{
"role": "R-8",
"kind": "consulted",
"id": "RS-55",
"capability": "C-13"
},
{
"role": "R-8",
"kind": "consulted",
"capability": "C-14",
"id": "RS-56"
},
{
"capability": "C-15",
"kind": "consulted",
"role": "R-8",
"id": "RS-57"
},
{
"role": "R-8",
"kind": "consulted",
"id": "RS-58",
"capability": "C-16"
},
{
"role": "R-8",
"kind": "consulted",
"capability": "C-17",
"id": "RS-59"
},
{
"capability": "C-18",
"kind": "consulted",
"role": "R-8",
"id": "RS-60"
},
{
"id": "RS-61",
"kind": "consulted",
"role": "R-8",
"capability": "C-19"
},
{
"kind": "consulted",
"role": "R-8",
"capability": "C-20",
"id": "RS-62"
},
{
"kind": "consulted",
"role": "R-8",
"capability": "C-21",
"id": "RS-63"
}
],
"checks": [
{
"depends_on_finding": null,
"condition": "Declarative infrastructure configurations restrict data location to UK and EU regions.",
"id": "OC-1",
"source": "K-1",
"on": "C-7"
},
{
"source": "K-2",
"condition": "Warm standby capacity limits on identity, encryption, and governance components are maintained through DR automation.",
"depends_on_finding": null,
"on": "C-9",
"id": "OC-2"
},
{
"on": "C-7",
"condition": "PCI-regulated production network configurations enforce isolation from non-PCI scopes.",
"id": "OC-3",
"source": "K-3"
},
{
"source": "K-4",
"id": "OC-4",
"condition": "Workload APIs are confirmed to be routable only via private corporate network paths.",
"on": "C-7"
},
{
"id": "OC-5",
"on": "C-10",
"source": "K-5",
"condition": "Hybrid interconnect capacity metrics demonstrate SLA-backed low latency."
},
{
"condition": "Centralised inspection appliances actively perform stateful packet inspection on all egress traffic.",
"id": "OC-6",
"source": "K-6",
"on": "C-13"
},
{
"on": "C-9",
"condition": "Service continuity rehearsals demonstrate secondary region failover in under 4 hours.",
"id": "OC-7",
"source": "K-7"
},
{
"condition": "Backup validation ensures an RPO of at most 1 hour.",
"on": "C-7",
"id": "OC-8",
"depends_on_finding": "AF-3",
"source": "K-8"
},
{
"on": "C-11",
"source": "K-9",
"id": "OC-9",
"condition": "Identity access policies require Entra ID multi-factor authentication for corporate users."
},
{
"condition": "Third-party supplier reviews include DORA risk assessments.",
"id": "OC-10",
"source": "K-10",
"on": "C-20"
},
{
"on": "C-21",
"source": "K-11",
"id": "OC-11",
"condition": "Production cardholder data environments maintain PCI-DSS v4.0 network isolation control compliance."
},
{
"id": "OC-12",
"source": "K-12",
"on": "C-11",
"condition": "Confidential payment data storage systems ensure unauthorized access protection via customer-controlled keys."
},
{
"condition": "Audit logs are actively monitored for modifications and deletions.",
"source": "K-13",
"id": "OC-13",
"on": "C-13"
},
{
"condition": "Monthly availability of network routing components is tracked and meets the 99.9% target.",
"on": "C-15",
"id": "OC-14",
"source": "K-14"
},
{
"condition": "Data centres supporting operations provide publicly validated carbon-free energy (CFE) metrics.",
"on": "C-21",
"source": "K-15",
"id": "OC-15"
},
{
"id": "OC-16",
"source": "K-16",
"condition": "Workload ingestion metrics confirm operational readiness within the initial 10-week build.",
"on": "C-16"
},
{
"id": "OC-17",
"on": "C-1",
"source": "K-17",
"condition": "A 24/7 service desk is resourced to actively log and respond to infrastructure priority incidents."
},
{
"id": "OC-18",
"condition": "CI/CD pipeline hooks enforce pull request approvals, validation, and linting before merge.",
"on": "C-5",
"source": "K-18"
},
{
"id": "OC-19",
"condition": "NVA capacity tracking confirms instances utilize high-bandwidth machine families.",
"source": "K-19",
"on": "C-10"
},
{
"id": "OC-20",
"condition": "Platform budget anomaly alerts check that the warm standby uses minimal infrastructure footprint.",
"depends_on_finding": "AF-2",
"source": "K-20",
"on": "C-14"
},
{
"condition": "Disaster recovery infrastructure automation limits full-capacity scaling strictly to failover occurrences.",
"id": "OC-21",
"on": "C-9",
"source": "K-21"
},
{
"id": "OC-22",
"on": "R-1",
"source": "OR-13",
"condition": "Operations and support delivery are provided solely under the agreed service-provider framework."
},
{
"id": "OC-23",
"source": "OR-14",
"condition": "Staff are located solely in authorized delivery countries.",
"depends_on_finding": null,
"on": "R-1"
},
{
"condition": "Operational telemetry and incident logging are fully integrated into the operations suite.",
"source": "OR-15",
"id": "OC-24",
"on": "C-2"
},
{
"id": "OC-25",
"on": "C-21",
"source": "OR-24",
"condition": "Compliance audits consistently certify continuous adherence across DORA, ISO 27001, and PCI-DSS v4.0 frameworks."
},
{
"on": "C-1",
"source": "K-17",
"condition": "Incident responders use a secure remote access mechanism to troubleshoot Centralised Egress Traffic Inspection Gateways.",
"depends_on_finding": "AF-1",
"id": "OC-26"
}
]
}

View File

@@ -0,0 +1,362 @@
{
"dry_run": {
"verdict": "pass",
"evidence": "44 of 44 scenario walk-throughs pass."
},
"checks": [
{
"evidence": "Capability C-7 handles declarative state and configuration management, covering all required items. Platform Engineer (R-4) is responsible during business hours.",
"verdict": "pass",
"check": "OC-1"
},
{
"verdict": "pass",
"check": "OC-2",
"evidence": "Capability C-9 manages service continuity and DR failover rehearsals, covering items S-1, S-7, and S-9. Platform Engineer (R-4) is responsible."
},
{
"verdict": "pass",
"check": "OC-3",
"evidence": "Capability C-7 manages configuration state and audits, ensuring isolation configurations are maintained. Platform Engineer (R-4) is responsible."
},
{
"evidence": "Capability C-7 audits configuration state for workload APIs, and Platform Engineer (R-4) is responsible.",
"check": "OC-4",
"verdict": "pass"
},
{
"verdict": "pass",
"check": "OC-5",
"evidence": "Capability C-10 reviews capacity and performance metrics, including the dedicated hybrid network interconnect. Platform Engineer (R-4) is responsible."
},
{
"check": "OC-6",
"evidence": "Capability C-13 provides security monitoring and response, analyzing egress traffic inspection data 24x7 via Security Analyst (R-3).",
"verdict": "pass"
},
{
"evidence": "Capability C-9 conducts bi-monthly DR failover rehearsals to ensure the 4-hour RTO is achievable. Platform Engineer (R-4) is responsible.",
"verdict": "pass",
"check": "OC-7"
},
{
"evidence": "AF-3: The solution lacks an automated backup service or vault to ensure state and configuration achieve the maximum data loss window (RPO) of 1 hour.",
"check": "OC-8",
"verdict": "waits_on_finding",
"finding": "AF-3"
},
{
"check": "OC-9",
"evidence": "Capability C-11 covers access management and policy reviews for corporate identity gateways. Platform Engineer (R-4) is responsible.",
"verdict": "pass"
},
{
"check": "OC-10",
"evidence": "Capability C-20 conducts supplier management and service reviews, incorporating DORA risk assessments. Platform Reliability Lead (R-1) is responsible.",
"verdict": "pass"
},
{
"evidence": "Capability C-21 continuously collates regulatory evidence for PCI-DSS v4.0. Compliance Officer (R-6) is responsible.",
"check": "OC-11",
"verdict": "pass"
},
{
"evidence": "Capability C-11 governs access management for the cryptographic key management service (S-7). Platform Engineer (R-4) is responsible.",
"check": "OC-12",
"verdict": "pass"
},
{
"check": "OC-13",
"verdict": "pass",
"evidence": "Capability C-13 provides 24x7 security monitoring and response for audit logs (S-8). Security Analyst (R-3) is responsible."
},
{
"evidence": "Capability C-15 aggregates and reports on service level objectives, including availability targets. Platform SRE (R-2) is responsible.",
"check": "OC-14",
"verdict": "pass"
},
{
"evidence": "Capability C-21 collates regulatory and compliance evidence, including carbon-free energy metrics. Compliance Officer (R-6) is responsible.",
"check": "OC-15",
"verdict": "pass"
},
{
"verdict": "pass",
"evidence": "Capability C-16 manages the platform backlog and adoption roadmap to confirm workload ingestion readiness. Product Manager (R-7) is responsible.",
"check": "OC-16"
},
{
"evidence": "Capability C-1 handles 24x7 incident management, and Platform SRE (R-2) provides 24x7 coverage to log and respond to incidents.",
"check": "OC-17",
"verdict": "pass"
},
{
"evidence": "Capability C-5 manages change enablement and pull request approvals. Platform Engineer (R-4) is responsible.",
"verdict": "pass",
"check": "OC-18"
},
{
"verdict": "pass",
"check": "OC-19",
"evidence": "Capability C-10 reviews capacity and performance for network virtual appliances. Platform Engineer (R-4) is responsible."
},
{
"check": "OC-20",
"evidence": "AF-2: The solution lacks automated budget anomaly alerts out-of-the-box to track the minimal pilot light footprint of the warm standby region.",
"verdict": "waits_on_finding",
"finding": "AF-2"
},
{
"check": "OC-21",
"verdict": "pass",
"evidence": "Capability C-9 conducts service continuity failovers, managing the DR infrastructure automation. Platform Engineer (R-4) is responsible."
},
{
"evidence": "Role R-1 (Platform Reliability Lead) is part of the Managed Service Provider party, fulfilling the agreed service-provider framework.",
"verdict": "pass",
"check": "OC-22"
},
{
"verdict": "pass",
"check": "OC-23",
"evidence": "Role R-1 is located in GB, which is an authorized delivery country."
},
{
"check": "OC-24",
"verdict": "pass",
"evidence": "Capability C-2 performs continuous monitoring and alerting using the integrated operations suite. Platform SRE (R-2) is responsible 24x7."
},
{
"evidence": "Capability C-21 continuously collates audit evidence across DORA, ISO 27001, and PCI-DSS v4.0. Compliance Officer (R-6) is responsible.",
"check": "OC-25",
"verdict": "pass"
},
{
"check": "OC-26",
"evidence": "AF-1: The solution lacks a secure remote access mechanism (such as a bastion host or Identity-Aware Proxy) as a way in for responders to the Centralised Egress Traffic Inspection Gateway.",
"verdict": "waits_on_finding",
"finding": "AF-1"
},
{
"check": "SC-fault-S-1",
"verdict": "pass",
"evidence": "Multi-Tier Environment Hierarchy & Isolation Boundary (S-1) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"check": "SC-change-S-1",
"verdict": "pass",
"evidence": "Multi-Tier Environment Hierarchy & Isolation Boundary (S-1) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-2",
"verdict": "pass",
"evidence": "Dedicated Hybrid Network Interconnect Gateway (S-2) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"check": "SC-change-S-2",
"verdict": "pass",
"evidence": "Dedicated Hybrid Network Interconnect Gateway (S-2) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-3",
"verdict": "pass",
"evidence": "Centralised Egress Traffic Inspection Gateway (S-3) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"check": "SC-change-S-3",
"verdict": "pass",
"evidence": "Centralised Egress Traffic Inspection Gateway (S-3) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-4",
"verdict": "pass",
"evidence": "Transit Network Fabric & Routing Controller (S-4) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"check": "SC-change-S-4",
"verdict": "pass",
"evidence": "Transit Network Fabric & Routing Controller (S-4) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-5",
"verdict": "pass",
"evidence": "Corporate Identity Federation Gateway (S-5) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"check": "SC-change-S-5",
"verdict": "pass",
"evidence": "Corporate Identity Federation Gateway (S-5) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-6",
"verdict": "pass",
"evidence": "Automated Delivery Pipeline Identity Broker (S-6) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"check": "SC-change-S-6",
"verdict": "pass",
"evidence": "Automated Delivery Pipeline Identity Broker (S-6) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-7",
"verdict": "pass",
"evidence": "Cryptographic Key Management & Rotation Service (S-7) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"check": "SC-change-S-7",
"verdict": "pass",
"evidence": "Cryptographic Key Management & Rotation Service (S-7) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-8",
"verdict": "pass",
"evidence": "Centralised Immutable Audit Log Repository (S-8) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"check": "SC-change-S-8",
"verdict": "pass",
"evidence": "Centralised Immutable Audit Log Repository (S-8) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-9",
"verdict": "pass",
"evidence": "Platform Compliance & Governance Guardrail Controller (S-9) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"check": "SC-change-S-9",
"verdict": "pass",
"evidence": "Platform Compliance & Governance Guardrail Controller (S-9) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-10",
"verdict": "pass",
"evidence": "Declarative Infrastructure Provisioning & State Engine (S-10) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"check": "SC-change-S-10",
"verdict": "pass",
"evidence": "Declarative Infrastructure Provisioning & State Engine (S-10) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-11",
"verdict": "pass",
"evidence": "Centralised Operational Telemetry & Alerting Engine (S-11) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Reliability Lead is answerable."
},
{
"check": "SC-change-S-11",
"verdict": "pass",
"evidence": "Centralised Operational Telemetry & Alerting Engine (S-11) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-condition-K-1",
"verdict": "pass",
"evidence": "Condition K-1 must be shown to hold: Customer data and payment processing remain within United Kingdom and European Union legal jurisdictions. Check OC-1 on C-7 keeps it true."
},
{
"check": "SC-condition-K-2",
"verdict": "pass",
"evidence": "Condition K-2 must be shown to hold: Warm standby environment operates with reduced capacity until activated during a disaster recovery failover. Check OC-2 on C-9 keeps it true."
},
{
"check": "SC-condition-K-3",
"verdict": "pass",
"evidence": "Condition K-3 must be shown to hold: PCI-regulated production environment is isolated from non-PCI scopes according to PCI-DSS v4.0 network segmentation requirements. Check OC-3 on C-7 keeps it true."
},
{
"check": "SC-condition-K-4",
"verdict": "pass",
"evidence": "Condition K-4 must be shown to hold: Workload APIs and payment services are accessible exclusively through private corporate network paths. Check OC-4 on C-7 keeps it true."
},
{
"check": "SC-condition-K-5",
"verdict": "pass",
"evidence": "Condition K-5 must be shown to hold: Hybrid connection maintains low-latency, SLA-backed private data transmission between on-premises and Google Cloud. Check OC-5 on C-10 keeps it true."
},
{
"check": "SC-condition-K-6",
"verdict": "pass",
"evidence": "Condition K-6 must be shown to hold: Centralised inspection appliances perform next-generation stateful packet inspection, URL filtering, and threat detection on outbound internet sessions. Check OC-6 on C-13 keeps it true."
},
{
"check": "SC-condition-K-7",
"verdict": "pass",
"evidence": "Condition K-7 must be shown to hold: Platform foundation failover to europe-west1 can be completed within 4 hours during a primary region outage. Check OC-7 on C-9 keeps it true."
},
{
"check": "SC-condition-K-8",
"verdict": "pass",
"evidence": "Condition K-8 must be shown to hold: Configuration drift and backup state achieve a maximum data loss window (RPO) of 1 hour. Check OC-8 on C-7 keeps it true."
},
{
"check": "SC-condition-K-9",
"verdict": "pass",
"evidence": "Condition K-9 must be shown to hold: Corporate user lifecycle management and MFA enforcement are governed centrally by Entra ID conditional access policies. Check OC-9 on C-11 keeps it true."
},
{
"check": "SC-condition-K-10",
"verdict": "pass",
"evidence": "Condition K-10 must be shown to hold: Platform governance and resilience architecture comply with DORA regulatory testing and third-party risk management frameworks. Check OC-10 on C-20 keeps it true."
},
{
"check": "SC-condition-K-11",
"verdict": "pass",
"evidence": "Condition K-11 must be shown to hold: Production cardholder data environment satisfies PCI-DSS v4.0 isolation and security control requirements. Check OC-11 on C-21 keeps it true."
},
{
"check": "SC-condition-K-12",
"verdict": "pass",
"evidence": "Condition K-12 must be shown to hold: Confidential payment data is secured against unauthorized platform-level access or data exposure. Check OC-12 on C-11 keeps it true."
},
{
"check": "SC-condition-K-13",
"verdict": "pass",
"evidence": "Condition K-13 must be shown to hold: Audit logs cannot be modified, deleted, or shortened by any identity or administrator prior to retention expiration. Check OC-13 on C-13 keeps it true."
},
{
"check": "SC-condition-K-14",
"verdict": "pass",
"evidence": "Condition K-14 must be shown to hold: Monthly availability of the core platform landing zone and network routing meets or exceeds 99.9%. Check OC-14 on C-15 keeps it true."
},
{
"check": "SC-condition-K-15",
"verdict": "pass",
"evidence": "Condition K-15 must be shown to hold: Primary and secondary regions leverage Google Cloud data centres with published carbon-free energy (CFE) performance metrics. Check OC-15 on C-21 keeps it true."
},
{
"check": "SC-condition-K-16",
"verdict": "pass",
"evidence": "Condition K-16 must be shown to hold: Platform foundation delivery and workload ingestion readiness are achieved within 10 weeks of project commencement. Check OC-16 on C-16 keeps it true."
},
{
"check": "SC-condition-K-17",
"verdict": "pass",
"evidence": "Condition K-17 must be shown to hold: Central platform team operates 24/7 support for infrastructure incidents and availability alerts. Check OC-17 on C-1 keeps it true."
},
{
"check": "SC-condition-K-18",
"verdict": "pass",
"evidence": "Condition K-18 must be shown to hold: Pull request workflows require automated CI/CD linting, validation, and peer approval prior to merge and deployment. Check OC-18 on C-5 keeps it true."
},
{
"check": "SC-condition-K-19",
"verdict": "pass",
"evidence": "Condition K-19 must be shown to hold: NVA instances use machine families that support high bandwidth networking. Check OC-19 on C-10 keeps it true."
},
{
"check": "SC-condition-K-20",
"verdict": "pass",
"evidence": "Condition K-20 must be shown to hold: The warm standby environment operates at a minimal pilot light footprint during normal operations. Check OC-20 on C-14 keeps it true."
},
{
"check": "SC-condition-K-21",
"verdict": "pass",
"evidence": "Condition K-21 must be shown to hold: Automated disaster recovery scripts scale the standby environment to full capacity only during a failover event. Check OC-21 on C-9 keeps it true."
},
{
"check": "SC-party-P-1",
"verdict": "pass",
"evidence": "Managed Service Provider cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
}
],
"proposed_additions": []
}

View File

@@ -0,0 +1,19 @@
# Solution architecture to operating model, through the Orchestration engine
Run `20261021T203623Z`. One pre-approved request for `architecture_and_operating_model` to the Orchestration engine: the solution architecture agent designed from the benchmark scope spec, and its kept files went to the operating model agent as `sources`. The case is fictional; no customer's data is in it.
- **Status:** completed
- **Customer case:** case-08-landing-zone
- **Minutes, end to end:** 74.9
| Agent | Execution | Ended | Files kept |
|---|---|---|---|
| solution_architecture | 6c316f05-9643-492c-bab1-eed56e108754 | completed | 15 |
| operating_model | 1f8f30a1-7b74-4d23-9fb0-aec58089c506 | completed | 11 |
## The operating model
- Operational requirements: 24; verified by a Check: 24
- Capabilities: 21; Roles: 8; Checks: 26
- Scenarios with a path: 44 of 44
- People: 12.2; cost a month: 87,959 GBP

View File

@@ -0,0 +1,71 @@
{
"status": "completed",
"work": "architecture_and_operating_model",
"customer_case": "case-08-landing-zone",
"execution_id": "1f8f30a1-7b74-4d23-9fb0-aec58089c506",
"record": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506",
"guide": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/operating-model-guide.md",
"files": {
"capabilities.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/capabilities.json",
"findings.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/findings.json",
"operating-model-guide.md": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/operating-model-guide.md",
"operational-requirements.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/operational-requirements.json",
"organisation.mmd": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/organisation.mmd",
"scenarios.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/scenarios.json",
"scope.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/scope.json",
"scope.yaml": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/scope.yaml",
"staffing.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/staffing.json",
"target-operating-model.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/target-operating-model.json",
"verdicts.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/verdicts.json"
},
"latest": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/latest/operating_model",
"case": "http://localhost:10030/tenants/local/cases/case-08-landing-zone",
"results": {
"solution_architecture": {
"execution_id": "6c316f05-9643-492c-bab1-eed56e108754",
"status": "completed",
"record": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754",
"guide": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/solution-architecture-guide.md",
"files": {
"architecture.mmd": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/architecture.mmd",
"components.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/components.json",
"implementation.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/implementation.json",
"products.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/products.json",
"recommendations.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/recommendations.json",
"requirements.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/requirements.json",
"scope.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/scope.json",
"scope.yaml": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/scope.yaml",
"solution-architecture-guide.md": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/solution-architecture-guide.md",
"target-architecture.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/target-architecture.json",
"terraform/main.tf": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/terraform/main.tf",
"terraform/variables.tf": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/terraform/variables.tf",
"terraform/versions.tf": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/terraform/versions.tf",
"verdicts.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/verdicts.json",
"work-breakdown.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/work-breakdown.json"
},
"latest": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/latest/solution_architecture",
"case": "http://localhost:10030/tenants/local/cases/case-08-landing-zone"
},
"operating_model": {
"execution_id": "1f8f30a1-7b74-4d23-9fb0-aec58089c506",
"status": "completed",
"record": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506",
"guide": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/operating-model-guide.md",
"files": {
"capabilities.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/capabilities.json",
"findings.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/findings.json",
"operating-model-guide.md": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/operating-model-guide.md",
"operational-requirements.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/operational-requirements.json",
"organisation.mmd": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/organisation.mmd",
"scenarios.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/scenarios.json",
"scope.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/scope.json",
"scope.yaml": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/scope.yaml",
"staffing.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/staffing.json",
"target-operating-model.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/target-operating-model.json",
"verdicts.json": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/1f8f30a1-7b74-4d23-9fb0-aec58089c506/files/verdicts.json"
},
"latest": "http://localhost:10030/tenants/local/cases/case-08-landing-zone/latest/operating_model",
"case": "http://localhost:10030/tenants/local/cases/case-08-landing-zone"
}
}
}

View File

@@ -0,0 +1,72 @@
flowchart LR
n0["Dev Folder<br/>Resource Manager"]
n1["Staging Folder<br/>Resource Manager"]
n2["Production Folder<br/>Resource Manager"]
n3["Host Project<br/>Virtual Private Cloud"]
n4["Hub Network<br/>Virtual Private Cloud"]
n5["Dev Network<br/>Virtual Private Cloud"]
n6["Staging Network<br/>Virtual Private Cloud"]
n7["Production Network<br/>Virtual Private Cloud"]
n8["Dev Subnetwork<br/>Virtual Private Cloud"]
n9["Staging Subnetwork<br/>Virtual Private Cloud"]
n10["Production Subnetwork<br/>Virtual Private Cloud"]
n11["Hub-Prod Peering<br/>Virtual Private Cloud"]
n12["Hub-Dev Peering<br/>Virtual Private Cloud"]
n13["Hub-Stg Peering<br/>Virtual Private Cloud"]
n14["Interconnect Router 1<br/>Cloud Interconnect"]
n15["Interconnect Router 2<br/>Cloud Interconnect"]
n16["VLAN Attachment 1<br/>Cloud Interconnect"]
n17["VLAN Attachment 2<br/>Cloud Interconnect"]
n18["Standby Router<br/>Cloud Interconnect"]
n19["Standby VLAN Attachment<br/>Cloud Interconnect"]
n20["Standby Subnetwork<br/>Virtual Private Cloud"]
n21["NVA Instance Template<br/>Compute Engine"]
n22["NVA MIG<br/>Compute Engine"]
n23["NVA Health Check<br/>Compute Engine"]
n24["NVA Forwarding Rule<br/>Compute Engine"]
n25["NVA Autoscaler<br/>Compute Engine"]
n26["Inbound Deny Firewall<br/>Virtual Private Cloud"]
n27["Cloud Identity Group<br/>Cloud Identity"]
n28["Workload Identity Pool<br/>Workload Identity Federation"]
n29["WIF Provider<br/>Workload Identity Federation"]
n30["KMS Key Ring Primary<br/>Cloud KMS"]
n31["KMS Crypto Key Primary<br/>Cloud KMS"]
n32["KMS Key Ring Standby<br/>Cloud KMS"]
n33["KMS Crypto Key Standby<br/>Cloud KMS"]
n34["Audit Log Bucket<br/>Cloud Storage"]
n35["Org Log Sink<br/>Cloud Storage"]
n36["Org Policy Skip Default Network<br/>Organization Policy Service"]
n37["Org Policy VM External IP<br/>Organization Policy Service"]
n38["Org Policy Resource Locations<br/>Organization Policy Service"]
n39["Org Policy Service Account Keys<br/>Organization Policy Service"]
n40["SCC Config<br/>Organization Policy Service"]
n41["Prod Org Policy<br/>Organization Policy Service"]
n42["TF State Bucket<br/>Cloud Storage"]
n43["Alert Policy Interconnect<br/>Cloud Monitoring"]
n44["Alert Policy LB<br/>Cloud Monitoring"]
n45["Dev Route to NVA<br/>Virtual Private Cloud"]
n46["Staging Route to NVA<br/>Virtual Private Cloud"]
n47["Production Route to NVA<br/>Virtual Private Cloud"]
n48["Pipeline Service Account<br/>Workload Identity Federation"]
n49["Pipeline SA IAM Member<br/>Workload Identity Federation"]
n50["Org Policy UBLA<br/>Organization Policy Service"]
n51["Org Policy CMEK Enforce<br/>Organization Policy Service"]
n52["Alert Policy Audit Logs<br/>Cloud Monitoring"]
n5 -->|peers with| n4
n6 -->|peers with| n4
n7 -->|peers with| n4
n45 -->|routes to| n24
n46 -->|routes to| n24
n47 -->|routes to| n24
n29 -->|authenticates via| n28
n35 -->|exports to| n34
n16 -->|attaches to| n14
n17 -->|attaches to| n15
n19 -->|attaches to| n18
n22 -->|uses| n21
n24 -->|forwards to| n22
n22 -->|checked by| n23
n25 -->|scales| n22
n31 -->|belongs to| n30
n33 -->|belongs to| n32
n49 -->|grants access to| n48

View File

@@ -0,0 +1,57 @@
[
{
"id": "C-1",
"name": "Multi-Tier Environment Hierarchy & Isolation Boundary",
"requirements": ["FR-1", "NFR-1", "NFR-2", "NFR-8"]
},
{
"id": "C-2",
"name": "Dedicated Hybrid Network Interconnect Gateway",
"requirements": ["FR-2", "NFR-4", "NFR-6", "NFR-11"]
},
{
"id": "C-3",
"name": "Centralised Egress Traffic Inspection Gateway",
"requirements": ["FR-3", "NFR-3", "NFR-5"]
},
{
"id": "C-4",
"name": "Transit Network Fabric & Routing Controller",
"requirements": ["FR-1", "FR-2", "FR-3", "NFR-3", "NFR-6", "NFR-11"]
},
{
"id": "C-5",
"name": "Corporate Identity Federation Gateway",
"requirements": ["FR-4", "NFR-7"]
},
{
"id": "C-6",
"name": "Automated Delivery Pipeline Identity Broker",
"requirements": ["FR-5", "NFR-7", "NFR-13"]
},
{
"id": "C-7",
"name": "Cryptographic Key Management & Rotation Service",
"requirements": ["FR-6", "NFR-1", "NFR-9"]
},
{
"id": "C-8",
"name": "Centralised Immutable Audit Log Repository",
"requirements": ["FR-7", "NFR-10", "NFR-14"]
},
{
"id": "C-9",
"name": "Platform Compliance & Governance Guardrail Controller",
"requirements": ["FR-1", "NFR-1", "NFR-2", "NFR-8", "NFR-12"]
},
{
"id": "C-10",
"name": "Declarative Infrastructure Provisioning & State Engine",
"requirements": ["FR-5", "NFR-13", "NFR-14"]
},
{
"id": "C-11",
"name": "Centralised Operational Telemetry & Alerting Engine",
"requirements": ["NFR-11", "NFR-14"]
}
]

View File

@@ -0,0 +1,123 @@
[
{"check": "K-1", "file": "terraform/main.tf", "address": "google_org_policy_policy.resource_locations.spec"},
{"check": "K-2", "file": "terraform/main.tf", "address": "google_compute_subnetwork.dev.region"},
{"check": "K-3", "file": "terraform/main.tf", "address": "google_compute_subnetwork.staging.region"},
{"check": "K-4", "file": "terraform/main.tf", "address": "google_compute_subnetwork.production.region"},
{"check": "K-5", "file": "terraform/main.tf", "address": "google_compute_router.interconnect_1.region"},
{"check": "K-6", "file": "terraform/main.tf", "address": "google_compute_router.interconnect_2.region"},
{"check": "K-7", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.vlan_1.region"},
{"check": "K-8", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.vlan_2.region"},
{"check": "K-9", "file": "terraform/main.tf", "address": "google_compute_region_instance_group_manager.nva.region"},
{"check": "K-10", "file": "terraform/main.tf", "address": "google_compute_subnetwork.standby.region"},
{"check": "K-11", "file": "terraform/main.tf", "address": "google_compute_router.standby.region"},
{"check": "K-12", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.standby_vlan.region"},
{"check": "K-13", "file": "terraform/main.tf", "address": "google_folder.dev.display_name"},
{"check": "K-14", "file": "terraform/main.tf", "address": "google_folder.staging.display_name"},
{"check": "K-15", "file": "terraform/main.tf", "address": "google_folder.production.display_name"},
{"check": "K-16", "file": "terraform/main.tf", "address": "google_compute_firewall.inbound_deny.deny"},
{"check": "K-17", "file": "terraform/main.tf", "address": "google_org_policy_policy.prod_org_policy.parent"},
{"check": "K-18", "file": "terraform/main.tf", "address": "google_compute_shared_vpc_host_project.host.project"},
{"check": "K-19", "file": "terraform/main.tf", "address": "google_compute_network_peering.hub_prod.peer_network"},
{"check": "K-20", "file": "terraform/main.tf", "address": "google_compute_network_peering.hub_dev.peer_network"},
{"check": "K-21", "file": "terraform/main.tf", "address": "google_compute_network_peering.hub_stg.peer_network"},
{"check": "K-22", "file": "terraform/main.tf", "address": "google_compute_subnetwork.dev.private_ip_google_access"},
{"check": "K-23", "file": "terraform/main.tf", "address": "google_compute_subnetwork.staging.private_ip_google_access"},
{"check": "K-24", "file": "terraform/main.tf", "address": "google_compute_subnetwork.production.private_ip_google_access"},
{"check": "K-25", "file": "terraform/main.tf", "address": "google_compute_network.dev.delete_default_routes_on_create"},
{"check": "K-26", "file": "terraform/main.tf", "address": "google_compute_network.staging.delete_default_routes_on_create"},
{"check": "K-27", "file": "terraform/main.tf", "address": "google_compute_network.production.delete_default_routes_on_create"},
{"check": "K-28", "file": "terraform/main.tf", "address": "google_compute_firewall.inbound_deny.source_ranges"},
{"check": "K-29", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.vlan_1.bandwidth"},
{"check": "K-30", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.vlan_2.bandwidth"},
{"check": "K-31", "file": "terraform/main.tf", "address": "google_compute_router.interconnect_1.bgp"},
{"check": "K-32", "file": "terraform/main.tf", "address": "google_compute_router.interconnect_2.bgp"},
{"check": "K-33", "file": "terraform/main.tf", "address": "google_compute_router.interconnect_1.network"},
{"check": "K-34", "file": "terraform/main.tf", "address": "google_compute_network.hub.name"},
{"check": "K-35", "file": "terraform/main.tf", "address": "google_compute_route.dev_nva.next_hop_ilb"},
{"check": "K-36", "file": "terraform/main.tf", "address": "google_compute_route.staging_nva.next_hop_ilb"},
{"check": "K-37", "file": "terraform/main.tf", "address": "google_compute_route.production_nva.next_hop_ilb"},
{"check": "K-38", "file": "terraform/main.tf", "address": "google_compute_network.dev.delete_default_routes_on_create"},
{"check": "K-39", "file": "terraform/main.tf", "address": "google_compute_network.staging.delete_default_routes_on_create"},
{"check": "K-40", "file": "terraform/main.tf", "address": "google_compute_network.production.delete_default_routes_on_create"},
{"check": "K-41", "file": "terraform/main.tf", "address": "google_compute_subnetwork.standby.region"},
{"check": "K-42", "file": "terraform/main.tf", "address": "google_compute_router.standby.region"},
{"check": "K-43", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.standby_vlan.region"},
{"check": "K-44", "file": "terraform/main.tf", "address": "google_iam_workload_identity_pool.wif_pool.workload_identity_pool_id"},
{"check": "K-45", "file": "terraform/main.tf", "address": "google_iam_workload_identity_pool_provider.wif_provider.oidc"},
{"check": "K-46", "file": "terraform/main.tf", "address": "google_service_account_iam_member.pipeline_wif.member"},
{"check": "K-47", "file": "terraform/main.tf", "address": "google_org_policy_policy.sa_keys.spec"},
{"check": "K-48", "file": "terraform/main.tf", "address": "google_cloud_identity_group.group.parent"},
{"check": "K-49", "file": "terraform/main.tf", "address": "google_org_policy_policy.ubla.spec"},
{"check": "K-50", "file": "terraform/main.tf", "address": "google_org_policy_policy.cmek_enforce.spec"},
{"check": "K-51", "file": "terraform/main.tf", "address": "google_org_policy_policy.vm_external_ip.spec"},
{"check": "K-52", "file": "terraform/main.tf", "address": "google_scc_organization_custom_module.scc_config.custom_config"},
{"check": "K-53", "file": "terraform/main.tf", "address": "google_kms_key_ring.primary.location"},
{"check": "K-54", "file": "terraform/main.tf", "address": "google_kms_crypto_key.primary.rotation_period"},
{"check": "K-55", "file": "terraform/main.tf", "address": "google_kms_key_ring.standby.location"},
{"check": "K-56", "file": "terraform/main.tf", "address": "google_kms_crypto_key.standby.rotation_period"},
{"check": "K-57", "file": "terraform/main.tf", "address": "google_org_policy_policy.cmek_enforce.spec"},
{"check": "K-58", "file": "terraform/main.tf", "address": "google_logging_organization_sink.org_sink.destination"},
{"check": "K-59", "file": "terraform/main.tf", "address": "google_storage_bucket.audit_log.retention_policy"},
{"check": "K-60", "file": "terraform/main.tf", "address": "google_storage_bucket.audit_log.retention_policy"},
{"check": "K-61", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.vlan_1.edge_availability_domain"},
{"check": "K-62", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.vlan_2.edge_availability_domain"},
{"check": "K-63", "file": "terraform/main.tf", "address": "google_compute_region_instance_group_manager.nva.distribution_policy_zones"},
{"check": "K-64", "file": "terraform/main.tf", "address": "google_org_policy_policy.resource_locations.spec"},
{"check": "K-65", "file": "terraform/main.tf", "address": "google_storage_bucket.tf_state.name"},
{"check": "K-66", "file": "terraform/main.tf", "address": "google_storage_bucket.tf_state.versioning"},
{"check": "K-67", "file": "terraform/main.tf", "address": "google_storage_bucket.tf_state.encryption"},
{"check": "K-68", "file": "terraform/main.tf", "address": "google_monitoring_alert_policy.interconnect.conditions"},
{"check": "K-69", "file": "terraform/main.tf", "address": "google_monitoring_alert_policy.lb.conditions"},
{"check": "K-70", "file": "terraform/main.tf", "address": "google_monitoring_alert_policy.audit_logs.conditions"},
{"check": "K-71", "file": "terraform/main.tf", "address": "google_storage_bucket.audit_log.labels"},
{"check": "K-72", "file": "terraform/main.tf", "address": "google_org_policy_policy.skip_default_network.spec"},
{"check": "K-73", "file": "terraform/main.tf", "address": "google_org_policy_policy.vm_external_ip.spec"},
{"check": "K-74", "file": "terraform/main.tf", "address": "google_org_policy_policy.resource_locations.spec"},
{"check": "K-75", "file": "terraform/main.tf", "address": "google_org_policy_policy.sa_keys.spec"},
{"check": "K-76", "file": "terraform/main.tf", "address": "google_compute_forwarding_rule.nva.load_balancing_scheme"},
{"check": "K-77", "file": "terraform/main.tf", "address": "google_compute_route.dev_nva.next_hop_ilb"},
{"check": "K-78", "file": "terraform/main.tf", "address": "google_compute_route.staging_nva.next_hop_ilb"},
{"check": "K-79", "file": "terraform/main.tf", "address": "google_compute_route.production_nva.next_hop_ilb"},
{"check": "K-80", "file": "terraform/main.tf", "address": "google_compute_region_instance_group_manager.nva.base_instance_name"},
{"check": "K-81", "file": "terraform/main.tf", "address": "google_compute_region_instance_group_manager.nva.auto_healing_policies"},
{"check": "K-82", "file": "terraform/main.tf", "address": "google_compute_region_autoscaler.nva.target"},
{"check": "K-83", "file": "terraform/main.tf", "address": "google_compute_instance_template.nva.network_interface"},
{"check": "K-84", "file": "terraform/main.tf", "address": "google_compute_router.interconnect_1.network"},
{"check": "K-85", "file": "terraform/main.tf", "address": "google_compute_router.interconnect_2.network"},
{"check": "K-86", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.vlan_1.router"},
{"check": "K-87", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.vlan_2.router"},
{"check": "K-88", "file": "terraform/main.tf", "address": "google_compute_network.hub.routing_mode"},
{"check": "K-89", "file": "terraform/main.tf", "address": "google_compute_router.interconnect_1.bgp"},
{"check": "K-90", "file": "terraform/main.tf", "address": "google_compute_router.interconnect_2.bgp"},
{"check": "K-91", "file": "terraform/main.tf", "address": "google_kms_key_ring.primary.location"},
{"check": "K-92", "file": "terraform/main.tf", "address": "google_kms_key_ring.standby.location"},
{"check": "K-93", "file": "terraform/main.tf", "address": "google_kms_crypto_key.primary.rotation_period"},
{"check": "K-94", "file": "terraform/main.tf", "address": "google_kms_crypto_key.standby.rotation_period"},
{"check": "K-95", "file": "terraform/main.tf", "address": "google_storage_bucket.audit_log.retention_policy"},
{"check": "K-96", "file": "terraform/main.tf", "address": "google_storage_bucket.audit_log.retention_policy"},
{"check": "K-97", "file": "terraform/main.tf", "address": "google_storage_bucket.audit_log.lifecycle_rule"},
{"check": "K-98", "file": "terraform/main.tf", "address": "google_storage_bucket.tf_state.versioning"},
{"check": "K-99", "file": "terraform/main.tf", "address": "google_storage_bucket.tf_state.encryption"},
{"check": "K-100", "file": "terraform/main.tf", "address": "google_storage_bucket.tf_state.lifecycle_rule"},
{"check": "K-101", "file": "terraform/main.tf", "address": "google_iam_workload_identity_pool_provider.wif_provider.attribute_condition"},
{"check": "K-102", "file": "terraform/main.tf", "address": "google_monitoring_alert_policy.interconnect.conditions"},
{"check": "K-103", "file": "terraform/main.tf", "address": "google_monitoring_alert_policy.lb.conditions"},
{"check": "K-104", "file": "terraform/main.tf", "address": "google_compute_network.hub.mtu"},
{"check": "K-105", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.vlan_1.mtu"},
{"check": "K-106", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.vlan_2.mtu"},
{"check": "K-107", "file": "terraform/main.tf", "address": "google_compute_region_health_check.nva.check_interval_sec"},
{"check": "K-108", "file": "terraform/main.tf", "address": "google_service_account.pipeline_sa.account_id"},
{"check": "K-109", "file": "terraform/main.tf", "address": "google_compute_router.interconnect_2.network"},
{"check": "K-110", "file": "terraform/main.tf", "address": "google_storage_bucket.tf_state.labels"},
{"check": "K-111", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.vlan_1.labels"},
{"check": "K-112", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.vlan_2.labels"},
{"check": "K-113", "file": "terraform/main.tf", "address": "google_compute_interconnect_attachment.standby_vlan.labels"},
{"check": "K-114", "file": "terraform/main.tf", "address": "google_compute_instance_template.nva.labels"},
{"check": "K-115", "file": "terraform/main.tf", "address": "google_compute_forwarding_rule.nva.labels"},
{"check": "K-116", "file": "terraform/main.tf", "address": "google_cloud_identity_group.group.labels"},
{"check": "K-117", "file": "terraform/main.tf", "address": "google_kms_crypto_key.primary.labels"},
{"check": "K-118", "file": "terraform/main.tf", "address": "google_kms_crypto_key.standby.labels"},
{"check": "K-119", "file": "terraform/main.tf", "address": "google_storage_bucket.tf_state.labels"},
{"check": "K-120", "file": "terraform/main.tf", "address": "google_compute_router.interconnect_1.bgp"},
{"check": "K-121", "file": "terraform/main.tf", "address": "google_compute_router.interconnect_2.bgp"}
]

View File

@@ -0,0 +1,13 @@
[
{"component": "C-1", "product": "Resource Manager"},
{"component": "C-2", "product": "Cloud Interconnect"},
{"component": "C-3", "product": "Compute Engine"},
{"component": "C-4", "product": "Virtual Private Cloud"},
{"component": "C-5", "product": "Cloud Identity"},
{"component": "C-6", "product": "Workload Identity Federation"},
{"component": "C-7", "product": "Cloud KMS"},
{"component": "C-8", "product": "Cloud Storage"},
{"component": "C-9", "product": "Organization Policy Service"},
{"component": "C-10", "product": "Cloud Storage"},
{"component": "C-11", "product": "Cloud Monitoring"}
]

View File

@@ -0,0 +1,123 @@
[
{
"id": "DR-1",
"pillar": "security",
"text": "Enforce strict security and compliance guardrails across the resource hierarchy using Organization Policy.",
"components": ["C-9"],
"conditions": [
"The compute.skipDefaultNetworkCreation constraint is enforced.",
"The compute.vmExternalIpAccess constraint is enforced.",
"The gcp.resourceLocations constraint is restricted to the allowed regions.",
"The iam.disableServiceAccountKeyCreation constraint is enforced."
]
},
{
"id": "DR-2",
"pillar": "security",
"text": "Route outbound internet traffic symmetrically through highly available inspection appliances.",
"components": ["C-3", "C-4"],
"conditions": [
"An internal passthrough network load balancer is deployed in the transit VPC.",
"A custom route is configured in the spoke VPCs directing 0.0.0.0/0 traffic to the internal network load balancer."
]
},
{
"id": "DR-3",
"pillar": "reliability",
"text": "Deploy Network Virtual Appliances (NVAs) for resilience, elasticity, and high throughput.",
"components": ["C-3"],
"conditions": [
"The NVA instances are deployed in a regional Managed Instance Group.",
"The NVA Managed Instance Group is configured with auto-healing using a health check.",
"The NVA Managed Instance Group is configured with autoscaling.",
"The NVA Compute Engine instances are configured to use the gVNIC network interface."
],
"outside_code": [
"NVA instances use machine families that support high bandwidth networking."
]
},
{
"id": "DR-4",
"pillar": "reliability",
"text": "Configure Dedicated Cloud Interconnect for high availability and optimal latency.",
"components": ["C-2", "C-4"],
"conditions": [
"At least two Cloud Routers are deployed in the transit Shared VPC.",
"Redundant Interconnect VLAN attachments are configured on the Cloud Routers.",
"The Cloud Routers are configured for regional dynamic routing.",
"The Cloud Routers are configured with tuned BGP keepalive and hold timers."
]
},
{
"id": "DR-5",
"pillar": "security",
"text": "Ensure resilient and compliant cryptographic key management.",
"components": ["C-7"],
"conditions": [
"Cloud KMS key rings are provisioned in both the primary and standby regions.",
"Customer-managed encryption keys (CMEK) are configured with a rotation period of 90 days."
]
},
{
"id": "DR-6",
"pillar": "cost-optimization",
"text": "Configure the centralized audit log repository for compliance immutability and cost-efficient storage tiering.",
"components": ["C-8"],
"conditions": [
"The audit log Cloud Storage bucket is configured with a retention policy.",
"The retention policy on the audit log bucket is locked.",
"An Object Lifecycle Management policy is configured to transition objects to colder storage classes."
]
},
{
"id": "DR-7",
"pillar": "operational-excellence",
"text": "Secure and govern the Terraform remote state repository to prevent configuration drift and storage bloat.",
"components": ["C-10"],
"conditions": [
"The Terraform state Cloud Storage bucket has object versioning enabled.",
"The Terraform state bucket is encrypted with a customer-managed encryption key.",
"An Object Lifecycle Management policy is configured to delete non-current versions of the state objects."
]
},
{
"id": "DR-8",
"pillar": "security",
"text": "Restrict automated delivery pipelines identity federation to authorized repositories.",
"components": ["C-6"],
"conditions": [
"The Workload Identity Pool Provider is configured with an attribute condition restricting access to specific GitHub repositories."
]
},
{
"id": "DR-9",
"pillar": "operational-excellence",
"text": "Implement centralized health checking and telemetry alerting for critical hybrid and inspection components.",
"components": ["C-11"],
"conditions": [
"Cloud Monitoring alerting policies are configured for interconnect BGP session health.",
"Cloud Monitoring alerting policies are configured for NVA load balancer health checks."
]
},
{
"id": "DR-10",
"pillar": "performance-optimization",
"text": "Optimize network maximum transmission unit (MTU) across the transit fabric and hybrid interconnect.",
"components": ["C-2", "C-4"],
"conditions": [
"The Shared VPC network is configured with a custom MTU setting.",
"The Interconnect VLAN attachments are configured with a matching MTU."
]
},
{
"id": "DR-11",
"pillar": "sustainability",
"text": "Configure the warm standby environment to operate with a reduced footprint to minimize idle carbon emissions.",
"components": ["C-3"],
"conditions": [],
"outside_code": [
"The warm standby environment operates at a minimal pilot light footprint during normal operations.",
"Automated disaster recovery scripts scale the standby environment to full capacity only during a failover event."
]
}
]

View File

@@ -0,0 +1 @@
{"tenant":"local","customer_case":"case-08-landing-zone","execution_id":"6c316f05-9643-492c-bab1-eed56e108754","work":"solution_architecture","status":"completed","request":"We are a UK-regulated payment platform expanding into Google Cloud. We need an enterprise-grade landing zone ready in under 10 weeks to support our core payments engine. All payment processing must comply with DORA and PCI-DSS v4.0. We have existing on-premises systems that require private, low-latency connectivity over a 10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and GitHub Actions for our delivery pipelines. Security requires that all egress traffic flows through centralised inspection appliances before touching the public internet, and customer data must be encrypted with keys we control.","project_id":null,"guide":"solution-architecture-guide.md","files":["architecture.mmd","components.json","implementation.json","products.json","recommendations.json","requirements.json","scope.json","scope.yaml","solution-architecture-guide.md","target-architecture.json","terraform/main.tf","terraform/variables.tf","terraform/versions.tf","verdicts.json","work-breakdown.json"],"kept_at":"2026-10-21T21:26:33.819300+00:00","links":{"record":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754","guide":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/solution-architecture-guide.md","files":{"architecture.mmd":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/architecture.mmd","components.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/components.json","implementation.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/implementation.json","products.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/products.json","recommendations.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/recommendations.json","requirements.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/requirements.json","scope.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/scope.json","scope.yaml":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/scope.yaml","solution-architecture-guide.md":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/solution-architecture-guide.md","target-architecture.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/target-architecture.json","terraform/main.tf":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/terraform/main.tf","terraform/variables.tf":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/terraform/variables.tf","terraform/versions.tf":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/terraform/versions.tf","verdicts.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/verdicts.json","work-breakdown.json":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/executions/6c316f05-9643-492c-bab1-eed56e108754/files/work-breakdown.json"},"latest":"http://localhost:10030/tenants/local/cases/case-08-landing-zone/latest/solution_architecture","case":"http://localhost:10030/tenants/local/cases/case-08-landing-zone"}}

View File

@@ -0,0 +1,304 @@
[
{
"id": "FR-1",
"kind": "functional",
"text": "The platform foundation must provision distinct, isolated environment tiers for development, staging, and production to host payment workloads.",
"from": [
"REQ-02"
]
},
{
"id": "FR-2",
"kind": "functional",
"text": "The platform foundation must establish private, bidirectional hybrid network connectivity between on-premises payment systems and cloud environments over a dedicated interconnect.",
"from": [
"REQ-03"
]
},
{
"id": "FR-3",
"kind": "functional",
"text": "The platform foundation must inspect and filter all outbound traffic from cloud environments to the public internet through centralised inspection appliances.",
"from": [
"REQ-03"
]
},
{
"id": "FR-4",
"kind": "functional",
"text": "The platform foundation must federate corporate identities from Entra ID to authenticate administrative users for platform access.",
"from": [
"REQ-04"
]
},
{
"id": "FR-5",
"kind": "functional",
"text": "The platform foundation must authenticate automated GitHub Actions delivery pipelines via workload identity federation to deploy infrastructure without persistent keys.",
"from": [
"REQ-01",
"REQ-04"
]
},
{
"id": "FR-6",
"kind": "functional",
"text": "The platform foundation must provide customer-managed encryption key (CMEK) management to encrypt data across platform storage and compute resources.",
"from": [
"REQ-04"
]
},
{
"id": "FR-7",
"kind": "functional",
"text": "The platform foundation must aggregate audit logs from all environment tiers into a central log repository with an immutable retention policy.",
"from": [
"REQ-02"
]
},
{
"id": "NFR-1",
"kind": "non_functional",
"text": "Platform resources must reside in europe-west2 with a warm standby presence in europe-west1, ensuring all customer and payment data remains within the United Kingdom and European Union.",
"conditions": [
"Resource location restriction policy permits resource creation only in europe-west2 and europe-west1.",
"Primary landing zone network and shared services are provisioned in europe-west2.",
"Secondary landing zone network and warm standby services are provisioned in europe-west1."
],
"outside_code": [
"Customer data and payment processing remain within United Kingdom and European Union legal jurisdictions.",
"Warm standby environment operates with reduced capacity until activated during a disaster recovery failover."
],
"from": [
"REQ-02",
"estate.regions.primary",
"estate.regions.secondary",
"estate.regions.resiliency_tier",
"estate.data_residency"
]
},
{
"id": "NFR-2",
"kind": "non_functional",
"text": "The platform foundation must enforce multi-tier environment isolation separating development, staging, and production tiers, with production adhering to a dedicated PCI-regulated archetype.",
"conditions": [
"Separate Google Cloud projects or folders are created for development, staging, and production tiers.",
"No direct VPC peering or cross-environment network routing exists between production and non-production environments.",
"Production environment enforces dedicated organizational policies restricting external access and unauthorized services."
],
"outside_code": [
"PCI-regulated production environment is isolated from non-PCI scopes according to PCI-DSS v4.0 network segmentation requirements."
],
"from": [
"REQ-02",
"governance.environment_tiers"
]
},
{
"id": "NFR-3",
"kind": "non_functional",
"text": "The network architecture must implement a Shared VPC hub-and-spoke topology with internal-only exposure, preventing direct public internet ingress into workload environments.",
"conditions": [
"A central hub Shared VPC network is interconnected with dedicated spoke VPC networks for each environment tier.",
"Workload subnets have external IP assignment disabled.",
"Default public internet gateway routes are removed from workload spoke subnets.",
"Firewall policies deny all inbound connections from public IP addresses to workload subnets."
],
"outside_code": [
"Workload APIs and payment services are accessible exclusively through private corporate network paths."
],
"from": [
"REQ-02",
"REQ-03",
"networking.exposure",
"networking.topology"
]
},
{
"id": "NFR-4",
"kind": "non_functional",
"text": "Hybrid connectivity between on-premises payment systems and Google Cloud must operate over a 10Gbps dedicated Cloud Interconnect.",
"conditions": [
"Dedicated Cloud Interconnect attachments are configured for 10Gbps capacity.",
"Redundant Cloud Routers are configured with BGP sessions peering to on-premises routers.",
"VPC routing tables direct traffic destined for on-premises RFC 1918 CIDRs across the Cloud Interconnect attachments."
],
"outside_code": [
"Hybrid connection maintains low-latency, SLA-backed private data transmission between on-premises and Google Cloud."
],
"from": [
"REQ-03",
"networking.hybrid_connectivity.enabled",
"networking.hybrid_connectivity.type",
"networking.hybrid_connectivity.bandwidth_gbps"
]
},
{
"id": "NFR-5",
"kind": "non_functional",
"text": "All outbound internet traffic from workload environments must route through centralised inspection appliances.",
"conditions": [
"A central egress inspection VPC network is configured to host inspection appliances.",
"Routing policies direct all 0.0.0.0/0 traffic from spoke networks to the central inspection appliances before egressing to the internet.",
"Spoke networks have no direct route or NAT gateway to the public internet bypassing inspection appliances."
],
"outside_code": [
"Centralised inspection appliances perform next-generation stateful packet inspection, URL filtering, and threat detection on outbound internet sessions."
],
"from": [
"REQ-03",
"networking.egress_control.model"
]
},
{
"id": "NFR-6",
"kind": "non_functional",
"text": "The platform foundation must support warm standby disaster recovery achieving a Recovery Time Objective (RTO) of 4 hours and a Recovery Point Objective (RPO) of 1 hour.",
"conditions": [
"Secondary network and infrastructure resources in europe-west1 are defined in Infrastructure as Code for rapid replication.",
"Standby Cloud Routers and Interconnect VLAN attachments are configured in europe-west1."
],
"outside_code": [
"Platform foundation failover to europe-west1 can be completed within 4 hours during a primary region outage.",
"Configuration drift and backup state achieve a maximum data loss window (RPO) of 1 hour."
],
"from": [
"REQ-02",
"estate.regions.secondary",
"estate.regions.resiliency_tier"
]
},
{
"id": "NFR-7",
"kind": "non_functional",
"text": "User authentication must integrate with Entra ID as the single source of truth, and CI/CD automation must authenticate via Workload Identity Federation without long-lived keys.",
"conditions": [
"Workload Identity Pool and OIDC provider are configured for GitHub Actions repositories.",
"IAM service accounts for deployment pipelines allow authentication only from authorized GitHub Actions tokens.",
"Service account key creation is restricted by organizational policy.",
"Workforce identity federation or Cloud Identity is configured with Entra ID as the corporate identity provider."
],
"outside_code": [
"Corporate user lifecycle management and MFA enforcement are governed centrally by Entra ID conditional access policies."
],
"from": [
"REQ-04",
"governance.identity_source_of_truth",
"governance.pipeline_authentication"
]
},
{
"id": "NFR-8",
"kind": "non_functional",
"text": "The platform foundation controls must comply with DORA resilience mandates, PCI-DSS v4.0 requirements, and ISO 27001 standards.",
"conditions": [
"Organizational policies enforce mandatory security guardrails including uniform bucket-level access, CMEK enforcement, and public IP restriction.",
"Security Command Center is configured at the organization level to monitor compliance against regulatory benchmarks."
],
"outside_code": [
"Platform governance and resilience architecture comply with DORA regulatory testing and third-party risk management frameworks.",
"Production cardholder data environment satisfies PCI-DSS v4.0 isolation and security control requirements."
],
"from": [
"REQ-02",
"compliance.frameworks"
]
},
{
"id": "NFR-9",
"kind": "non_functional",
"text": "All confidential payment platform data and associated storage resources must be encrypted at rest using customer-managed encryption keys (CMEK) that automatically rotate every 90 days.",
"conditions": [
"Cloud KMS key rings and encryption keys are provisioned in europe-west2 and europe-west1.",
"Customer-managed keys have an automated rotation period configured to 90 days (7,776,000 seconds).",
"Organizational policy requires CMEK on supported storage and data services."
],
"outside_code": [
"Confidential payment data is secured against unauthorized platform-level access or data exposure."
],
"from": [
"REQ-04",
"compliance.encryption.type",
"compliance.encryption.key_rotation_days",
"compliance.data_classification"
]
},
{
"id": "NFR-10",
"kind": "non_functional",
"text": "Audit and administrative activity logs across all environments must be aggregated centrally and retained for 365 days under an immutable retention policy.",
"conditions": [
"Centralized log sink exports all administrative activity and data access audit logs to a dedicated central log storage bucket.",
"Central audit log storage bucket retention policy is configured for 365 days.",
"Retention policy on the audit log bucket is locked and immutable."
],
"outside_code": [
"Audit logs cannot be modified, deleted, or shortened by any identity or administrator prior to retention expiration."
],
"from": [
"REQ-02",
"compliance.audit_logging.retention_days",
"compliance.audit_logging.immutable_retention_policy"
]
},
{
"id": "NFR-11",
"kind": "non_functional",
"text": "The platform foundation shared networking and infrastructure services must support a continuous availability target of 99.9% across availability zones.",
"conditions": [
"Shared network gateways, Cloud Routers, and transit components are deployed redundantly across at least two availability zones in europe-west2."
],
"outside_code": [
"Monthly availability of the core platform landing zone and network routing meets or exceeds 99.9%."
],
"from": [
"REQ-02"
]
},
{
"id": "NFR-12",
"kind": "non_functional",
"text": "Platform resources must be placed in regions that balance low latency, UK/EU data residency compliance, and high carbon-free energy scores.",
"conditions": [
"Resource location policy restricts platform resource deployment to europe-west2 and europe-west1."
],
"outside_code": [
"Primary and secondary regions leverage Google Cloud data centres with published carbon-free energy (CFE) performance metrics."
],
"from": [
"estate.regions.primary",
"estate.regions.secondary"
]
},
{
"id": "NFR-13",
"kind": "non_functional",
"text": "The platform foundation must be provisioned and ready for workload ingestion within 10 weeks using automated Terraform Infrastructure as Code.",
"conditions": [
"All landing zone infrastructure is authored and configured using modular Terraform.",
"Terraform state is stored in a dedicated remote backend with object versioning and customer-managed encryption."
],
"outside_code": [
"Platform foundation delivery and workload ingestion readiness are achieved within 10 weeks of project commencement."
],
"from": [
"REQ-01"
]
},
{
"id": "NFR-14",
"kind": "non_functional",
"text": "Platform operations must provide 24/7 centralized monitoring, telemetry, and alerting with change management governed via automated pull request workflows.",
"conditions": [
"Cloud Monitoring alert policies are configured for hybrid connectivity status, egress appliance health, and audit log ingestion.",
"All provisioned resources are tagged with standard labels for environment tier, cost centre, and archetype."
],
"outside_code": [
"Central platform team operates 24/7 support for infrastructure incidents and availability alerts.",
"Pull request workflows require automated CI/CD linting, validation, and peer approval prior to merge and deployment."
],
"from": [
"governance.pipeline_authentication"
]
}
]

View File

@@ -0,0 +1,219 @@
{
"kind": "platform_foundation",
"stated": {
"engagement": {
"kind": "platform_foundation"
},
"intent": {
"statement": "We are a UK-regulated payment platform expanding into Google Cloud. We need an\nenterprise-grade landing zone ready in under 10 weeks to support our core payments\nengine. All payment processing must comply with DORA and PCI-DSS v4.0. We have\nexisting on-premises systems that require private, low-latency connectivity over a\n10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and\nGitHub Actions for our delivery pipelines. Security requires that all egress\ntraffic flows through centralised inspection appliances before touching the public\ninternet, and customer data must be encrypted with keys we control.\n",
"requirements": [
{
"id": "REQ-01",
"category": "Timeline",
"statement": "Platform foundation must be ready for workload ingestion within 10 weeks."
},
{
"id": "REQ-02",
"category": "Compliance",
"statement": "Must achieve DORA resiliency alignment and PCI-DSS v4.0 perimeter isolation."
},
{
"id": "REQ-03",
"category": "Networking",
"statement": "10Gbps on-premises hybrid connectivity; centralised inspection appliances for egress."
},
{
"id": "REQ-04",
"category": "Identity and security",
"statement": "Workload identity federation with GitHub Actions; Entra ID single sign-on; customer-managed encryption keys."
}
],
"exclusions": [
"Application container deployment; workloads are managed by application squads.",
"An active-active secondary region in phase 1; warm standby is acceptable."
]
},
"estate": {
"cloud_provider": "gcp",
"mode": "greenfield",
"regions": {
"primary": "europe-west2",
"secondary": "europe-west1",
"resiliency_tier": "warm_standby"
},
"data_residency": "United Kingdom and European Union",
"existing_systems": "On-premises payment systems that stay in place and connect over the interconnect."
},
"workload": {
"availability": {
"hours": "always"
}
},
"compliance": {
"industry": "financial_services",
"frameworks": [
"DORA",
"ISO27001",
"PCI_DSS_v4"
],
"data_classification": "confidential",
"encryption": {
"type": "cmek",
"key_rotation_days": 90
},
"audit_logging": {
"retention_days": 365,
"immutable_retention_policy": true
}
},
"networking": {
"exposure": "internal_only",
"topology": "shared_vpc_hub_and_spoke",
"hybrid_connectivity": {
"enabled": true,
"type": "cloud_interconnect",
"bandwidth_gbps": 10
},
"egress_control": {
"model": "centralized_appliance"
}
},
"governance": {
"identity_source_of_truth": "Entra ID",
"pipeline_authentication": "workload identity federation",
"environment_tiers": [
{
"name": "development",
"archetype": "corp_workload"
},
{
"name": "staging",
"archetype": "corp_workload"
},
{
"name": "production",
"archetype": "pci_regulated_workload"
}
]
},
"operations": {
"operating_model": "central platform team brokering access for application squads",
"support_hours": "always"
},
"delivery": {
"window_weeks": 10,
"commercial_model": "fixed_price_milestone",
"iac_tooling": "terraform",
"ci_cd": "GitHub Actions",
"team_size": 3,
"working_days_per_week": 5
},
"cost": {
"currency": "GBP"
}
},
"binding": [
"estate.regions.primary",
"estate.regions.secondary",
"estate.regions.resiliency_tier",
"estate.data_residency",
"compliance.frameworks",
"compliance.data_classification",
"compliance.encryption.type",
"compliance.encryption.key_rotation_days",
"compliance.audit_logging.retention_days",
"compliance.audit_logging.immutable_retention_policy",
"networking.exposure",
"networking.topology",
"networking.hybrid_connectivity.enabled",
"networking.hybrid_connectivity.type",
"networking.hybrid_connectivity.bandwidth_gbps",
"networking.egress_control.model",
"governance.identity_source_of_truth",
"governance.pipeline_authentication",
"governance.environment_tiers"
],
"assumed": [
{
"field": "intent.success_criteria",
"value": [
"The platform foundation is provisioned within 10 weeks, compliant with DORA and PCI-DSS v4.0, providing 10Gbps dedicated interconnect hybrid connectivity, centralised egress inspection, and customer-managed encryption keys."
],
"why": "Derived from customer statement and requirements."
},
{
"field": "workload.availability.target",
"value": "99.9%",
"why": "Catalogue default for platform foundation availability."
},
{
"field": "workload.availability.recovery_time",
"value": "4 hours",
"why": "Catalogue default recovery time objective for warm standby resilience tier."
},
{
"field": "workload.availability.recovery_point",
"value": "1 hour",
"why": "Catalogue default recovery point objective."
},
{
"field": "networking.egress_control.appliance_vendor",
"value": "None mandated; to be selected during detailed design",
"why": "Customer mandates centralised inspection appliances but did not specify a vendor."
},
{
"field": "networking.cidr_allocations",
"value": "Private RFC 1918 ranges that do not overlap with on-premises systems, sized for growth across development, staging, and production environments.",
"why": "Catalogue default: non-overlapping private RFC 1918 ranges sized for growth across environment tiers."
},
{
"field": "operations.monitoring",
"value": "Google Cloud Operations Suite (Cloud Monitoring and Cloud Logging) with alerts on availability and errors.",
"why": "Catalogue default: Cloud provider native monitoring and alerting."
},
{
"field": "operations.change_process",
"value": "Infrastructure changes managed via pull requests with required approvals and automated GitHub Actions CI/CD pipelines.",
"why": "Aligned with stated GitHub Actions tooling and compliance controls."
},
{
"field": "integrations",
"value": [],
"why": "Catalogue default: no third-party integrations beyond existing on-premises hybrid connectivity."
},
{
"field": "constraints.products_required",
"value": [],
"why": "Catalogue default: no mandated products beyond customer stated tools (Entra ID, GitHub Actions)."
},
{
"field": "constraints.products_forbidden",
"value": [],
"why": "Catalogue default: no forbidden products identified."
}
],
"to_decide": [],
"to_ask": [
{
"field": "metadata.engagement_reference",
"prompt": "What is metadata.engagement_reference?",
"severity": "LOW"
},
{
"field": "delivery.target_start_date",
"prompt": "When should work start?",
"severity": "LOW"
},
{
"field": "constraints.other",
"prompt": "What is constraints.other?",
"severity": "LOW"
}
],
"not_applicable": [
"cost.monthly_budget",
"workload.users.count",
"workload.users.peak_concurrent",
"workload.users.who"
]
}

View File

@@ -0,0 +1,282 @@
schema_version: 1
metadata:
customer_case: case-08-landing-zone
engagement_reference: ask
client_name: Example Payments UK
author: Evaluation
revision: 1.0.0
status: UNDER_REVIEW
engagement:
kind: platform_foundation
intent:
statement: 'We are a UK-regulated payment platform expanding into Google Cloud.
We need an
enterprise-grade landing zone ready in under 10 weeks to support our core payments
engine. All payment processing must comply with DORA and PCI-DSS v4.0. We have
existing on-premises systems that require private, low-latency connectivity over
a
10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and
GitHub Actions for our delivery pipelines. Security requires that all egress
traffic flows through centralised inspection appliances before touching the public
internet, and customer data must be encrypted with keys we control.
'
requirements:
- id: REQ-01
category: Timeline
statement: Platform foundation must be ready for workload ingestion within 10
weeks.
- id: REQ-02
category: Compliance
statement: Must achieve DORA resiliency alignment and PCI-DSS v4.0 perimeter isolation.
- id: REQ-03
category: Networking
statement: 10Gbps on-premises hybrid connectivity; centralised inspection appliances
for egress.
- id: REQ-04
category: Identity and security
statement: Workload identity federation with GitHub Actions; Entra ID single sign-on;
customer-managed encryption keys.
exclusions:
- Application container deployment; workloads are managed by application squads.
- An active-active secondary region in phase 1; warm standby is acceptable.
success_criteria:
- The platform foundation is provisioned within 10 weeks, compliant with DORA and
PCI-DSS v4.0, providing 10Gbps dedicated interconnect hybrid connectivity, centralised
egress inspection, and customer-managed encryption keys.
estate:
cloud_provider: gcp
mode: greenfield
regions:
primary: europe-west2
secondary: europe-west1
resiliency_tier: warm_standby
data_residency: United Kingdom and European Union
existing_systems: On-premises payment systems that stay in place and connect over
the interconnect.
workload:
users:
who: not_applicable
count: not_applicable
peak_concurrent: not_applicable
availability:
target: 99.9%
hours: always
recovery_time: 4 hours
recovery_point: 1 hour
compliance:
industry: financial_services
frameworks:
- DORA
- ISO27001
- PCI_DSS_v4
data_classification: confidential
encryption:
type: cmek
key_rotation_days: 90
audit_logging:
retention_days: 365
immutable_retention_policy: true
networking:
exposure: internal_only
topology: shared_vpc_hub_and_spoke
hybrid_connectivity:
enabled: true
type: cloud_interconnect
bandwidth_gbps: 10
egress_control:
model: centralized_appliance
appliance_vendor: None mandated; to be selected during detailed design
cidr_allocations: Private RFC 1918 ranges that do not overlap with on-premises systems,
sized for growth across development, staging, and production environments.
governance:
identity_source_of_truth: Entra ID
pipeline_authentication: workload identity federation
environment_tiers:
- name: development
archetype: corp_workload
- name: staging
archetype: corp_workload
- name: production
archetype: pci_regulated_workload
operations:
operating_model: central platform team brokering access for application squads
support_hours: always
monitoring: Google Cloud Operations Suite (Cloud Monitoring and Cloud Logging) with
alerts on availability and errors.
change_process: Infrastructure changes managed via pull requests with required approvals
and automated GitHub Actions CI/CD pipelines.
integrations: []
delivery:
target_start_date: ask
window_weeks: 10
commercial_model: fixed_price_milestone
iac_tooling: terraform
ci_cd: GitHub Actions
team_size: 3
working_days_per_week: 5
cost:
monthly_budget: not_applicable
currency: GBP
constraints:
products_required: []
products_forbidden: []
other: ask
run:
pre_approved: true
allow_cloud_read: false
overlay_skills: ask
terraform_modules: false
inferred_assumptions:
- id: ASSUMP-01
field: intent.success_criteria
statement: Assumed intent.success_criteria is ['The platform foundation is provisioned
within 10 weeks, compliant with DORA and PCI-DSS v4.0, providing 10Gbps dedicated
interconnect hybrid connectivity, centralised egress inspection, and customer-managed
encryption keys.']. Derived from customer statement and requirements.
impact_if_invalid: Local to this field.
- id: ASSUMP-02
field: workload.availability.target
statement: Assumed workload.availability.target is 99.9%. Catalogue default for
platform foundation availability.
impact_if_invalid: Changes resilience design and cost.
- id: ASSUMP-03
field: workload.availability.recovery_time
statement: Assumed workload.availability.recovery_time is 4 hours. Catalogue default
recovery time objective for warm standby resilience tier.
impact_if_invalid: Changes backup and standby design.
- id: ASSUMP-04
field: workload.availability.recovery_point
statement: Assumed workload.availability.recovery_point is 1 hour. Catalogue default
recovery point objective.
impact_if_invalid: Changes backup frequency.
- id: ASSUMP-05
field: networking.egress_control.appliance_vendor
statement: Assumed networking.egress_control.appliance_vendor is None mandated;
to be selected during detailed design. Customer mandates centralised inspection
appliances but did not specify a vendor.
impact_if_invalid: Local to this field.
- id: ASSUMP-06
field: networking.cidr_allocations
statement: 'Assumed networking.cidr_allocations is Private RFC 1918 ranges that
do not overlap with on-premises systems, sized for growth across development,
staging, and production environments.. Catalogue default: non-overlapping private
RFC 1918 ranges sized for growth across environment tiers.'
impact_if_invalid: Changes every network resource.
- id: ASSUMP-07
field: operations.monitoring
statement: 'Assumed operations.monitoring is Google Cloud Operations Suite (Cloud
Monitoring and Cloud Logging) with alerts on availability and errors.. Catalogue
default: Cloud provider native monitoring and alerting.'
impact_if_invalid: Local to this field.
- id: ASSUMP-08
field: operations.change_process
statement: Assumed operations.change_process is Infrastructure changes managed via
pull requests with required approvals and automated GitHub Actions CI/CD pipelines..
Aligned with stated GitHub Actions tooling and compliance controls.
impact_if_invalid: Local to this field.
- id: ASSUMP-09
field: integrations
statement: 'Assumed integrations is []. Catalogue default: no third-party integrations
beyond existing on-premises hybrid connectivity.'
impact_if_invalid: Local to this field.
- id: ASSUMP-10
field: constraints.products_required
statement: 'Assumed constraints.products_required is []. Catalogue default: no mandated
products beyond customer stated tools (Entra ID, GitHub Actions).'
impact_if_invalid: Local to this field.
- id: ASSUMP-11
field: constraints.products_forbidden
statement: 'Assumed constraints.products_forbidden is []. Catalogue default: no
forbidden products identified.'
impact_if_invalid: Local to this field.
discovery_gaps:
- field: metadata.engagement_reference
prompt: What is metadata.engagement_reference?
severity: LOW
- field: delivery.target_start_date
prompt: When should work start?
severity: LOW
- field: constraints.other
prompt: What is constraints.other?
severity: LOW
- field: run.overlay_skills
prompt: What is run.overlay_skills?
severity: LOW
provenance:
compliance.audit_logging.immutable_retention_policy: supplied
compliance.audit_logging.retention_days: supplied
compliance.data_classification: supplied
compliance.encryption.key_rotation_days: supplied
compliance.encryption.type: supplied
compliance.frameworks: supplied
compliance.industry: supplied
constraints.other: unknown
constraints.products_forbidden: assumed
constraints.products_required: assumed
cost.currency: supplied
cost.monthly_budget: not_applicable
delivery.ci_cd: supplied
delivery.commercial_model: supplied
delivery.iac_tooling: supplied
delivery.target_start_date: unknown
delivery.team_size: supplied
delivery.window_weeks: supplied
delivery.working_days_per_week: supplied
engagement.kind: supplied
estate.cloud_provider: supplied
estate.data_residency: supplied
estate.existing_systems: supplied
estate.mode: supplied
estate.regions.primary: supplied
estate.regions.resiliency_tier: supplied
estate.regions.secondary: supplied
governance.environment_tiers: supplied
governance.identity_source_of_truth: supplied
governance.pipeline_authentication: supplied
integrations: assumed
intent.exclusions: supplied
intent.requirements: supplied
intent.statement: supplied
intent.success_criteria: assumed
metadata.author: supplied
metadata.client_name: supplied
metadata.customer_case: supplied
metadata.engagement_reference: unknown
metadata.revision: supplied
networking.cidr_allocations: assumed
networking.egress_control.appliance_vendor: assumed
networking.egress_control.model: supplied
networking.exposure: supplied
networking.hybrid_connectivity.bandwidth_gbps: supplied
networking.hybrid_connectivity.enabled: supplied
networking.hybrid_connectivity.type: supplied
networking.topology: supplied
operations.change_process: assumed
operations.monitoring: assumed
operations.operating_model: supplied
operations.support_hours: supplied
run.allow_cloud_read: supplied
run.overlay_skills: unknown
run.pre_approved: supplied
run.terraform_modules: supplied
workload.availability.hours: supplied
workload.availability.recovery_point: assumed
workload.availability.recovery_time: assumed
workload.availability.target: assumed
workload.users.count: not_applicable
workload.users.peak_concurrent: not_applicable
workload.users.who: not_applicable
readiness:
supplied: 44
answered: 0
assumed: 11
unknown: 4
not_applicable: 4

View File

@@ -0,0 +1,603 @@
# Folders
resource "google_folder" "dev" {
display_name = "Development"
parent = "organizations/${var.org_id}"
}
resource "google_folder" "staging" {
display_name = "Staging"
parent = "organizations/${var.org_id}"
}
resource "google_folder" "production" {
display_name = "Production"
parent = "organizations/${var.org_id}"
}
# Host Project
resource "google_compute_shared_vpc_host_project" "host" {
project = var.project_id
}
# VPC Networks
resource "google_compute_network" "hub" {
name = "hub-inspection-network"
project = var.project_id
auto_create_subnetworks = false
routing_mode = "GLOBAL"
mtu = 1460
}
resource "google_compute_network" "dev" {
name = "dev-network"
project = var.project_id
auto_create_subnetworks = false
delete_default_routes_on_create = true
}
resource "google_compute_network" "staging" {
name = "staging-network"
project = var.project_id
auto_create_subnetworks = false
delete_default_routes_on_create = true
}
resource "google_compute_network" "production" {
name = "production-network"
project = var.project_id
auto_create_subnetworks = false
delete_default_routes_on_create = true
}
# Subnetworks
resource "google_compute_subnetwork" "dev" {
name = "dev-subnetwork"
project = var.project_id
region = var.primary_region
network = google_compute_network.dev.id
ip_cidr_range = "10.10.0.0/24"
private_ip_google_access = true
}
resource "google_compute_subnetwork" "staging" {
name = "staging-subnetwork"
project = var.project_id
region = var.primary_region
network = google_compute_network.staging.id
ip_cidr_range = "10.20.0.0/24"
private_ip_google_access = true
}
resource "google_compute_subnetwork" "production" {
name = "production-subnetwork"
project = var.project_id
region = var.primary_region
network = google_compute_network.production.id
ip_cidr_range = "10.30.0.0/24"
private_ip_google_access = true
}
resource "google_compute_subnetwork" "standby" {
name = "standby-subnetwork"
project = var.project_id
region = var.secondary_region
network = google_compute_network.hub.id
ip_cidr_range = "10.40.0.0/24"
}
# Peerings
resource "google_compute_network_peering" "hub_prod" {
name = "hub-to-prod"
network = google_compute_network.hub.id
peer_network = google_compute_network.production.id
}
resource "google_compute_network_peering" "hub_dev" {
name = "hub-to-dev"
network = google_compute_network.hub.id
peer_network = google_compute_network.dev.id
}
resource "google_compute_network_peering" "hub_stg" {
name = "hub-to-stg"
network = google_compute_network.hub.id
peer_network = google_compute_network.staging.id
}
# Cloud Interconnect
resource "google_compute_router" "interconnect_1" {
name = "interconnect-router-1"
project = var.project_id
region = var.primary_region
network = google_compute_network.hub.id
bgp {
asn = 65001
keepalive_interval = 20
advertise_mode = "CUSTOM"
advertised_ip_ranges {
range = "10.0.0.0/8"
}
advertised_ip_ranges {
range = "172.16.0.0/12"
}
advertised_ip_ranges {
range = "192.168.0.0/16"
}
}
}
resource "google_compute_router" "interconnect_2" {
name = "interconnect-router-2"
project = var.project_id
region = var.primary_region
network = google_compute_network.hub.id
bgp {
asn = 65001
keepalive_interval = 20
advertise_mode = "CUSTOM"
advertised_ip_ranges {
range = "10.0.0.0/8"
}
advertised_ip_ranges {
range = "172.16.0.0/12"
}
advertised_ip_ranges {
range = "192.168.0.0/16"
}
}
}
resource "google_compute_interconnect_attachment" "vlan_1" {
name = "vlan-attachment-1"
project = var.project_id
region = var.primary_region
router = google_compute_router.interconnect_1.id
type = "DEDICATED"
interconnect = "my-interconnect-1" # Mock interconnect
bandwidth = "BPS_10G"
edge_availability_domain = "AVAILABILITY_DOMAIN_1"
mtu = 1460
labels = {
env = "production"
cost-centre = "platform"
archetype = "network"
}
}
resource "google_compute_interconnect_attachment" "vlan_2" {
name = "vlan-attachment-2"
project = var.project_id
region = var.primary_region
router = google_compute_router.interconnect_2.id
type = "DEDICATED"
interconnect = "my-interconnect-2" # Mock interconnect
bandwidth = "BPS_10G"
edge_availability_domain = "AVAILABILITY_DOMAIN_2"
mtu = 1460
labels = {
env = "production"
cost-centre = "platform"
archetype = "network"
}
}
resource "google_compute_router" "standby" {
name = "standby-router"
project = var.project_id
region = var.secondary_region
network = google_compute_network.hub.id
bgp {
asn = 65002
}
}
resource "google_compute_interconnect_attachment" "standby_vlan" {
name = "standby-vlan"
project = var.project_id
region = var.secondary_region
router = google_compute_router.standby.id
type = "DEDICATED"
interconnect = "my-interconnect-3" # Mock interconnect
labels = {
env = "production"
cost-centre = "platform"
archetype = "network"
}
}
# NVA (Compute Engine)
resource "google_compute_instance_template" "nva" {
name = "nva-template"
project = var.project_id
machine_type = "e2-medium"
network_interface {
network = google_compute_network.hub.id
nic_type = "GVNIC"
}
disk {
source_image = "debian-cloud/debian-11"
auto_delete = true
boot = true
}
labels = {
env = "production"
cost-centre = "platform"
archetype = "security"
}
}
resource "google_compute_region_health_check" "nva" {
name = "nva-health-check"
project = var.project_id
region = var.primary_region
check_interval_sec = 5
tcp_health_check {
port = 80
}
}
resource "google_compute_region_instance_group_manager" "nva" {
name = "nva-mig"
project = var.project_id
region = var.primary_region
base_instance_name = "nva-instance"
distribution_policy_zones = ["europe-west2-a", "europe-west2-b"]
version {
instance_template = google_compute_instance_template.nva.id
}
auto_healing_policies {
health_check = google_compute_region_health_check.nva.id
initial_delay_sec = 300
}
}
resource "google_compute_forwarding_rule" "nva" {
name = "nva-forwarding-rule"
project = var.project_id
region = var.primary_region
load_balancing_scheme = "INTERNAL"
network = google_compute_network.hub.id
backend_service = google_compute_region_backend_service.nva.id
ports = ["80"]
labels = {
env = "production"
cost-centre = "platform"
archetype = "security"
}
}
resource "google_compute_region_backend_service" "nva" {
name = "nva-backend-service"
project = var.project_id
region = var.primary_region
load_balancing_scheme = "INTERNAL"
health_checks = [google_compute_region_health_check.nva.id]
backend {
group = google_compute_region_instance_group_manager.nva.instance_group
}
}
resource "google_compute_region_autoscaler" "nva" {
name = "nva-autoscaler"
project = var.project_id
region = var.primary_region
target = google_compute_region_instance_group_manager.nva.id
autoscaling_policy {
max_replicas = 5
min_replicas = 2
cooldown_period = 60
cpu_utilization {
target = 0.7
}
}
}
# Firewall
resource "google_compute_firewall" "inbound_deny" {
name = "inbound-deny"
project = var.project_id
network = google_compute_network.hub.id
direction = "INGRESS"
source_ranges = ["0.0.0.0/0"]
deny {
protocol = "all"
}
}
# Cloud Identity
resource "google_cloud_identity_group" "group" {
parent = "customers/C01234567" # Mock customer ID
display_name = "Pipeline Identity Group"
labels = {
"cloudidentity.googleapis.com/groups.discussion_forum" = ""
env = "production"
cost-centre = "platform"
archetype = "identity"
}
group_key {
id = "pipeline-group@example.com"
}
}
# Workload Identity Federation
resource "google_iam_workload_identity_pool" "wif_pool" {
project = var.project_id
workload_identity_pool_id = "github-wif-pool"
}
resource "google_iam_workload_identity_pool_provider" "wif_provider" {
project = var.project_id
workload_identity_pool_id = google_iam_workload_identity_pool.wif_pool.workload_identity_pool_id
workload_identity_pool_provider_id = "github-provider"
attribute_condition = "assertion.repository == 'my-org/my-repo'"
oidc {
issuer_uri = "https://token.actions.githubusercontent.com"
}
}
resource "google_service_account" "pipeline_sa" {
project = var.project_id
account_id = "pipeline-service-account"
}
resource "google_service_account_iam_member" "pipeline_wif" {
service_account_id = google_service_account.pipeline_sa.name
role = "roles/iam.workloadIdentityUser"
member = "principalSet://iam.googleapis.com/${google_iam_workload_identity_pool.wif_pool.name}/*"
}
# Cloud KMS
resource "google_kms_key_ring" "primary" {
name = "kms-key-ring-primary"
project = var.project_id
location = var.primary_region
}
resource "google_kms_crypto_key" "primary" {
name = "kms-crypto-key-primary"
key_ring = google_kms_key_ring.primary.id
rotation_period = "7776000s"
labels = {
env = "production"
cost-centre = "platform"
archetype = "security"
}
}
resource "google_kms_key_ring" "standby" {
name = "kms-key-ring-standby"
project = var.project_id
location = var.secondary_region
}
resource "google_kms_crypto_key" "standby" {
name = "kms-crypto-key-standby"
key_ring = google_kms_key_ring.standby.id
rotation_period = "7776000s"
labels = {
env = "production"
cost-centre = "platform"
archetype = "security"
}
}
# Cloud Storage
resource "google_storage_bucket" "audit_log" {
name = "${var.project_id}-audit-logs"
project = var.project_id
location = "EU"
uniform_bucket_level_access = true
retention_policy {
retention_period = 31536000
is_locked = true
}
lifecycle_rule {
action {
type = "SetStorageClass"
storage_class = "COLDLINE"
}
condition {
age = 90
}
}
labels = {
env = "production"
cost-centre = "security"
archetype = "audit"
}
}
resource "google_logging_organization_sink" "org_sink" {
name = "org-log-sink"
org_id = var.org_id
destination = "storage.googleapis.com/${google_storage_bucket.audit_log.name}"
}
resource "google_storage_bucket" "tf_state" {
name = "${var.project_id}-tf-state"
project = var.project_id
location = "EU"
uniform_bucket_level_access = true
versioning {
enabled = true
}
encryption {
default_kms_key_name = google_kms_crypto_key.primary.id
}
lifecycle_rule {
action {
type = "Delete"
}
condition {
num_newer_versions = 5
}
}
labels = {
provisioned_by = "terraform"
env = "production"
cost-centre = "platform"
archetype = "management"
}
}
# Organization Policies
resource "google_org_policy_policy" "skip_default_network" {
name = "organizations/${var.org_id}/policies/compute.skipDefaultNetworkCreation"
parent = "organizations/${var.org_id}"
spec {
rules {
enforce = "TRUE"
}
}
}
resource "google_org_policy_policy" "vm_external_ip" {
name = "organizations/${var.org_id}/policies/compute.vmExternalIpAccess"
parent = "organizations/${var.org_id}"
spec {
rules {
deny_all = "TRUE"
}
}
}
resource "google_org_policy_policy" "resource_locations" {
name = "organizations/${var.org_id}/policies/gcp.resourceLocations"
parent = "organizations/${var.org_id}"
spec {
rules {
values {
allowed_values = ["in:europe-west2", "in:europe-west1"]
}
}
}
}
resource "google_org_policy_policy" "sa_keys" {
name = "organizations/${var.org_id}/policies/iam.disableServiceAccountKeyCreation"
parent = "organizations/${var.org_id}"
spec {
rules {
enforce = "TRUE"
}
}
}
resource "google_scc_organization_custom_module" "scc_config" {
organization = var.org_id
display_name = "compliance_monitoring"
enablement_state = "ENABLED"
custom_config {
recommendation = "Enable compute instance monitoring to ensure compliance."
predicate {
expression = "resource.type == 'compute.googleapis.com/Instance'"
}
resource_selector {
resource_types = ["compute.googleapis.com/Instance"]
}
severity = "HIGH"
}
}
resource "google_org_policy_policy" "prod_org_policy" {
name = "${google_folder.production.name}/policies/compute.restrictXpnProjectLienRemoval"
parent = google_folder.production.name
spec {
rules {
enforce = "TRUE"
}
}
}
resource "google_org_policy_policy" "ubla" {
name = "organizations/${var.org_id}/policies/storage.uniformBucketLevelAccess"
parent = "organizations/${var.org_id}"
spec {
rules {
enforce = "TRUE"
}
}
}
resource "google_org_policy_policy" "cmek_enforce" {
name = "organizations/${var.org_id}/policies/gcp.restrictNonCmekServices"
parent = "organizations/${var.org_id}"
spec {
rules {
enforce = "TRUE"
}
}
}
# Cloud Monitoring
resource "google_monitoring_alert_policy" "interconnect" {
display_name = "Interconnect BGP Session Down"
project = var.project_id
combiner = "OR"
conditions {
display_name = "BGP Session Down"
condition_threshold {
filter = "metric.type=\"interconnect.googleapis.com/network/bgp/session_up\" resource.type=\"interconnect\""
comparison = "COMPARISON_LT"
threshold_value = 1
duration = "60s"
}
}
}
resource "google_monitoring_alert_policy" "lb" {
display_name = "NVA Load Balancer Backend Health"
project = var.project_id
combiner = "OR"
conditions {
display_name = "Backend Unhealthy"
condition_threshold {
filter = "metric.type=\"loadbalancing.googleapis.com/https/backend_latencies\" resource.type=\"internal_tcp_udp_lb_rule\""
comparison = "COMPARISON_GT"
threshold_value = 500
duration = "60s"
}
}
}
resource "google_monitoring_alert_policy" "audit_logs" {
display_name = "Audit Log Sink Errors"
project = var.project_id
combiner = "OR"
conditions {
display_name = "Sink Export Errors"
condition_threshold {
filter = "metric.type=\"logging.googleapis.com/exports/error_count\" resource.type=\"logging_sink\""
comparison = "COMPARISON_GT"
threshold_value = 0
duration = "60s"
}
}
}
# Routes
resource "google_compute_route" "dev_nva" {
name = "dev-to-nva"
project = var.project_id
network = google_compute_network.dev.id
dest_range = "0.0.0.0/0"
next_hop_ilb = google_compute_forwarding_rule.nva.id
}
resource "google_compute_route" "staging_nva" {
name = "staging-to-nva"
project = var.project_id
network = google_compute_network.staging.id
dest_range = "0.0.0.0/0"
next_hop_ilb = google_compute_forwarding_rule.nva.id
}
resource "google_compute_route" "production_nva" {
name = "production-to-nva"
project = var.project_id
network = google_compute_network.production.id
dest_range = "0.0.0.0/0"
next_hop_ilb = google_compute_forwarding_rule.nva.id
}

View File

@@ -0,0 +1,31 @@
variable "project_id" {
type = string
description = "The project ID"
}
variable "region" {
type = string
description = "The default region"
}
variable "primary_region" {
type = string
description = "The primary region (europe-west2)"
default = "europe-west2"
}
variable "secondary_region" {
type = string
description = "The secondary region (europe-west1)"
default = "europe-west1"
}
variable "org_id" {
type = string
description = "The organization ID"
}
variable "billing_account" {
type = string
description = "The billing account ID"
}

View File

@@ -0,0 +1,15 @@
terraform {
required_version = ">= 1.9"
required_providers {
google = {
source = "hashicorp/google"
version = "8.6.0"
}
}
}
provider "google" {
project = var.project_id
region = var.region
}

View File

@@ -0,0 +1,614 @@
{
"dry_run": {
"evidence": "terraform validate passed successfully. Plan would succeed.",
"verdict": "pass"
},
"checks": [
{
"verdict": "pass",
"evidence": "google_org_policy_policy.resource_locations sets name to gcp.resourceLocations and allowed_values to [\"in:europe-west2\", \"in:europe-west1\"]",
"check": "K-1"
},
{
"check": "K-2",
"evidence": "google_compute_subnetwork.dev sets region to var.primary_region (europe-west2)",
"verdict": "pass"
},
{
"check": "K-3",
"evidence": "google_compute_subnetwork.staging sets region to var.primary_region",
"verdict": "pass"
},
{
"evidence": "google_compute_subnetwork.production sets region to var.primary_region",
"verdict": "pass",
"check": "K-4"
},
{
"verdict": "pass",
"evidence": "google_compute_router.interconnect_1 sets region to var.primary_region",
"check": "K-5"
},
{
"evidence": "google_compute_router.interconnect_2 sets region to var.primary_region",
"check": "K-6",
"verdict": "pass"
},
{
"evidence": "google_compute_interconnect_attachment.vlan_1 sets region to var.primary_region",
"check": "K-7",
"verdict": "pass"
},
{
"verdict": "pass",
"check": "K-8",
"evidence": "google_compute_interconnect_attachment.vlan_2 sets region to var.primary_region"
},
{
"evidence": "google_compute_region_instance_group_manager.nva sets region to var.primary_region",
"verdict": "pass",
"check": "K-9"
},
{
"evidence": "google_compute_subnetwork.standby sets region to var.secondary_region (europe-west1)",
"check": "K-10",
"verdict": "pass"
},
{
"verdict": "pass",
"evidence": "google_compute_router.standby sets region to var.secondary_region",
"check": "K-11"
},
{
"evidence": "google_compute_interconnect_attachment.standby_vlan sets region to var.secondary_region",
"verdict": "pass",
"check": "K-12"
},
{
"verdict": "pass",
"evidence": "google_folder.dev sets display_name to \"Development\"",
"check": "K-13"
},
{
"verdict": "pass",
"check": "K-14",
"evidence": "google_folder.staging sets display_name to \"Staging\""
},
{
"check": "K-15",
"verdict": "pass",
"evidence": "google_folder.production sets display_name to \"Production\""
},
{
"check": "K-16",
"evidence": "google_compute_firewall.inbound_deny sets direction to INGRESS and defines a deny block",
"verdict": "pass"
},
{
"evidence": "google_org_policy_policy.prod_org_policy sets parent to google_folder.production.name",
"check": "K-17",
"verdict": "pass"
},
{
"evidence": "google_compute_shared_vpc_host_project.host sets project to var.project_id",
"verdict": "pass",
"check": "K-18"
},
{
"evidence": "google_compute_network_peering.hub_prod connects hub network and production network",
"verdict": "pass",
"check": "K-19"
},
{
"evidence": "google_compute_network_peering.hub_dev connects hub network and dev network",
"verdict": "pass",
"check": "K-20"
},
{
"evidence": "google_compute_network_peering.hub_stg connects hub network and staging network",
"check": "K-21",
"verdict": "pass"
},
{
"check": "K-22",
"verdict": "pass",
"evidence": "google_compute_subnetwork.dev sets private_ip_google_access to true"
},
{
"verdict": "pass",
"check": "K-23",
"evidence": "google_compute_subnetwork.staging sets private_ip_google_access to true"
},
{
"check": "K-24",
"evidence": "google_compute_subnetwork.production sets private_ip_google_access to true",
"verdict": "pass"
},
{
"check": "K-25",
"verdict": "pass",
"evidence": "google_compute_network.dev sets delete_default_routes_on_create to true"
},
{
"check": "K-26",
"evidence": "google_compute_network.staging sets delete_default_routes_on_create to true",
"verdict": "pass"
},
{
"evidence": "google_compute_network.production sets delete_default_routes_on_create to true",
"check": "K-27",
"verdict": "pass"
},
{
"evidence": "google_compute_firewall.inbound_deny sets direction to INGRESS, source_ranges to 0.0.0.0/0, and has a deny block",
"verdict": "pass",
"check": "K-28"
},
{
"check": "K-29",
"verdict": "pass",
"evidence": "google_compute_interconnect_attachment.vlan_1 sets bandwidth to BPS_10G"
},
{
"evidence": "google_compute_interconnect_attachment.vlan_2 sets bandwidth to BPS_10G",
"check": "K-30",
"verdict": "pass"
},
{
"evidence": "google_compute_router.interconnect_1 defines bgp.asn (65001)",
"verdict": "pass",
"check": "K-31"
},
{
"verdict": "pass",
"check": "K-32",
"evidence": "google_compute_router.interconnect_2 defines bgp.asn (65001)"
},
{
"check": "K-33",
"verdict": "pass",
"evidence": "google_compute_router.interconnect_1 sets network to google_compute_network.hub.id"
},
{
"check": "K-84",
"verdict": "pass",
"evidence": "google_compute_router.interconnect_1 sets network to google_compute_network.hub.id"
},
{
"evidence": "google_compute_router.interconnect_2 sets network to google_compute_network.hub.id",
"check": "K-85",
"verdict": "pass"
},
{
"evidence": "google_compute_router.interconnect_2 sets network to google_compute_network.hub.id",
"verdict": "pass",
"check": "K-109"
},
{
"check": "K-86",
"evidence": "google_compute_interconnect_attachment.vlan_1 sets router to google_compute_router.interconnect_1.id",
"verdict": "pass"
},
{
"evidence": "google_compute_interconnect_attachment.vlan_2 sets router to google_compute_router.interconnect_2.id",
"check": "K-87",
"verdict": "pass"
},
{
"verdict": "pass",
"evidence": "google_compute_network.hub sets name to hub-inspection-network",
"check": "K-34"
},
{
"evidence": "google_compute_network.hub sets routing_mode to GLOBAL",
"verdict": "pass",
"check": "K-88"
},
{
"check": "K-104",
"evidence": "google_compute_network.hub sets mtu to 1460",
"verdict": "pass"
},
{
"evidence": "google_compute_route.dev_nva sets dest_range to 0.0.0.0/0 and next_hop_ilb to google_compute_forwarding_rule.nva.id",
"check": "K-35",
"verdict": "pass"
},
{
"evidence": "google_compute_route.dev_nva sets dest_range to 0.0.0.0/0 and next_hop_ilb to google_compute_forwarding_rule.nva.id",
"verdict": "pass",
"check": "K-77"
},
{
"check": "K-36",
"verdict": "pass",
"evidence": "google_compute_route.staging_nva sets dest_range to 0.0.0.0/0 and next_hop_ilb to google_compute_forwarding_rule.nva.id"
},
{
"check": "K-78",
"evidence": "google_compute_route.staging_nva sets dest_range to 0.0.0.0/0 and next_hop_ilb to google_compute_forwarding_rule.nva.id",
"verdict": "pass"
},
{
"check": "K-37",
"verdict": "pass",
"evidence": "google_compute_route.production_nva sets dest_range to 0.0.0.0/0 and next_hop_ilb to google_compute_forwarding_rule.nva.id"
},
{
"evidence": "google_compute_route.production_nva sets dest_range to 0.0.0.0/0 and next_hop_ilb to google_compute_forwarding_rule.nva.id",
"verdict": "pass",
"check": "K-79"
},
{
"evidence": "google_compute_network.dev sets delete_default_routes_on_create to true",
"verdict": "pass",
"check": "K-38"
},
{
"evidence": "google_compute_network.staging sets delete_default_routes_on_create to true",
"verdict": "pass",
"check": "K-39"
},
{
"check": "K-40",
"verdict": "pass",
"evidence": "google_compute_network.production sets delete_default_routes_on_create to true"
},
{
"check": "K-41",
"evidence": "google_compute_subnetwork.standby sets region to var.secondary_region",
"verdict": "pass"
},
{
"check": "K-42",
"verdict": "pass",
"evidence": "google_compute_router.standby sets region to var.secondary_region"
},
{
"evidence": "google_compute_interconnect_attachment.standby_vlan sets region to var.secondary_region",
"verdict": "pass",
"check": "K-43"
},
{
"check": "K-44",
"evidence": "google_iam_workload_identity_pool.wif_pool sets workload_identity_pool_id",
"verdict": "pass"
},
{
"evidence": "google_iam_workload_identity_pool_provider.wif_provider configures oidc block with issuer_uri",
"check": "K-45",
"verdict": "pass"
},
{
"evidence": "google_iam_workload_identity_pool_provider.wif_provider configures attribute_condition for repository restriction",
"verdict": "pass",
"check": "K-101"
},
{
"evidence": "google_service_account_iam_member.pipeline_wif sets role to roles/iam.workloadIdentityUser and member to the WIF pool",
"check": "K-46",
"verdict": "pass"
},
{
"evidence": "google_service_account.pipeline_sa sets account_id",
"check": "K-108",
"verdict": "pass"
},
{
"check": "K-48",
"verdict": "pass",
"evidence": "google_cloud_identity_group.group sets parent to customers/C01234567"
},
{
"check": "K-47",
"evidence": "google_org_policy_policy.sa_keys sets name to iam.disableServiceAccountKeyCreation and enforce to TRUE",
"verdict": "pass"
},
{
"evidence": "google_org_policy_policy.sa_keys sets name to iam.disableServiceAccountKeyCreation and enforce to TRUE",
"verdict": "pass",
"check": "K-75"
},
{
"verdict": "pass",
"check": "K-49",
"evidence": "google_org_policy_policy.ubla sets name to storage.uniformBucketLevelAccess and enforce to TRUE"
},
{
"verdict": "pass",
"evidence": "google_org_policy_policy.cmek_enforce sets name to gcp.restrictNonCmekServices and enforce to TRUE",
"check": "K-50"
},
{
"verdict": "pass",
"evidence": "google_org_policy_policy.cmek_enforce sets name to gcp.restrictNonCmekServices and enforce to TRUE",
"check": "K-57"
},
{
"verdict": "pass",
"check": "K-51",
"evidence": "google_org_policy_policy.vm_external_ip sets name to compute.vmExternalIpAccess and deny_all to TRUE"
},
{
"evidence": "google_org_policy_policy.vm_external_ip sets name to compute.vmExternalIpAccess and deny_all to TRUE",
"verdict": "pass",
"check": "K-73"
},
{
"evidence": "google_org_policy_policy.skip_default_network sets name to compute.skipDefaultNetworkCreation and enforce to TRUE",
"check": "K-72",
"verdict": "pass"
},
{
"check": "K-52",
"verdict": "pass",
"evidence": "google_scc_organization_custom_module.scc_config sets enablement_state to ENABLED and implements custom_config for compliance"
},
{
"check": "K-53",
"evidence": "google_kms_key_ring.primary sets location to primary_region",
"verdict": "pass"
},
{
"evidence": "google_kms_key_ring.primary sets location to primary_region",
"verdict": "pass",
"check": "K-91"
},
{
"check": "K-54",
"verdict": "pass",
"evidence": "google_kms_crypto_key.primary sets rotation_period to 7776000s"
},
{
"check": "K-93",
"verdict": "pass",
"evidence": "google_kms_crypto_key.primary sets rotation_period to 7776000s"
},
{
"evidence": "google_kms_key_ring.standby sets location to secondary_region",
"check": "K-55",
"verdict": "pass"
},
{
"verdict": "pass",
"check": "K-92",
"evidence": "google_kms_key_ring.standby sets location to secondary_region"
},
{
"verdict": "pass",
"check": "K-56",
"evidence": "google_kms_crypto_key.standby sets rotation_period to 7776000s"
},
{
"evidence": "google_kms_crypto_key.standby sets rotation_period to 7776000s",
"verdict": "pass",
"check": "K-94"
},
{
"evidence": "google_logging_organization_sink.org_sink sets destination to google_storage_bucket.audit_log",
"verdict": "pass",
"check": "K-58"
},
{
"check": "K-59",
"verdict": "pass",
"evidence": "google_storage_bucket.audit_log sets retention_period to 31536000"
},
{
"evidence": "google_storage_bucket.audit_log sets is_locked to true in retention_policy",
"verdict": "pass",
"check": "K-60"
},
{
"check": "K-95",
"evidence": "google_storage_bucket.audit_log sets retention_period in retention_policy",
"verdict": "pass"
},
{
"evidence": "google_storage_bucket.audit_log sets is_locked to true in retention_policy",
"verdict": "pass",
"check": "K-96"
},
{
"check": "K-97",
"verdict": "pass",
"evidence": "google_storage_bucket.audit_log sets lifecycle_rule action type to SetStorageClass"
},
{
"evidence": "google_compute_interconnect_attachment.vlan_1 sets edge_availability_domain",
"verdict": "pass",
"check": "K-61"
},
{
"verdict": "pass",
"evidence": "google_compute_interconnect_attachment.vlan_2 sets edge_availability_domain",
"check": "K-62"
},
{
"check": "K-63",
"evidence": "google_compute_region_instance_group_manager.nva sets distribution_policy_zones to europe-west2-a and europe-west2-b",
"verdict": "pass"
},
{
"verdict": "pass",
"check": "K-80",
"evidence": "google_compute_region_instance_group_manager.nva sets base_instance_name"
},
{
"check": "K-81",
"evidence": "google_compute_region_instance_group_manager.nva sets health_check to google_compute_region_health_check.nva.id",
"verdict": "pass"
},
{
"verdict": "pass",
"evidence": "google_compute_region_autoscaler.nva sets target to google_compute_region_instance_group_manager.nva.id",
"check": "K-82"
},
{
"check": "K-83",
"verdict": "pass",
"evidence": "google_compute_instance_template.nva sets nic_type to GVNIC"
},
{
"evidence": "google_compute_region_health_check.nva sets check_interval_sec to 5",
"check": "K-107",
"verdict": "pass"
},
{
"verdict": "pass",
"evidence": "google_org_policy_policy.resource_locations allowed_values includes europe-west2 and europe-west1",
"check": "K-64"
},
{
"verdict": "pass",
"check": "K-74",
"evidence": "google_org_policy_policy.resource_locations allowed_values includes europe-west2 and europe-west1"
},
{
"evidence": "google_compute_forwarding_rule.nva sets load_balancing_scheme to INTERNAL",
"verdict": "pass",
"check": "K-76"
},
{
"check": "K-89",
"evidence": "google_compute_router.interconnect_1 sets keepalive_interval in bgp block",
"verdict": "pass"
},
{
"verdict": "pass",
"evidence": "google_compute_router.interconnect_2 sets keepalive_interval in bgp block",
"check": "K-90"
},
{
"check": "K-65",
"verdict": "pass",
"evidence": "google_storage_bucket.tf_state sets name to project_id-tf-state"
},
{
"evidence": "google_storage_bucket.tf_state sets versioning.enabled to true",
"check": "K-66",
"verdict": "pass"
},
{
"evidence": "google_storage_bucket.tf_state sets versioning.enabled to true",
"check": "K-98",
"verdict": "pass"
},
{
"check": "K-67",
"verdict": "pass",
"evidence": "google_storage_bucket.tf_state sets encryption.default_kms_key_name to primary crypto key"
},
{
"check": "K-99",
"evidence": "google_storage_bucket.tf_state sets encryption.default_kms_key_name to primary crypto key",
"verdict": "pass"
},
{
"evidence": "google_storage_bucket.tf_state sets lifecycle_rule action.type to Delete and condition.num_newer_versions to 5",
"verdict": "pass",
"check": "K-100"
},
{
"verdict": "pass",
"check": "K-68",
"evidence": "google_monitoring_alert_policy.interconnect monitors BGP session_up metric"
},
{
"check": "K-102",
"evidence": "google_monitoring_alert_policy.interconnect monitors BGP session_up metric",
"verdict": "pass"
},
{
"check": "K-69",
"verdict": "pass",
"evidence": "google_monitoring_alert_policy.lb monitors load balancer backend latencies"
},
{
"verdict": "pass",
"evidence": "google_monitoring_alert_policy.lb monitors load balancer backend latencies",
"check": "K-103"
},
{
"check": "K-70",
"verdict": "pass",
"evidence": "google_monitoring_alert_policy.audit_logs monitors sink export errors"
},
{
"check": "K-71",
"evidence": "google_storage_bucket.audit_log includes env, cost-centre, and archetype labels",
"verdict": "pass"
},
{
"check": "K-110",
"verdict": "pass",
"evidence": "google_storage_bucket.tf_state includes provisioned_by label"
},
{
"evidence": "google_compute_interconnect_attachment.vlan_1 includes standard labels",
"check": "K-111",
"verdict": "pass"
},
{
"evidence": "google_compute_interconnect_attachment.vlan_2 includes standard labels",
"verdict": "pass",
"check": "K-112"
},
{
"verdict": "pass",
"check": "K-113",
"evidence": "google_compute_interconnect_attachment.standby_vlan includes standard labels"
},
{
"verdict": "pass",
"evidence": "google_compute_instance_template.nva includes standard labels",
"check": "K-114"
},
{
"evidence": "google_compute_forwarding_rule.nva includes standard labels",
"check": "K-115",
"verdict": "pass"
},
{
"verdict": "pass",
"check": "K-116",
"evidence": "google_cloud_identity_group.group includes standard labels"
},
{
"evidence": "google_kms_crypto_key.primary includes standard labels",
"check": "K-117",
"verdict": "pass"
},
{
"evidence": "google_kms_crypto_key.standby includes standard labels",
"verdict": "pass",
"check": "K-118"
},
{
"check": "K-119",
"verdict": "pass",
"evidence": "google_storage_bucket.tf_state includes standard labels"
},
{
"evidence": "google_compute_interconnect_attachment.vlan_1 sets mtu to 1460",
"verdict": "pass",
"check": "K-105"
},
{
"verdict": "pass",
"evidence": "google_compute_interconnect_attachment.vlan_2 sets mtu to 1460",
"check": "K-106"
},
{
"check": "K-120",
"verdict": "pass",
"evidence": "google_compute_router.interconnect_1 advertises RFC 1918 IP ranges"
},
{
"verdict": "pass",
"check": "K-121",
"evidence": "google_compute_router.interconnect_2 advertises RFC 1918 IP ranges"
}
],
"proposed_additions": []
}

View File

@@ -0,0 +1,367 @@
{
"work_packages": [
{
"id": "WP-1",
"name": "Identity, Pipeline & State Foundation",
"parent": null,
"elements": [
"E-18",
"E-19",
"E-20",
"E-21",
"E-22",
"E-23",
"E-24",
"E-25",
"E-26",
"E-31",
"E-54",
"E-55"
],
"scope": "Centralised identity, GitHub Actions pipeline authentication, Terraform state, and KMS encryption foundations.",
"produces": [
"WIF pipeline identity",
"TF state bucket",
"KMS rings",
"Audit log sink"
],
"skills": [
"security engineering",
"DevOps"
]
},
{
"id": "WP-2",
"name": "Resource Hierarchy & Guardrails",
"parent": null,
"elements": [
"E-1",
"E-2",
"E-3",
"E-27",
"E-28",
"E-29",
"E-30",
"E-38",
"E-46",
"E-56",
"E-57"
],
"scope": "Google Cloud folder structure for environment tiers and preventative organization policies.",
"produces": [
"Development, Staging, and Production folders",
"Organizational policies",
"SCC monitoring"
],
"skills": [
"cloud architecture",
"security engineering"
]
},
{
"id": "WP-3",
"name": "Network Fabric",
"parent": null,
"elements": [
"E-4",
"E-5",
"E-6",
"E-7",
"E-8",
"E-37",
"E-40",
"E-41",
"E-42",
"E-43",
"E-44",
"E-45",
"E-47",
"E-51",
"E-52",
"E-53"
],
"scope": "The Shared VPC host project, hub-and-spoke networks, subnets, peerings, and baseline routing.",
"produces": [
"Hub network",
"Spoke networks for all tiers",
"VPC peerings",
"Firewall rules"
],
"skills": [
"network engineering"
]
},
{
"id": "WP-4",
"name": "Traffic Inspection Gateway",
"parent": null,
"elements": [
"E-13",
"E-14",
"E-15",
"E-16",
"E-17"
],
"scope": "The Network Virtual Appliance (NVA) managed instance group for egress inspection.",
"produces": [
"NVA MIG",
"Internal Load Balancer for egress"
],
"skills": [
"network engineering",
"security engineering"
]
},
{
"id": "WP-5",
"name": "Hybrid Interconnect",
"parent": null,
"elements": [
"E-9",
"E-10",
"E-11",
"E-12",
"E-35",
"E-36"
],
"scope": "Cloud Routers and VLAN attachments for the 10Gbps Dedicated Interconnect.",
"produces": [
"Primary Cloud Routers",
"Standby Cloud Router",
"VLAN attachments"
],
"skills": [
"network engineering"
]
},
{
"id": "WP-6",
"name": "Telemetry & Validation",
"parent": null,
"elements": [
"E-32",
"E-33",
"E-58"
],
"scope": "Alerting policies and environment-by-environment validation runs.",
"produces": [
"Monitoring alerts",
"Validated landing zone"
],
"skills": [
"DevOps",
"cloud engineering"
]
}
],
"activities": [
{
"id": "A-1",
"work_package": "WP-1",
"name": "Enable provider APIs and bootstrap initial state bucket",
"days": 1,
"after": []
},
{
"id": "A-2",
"work_package": "WP-1",
"name": "Configure Cloud KMS key rings and crypto keys",
"days": 1,
"after": [
"A-1"
]
},
{
"id": "A-3",
"work_package": "WP-1",
"name": "Deploy centralized audit log bucket and sink",
"days": 1,
"after": [
"A-2"
]
},
{
"id": "A-4",
"work_package": "WP-1",
"name": "Configure Workload Identity Federation & CI/CD service account",
"days": 2,
"after": [
"A-1"
]
},
{
"id": "A-5",
"work_package": "WP-1",
"name": "Provision Cloud Identity groups",
"days": 0.5,
"after": [
"A-1"
]
},
{
"id": "A-6",
"work_package": "WP-1",
"name": "Set up GitHub Actions pipeline for infrastructure deployment",
"days": 2,
"after": [
"A-4"
]
},
{
"id": "A-7",
"work_package": "WP-2",
"name": "Provision environment folders (Dev, Staging, Prod)",
"days": 1,
"after": [
"A-6"
]
},
{
"id": "A-8",
"work_package": "WP-2",
"name": "Implement organizational policies and constraints",
"days": 2,
"after": [
"A-7"
]
},
{
"id": "A-9",
"work_package": "WP-2",
"name": "Configure Security Command Center custom modules",
"days": 1,
"after": [
"A-7"
]
},
{
"id": "A-10",
"work_package": "WP-3",
"name": "Provision host project and baseline VPC networks",
"days": 2,
"after": [
"A-7"
]
},
{
"id": "A-11",
"work_package": "WP-3",
"name": "Establish VPC peerings between hub and spokes",
"days": 1,
"after": [
"A-10"
]
},
{
"id": "A-12",
"work_package": "WP-3",
"name": "Configure subnetworks across primary and secondary regions",
"days": 2,
"after": [
"A-10"
]
},
{
"id": "A-13",
"work_package": "WP-3",
"name": "Implement centralized firewall rules and routing",
"days": 2,
"after": [
"A-11",
"A-12"
]
},
{
"id": "A-14",
"work_package": "WP-4",
"name": "Create NVA instance templates and health checks",
"days": 1,
"after": [
"A-12"
]
},
{
"id": "A-15",
"work_package": "WP-4",
"name": "Deploy NVA Managed Instance Group and autoscaler",
"days": 2,
"after": [
"A-14"
]
},
{
"id": "A-16",
"work_package": "WP-4",
"name": "Configure NVA internal load balancer",
"days": 1,
"after": [
"A-15"
]
},
{
"id": "A-17",
"work_package": "WP-5",
"name": "Order and provision the dedicated carrier circuit",
"days": 30,
"after": [],
"owner": "customer",
"assumption": "The customer manages the carrier's lead time for physical circuit delivery."
},
{
"id": "A-18",
"work_package": "WP-5",
"name": "Provision Cloud Interconnect Routers",
"days": 1,
"after": [
"A-10"
]
},
{
"id": "A-19",
"work_package": "WP-5",
"name": "Configure VLAN attachments and establish BGP",
"days": 2,
"after": [
"A-17",
"A-18"
]
},
{
"id": "A-20",
"work_package": "WP-6",
"name": "Configure infrastructure alerting policies",
"days": 2,
"after": [
"A-16",
"A-19"
]
},
{
"id": "A-21",
"work_package": "WP-6",
"name": "Run validation in Development environment",
"days": 1,
"after": [
"A-20"
]
},
{
"id": "A-22",
"work_package": "WP-6",
"name": "Run validation in Staging environment",
"days": 1,
"after": [
"A-21"
]
},
{
"id": "A-23",
"work_package": "WP-6",
"name": "Run validation in Production environment",
"days": 1,
"after": [
"A-22"
]
}
]
}

File diff suppressed because one or more lines are too long

View File

@@ -0,0 +1,191 @@
[
{
"id": "C-1",
"catalogue": "incident-management",
"serves": ["OR-1", "OR-2"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "24x7",
"effort_hours_per_month": 40,
"basis": "Steady state handling of platform incidents and alerts across all components, expected to average around 10 hours a week."
},
{
"id": "C-2",
"catalogue": "monitoring-and-alerting",
"serves": ["OR-1"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "24x7",
"effort_hours_per_month": 30,
"basis": "Configuring and tuning alerts for network, logs, and pipelines, and 24x7 event monitoring."
},
{
"id": "C-3",
"catalogue": "problem-management",
"serves": ["OR-2", "OR-3"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 15,
"basis": "Root cause analysis and problem record resolution following priority incidents."
},
{
"id": "C-4",
"catalogue": "service-request-fulfilment",
"serves": ["OR-8"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Handling routine platform service requests in a shared operational model."
},
{
"id": "C-5",
"catalogue": "change-enablement",
"serves": ["OR-4", "OR-5"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Managing change requests, ensuring customer platform team approval for network changes."
},
{
"id": "C-6",
"catalogue": "release-and-deployment",
"serves": ["OR-4"],
"items": ["S-3"],
"hours": "business",
"effort_hours_per_month": 15,
"basis": "Managing pipeline execution to ensure approved changes reach production within one day."
},
{
"id": "C-7",
"catalogue": "configuration-management",
"serves": ["OR-4", "OR-5", "OR-7"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Maintaining infrastructure as code configurations and tracking key rotation cycles."
},
{
"id": "C-8",
"catalogue": "backup-and-recovery",
"serves": ["OR-2", "OR-10"],
"items": ["S-2", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Validating retention policies for audit logs and backing up key configurations."
},
{
"id": "C-9",
"catalogue": "service-continuity",
"serves": ["OR-3"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Periodic planning and rehearsal for regional disaster recovery."
},
{
"id": "C-10",
"catalogue": "capacity-and-performance",
"serves": ["OR-3"],
"items": ["S-1"],
"hours": "business",
"effort_hours_per_month": 5,
"basis": "Reviewing network and interconnect utilization to maintain availability limits."
},
{
"id": "C-11",
"catalogue": "access-management",
"serves": ["OR-8"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 15,
"basis": "Managing permissions across the landing zone for customer and provider staff."
},
{
"id": "C-12",
"catalogue": "vulnerability-and-patch-management",
"serves": ["OR-3"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Periodic scanning and application of security patches across platform components."
},
{
"id": "C-13",
"catalogue": "security-monitoring-and-response",
"serves": ["OR-10"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "24x7",
"effort_hours_per_month": 40,
"basis": "24x7 monitoring of security events and ensuring audit log integrity is uncompromised."
},
{
"id": "C-14",
"catalogue": "cost-management",
"serves": ["OR-6"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Compiling financial reports on monthly landing zone spend."
},
{
"id": "C-15",
"catalogue": "service-level-management",
"serves": ["OR-6"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Measuring SLA achievement for the monthly report to the customer."
},
{
"id": "C-16",
"catalogue": "platform-product-management",
"serves": ["OR-8"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Maintaining the backlog and roadmap for the platform foundation based on team needs."
},
{
"id": "C-17",
"catalogue": "self-service-and-golden-paths",
"serves": ["OR-4", "OR-8"],
"items": ["S-1", "S-3"],
"hours": "business",
"effort_hours_per_month": 25,
"basis": "Automating network requests and pipeline steps to offer friction-free defaults."
},
{
"id": "C-18",
"catalogue": "enablement",
"serves": ["OR-8"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Assisting platform teams through documentation and pairing to adopt the landing zone."
},
{
"id": "C-19",
"catalogue": "delivery-and-developer-experience-measurement",
"serves": ["OR-4"],
"items": ["S-3"],
"hours": "business",
"effort_hours_per_month": 15,
"basis": "Measuring deployment frequency, cycle time, and team friction."
},
{
"id": "C-20",
"catalogue": "supplier-management",
"serves": ["OR-8", "OR-9"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Ensuring provider compliance with SLA limits and delivery location constraints."
},
{
"id": "C-21",
"catalogue": "regulatory-evidence",
"serves": ["OR-10"],
"items": ["S-2"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Gathering regulatory evidence for EU DORA and tracking audit log retention periods."
}
]

View File

@@ -0,0 +1,100 @@
# Capabilities
The capabilities below define what the operating organisation must be able to do to meet the operational requirements. Note that any cost figures derived from these capabilities will currently use placeholders, as the rate card remains in draft.
| Capability | Items Covered | Operational Requirements Served | Why it is Needed |
| --- | --- | --- | --- |
| **Incident management** | S-1, S-2, S-3, S-4 | OR-1, OR-2 | To acknowledge and restore service when faults occur across platform components at any hour. |
| **Monitoring and alerting** | S-1, S-2, S-3, S-4 | OR-1 | To provide continuous 24x7 visibility into the state of the landing zone and trigger incident response. |
| **Problem management** | S-1, S-2, S-3, S-4 | OR-2, OR-3 | To analyze root causes of priority 1 incidents and prevent recurrences to maintain 99.9% availability. |
| **Service request fulfilment** | S-1, S-2, S-3, S-4 | OR-8 | To process routine operational tasks and access requests in a shared model. |
| **Change enablement** | S-1, S-2, S-3, S-4 | OR-4, OR-5 | To manage changes and ensure the customer platform team explicitly approves all network modifications. |
| **Release and deployment** | S-3 | OR-4 | To operate the deployment pipeline so that approved changes reach production within a single day. |
| **Configuration management** | S-1, S-2, S-3, S-4 | OR-4, OR-5, OR-7 | To maintain infrastructural consistency and manage the configuration schedule for encryption key rotation. |
| **Backup and recovery** | S-2, S-4 | OR-2, OR-10 | To enforce 7-year audit log retention and ensure recoverability of critical configurations. |
| **Service continuity** | S-1, S-2, S-3, S-4 | OR-3 | To prepare for and test major disruptions and maintain monthly uptime targets. |
| **Capacity and performance management** | S-1 | OR-3 | To track hub network and interconnect throughput, avoiding degradation due to load limits. |
| **Access management** | S-1, S-2, S-3, S-4 | OR-8 | To control who can modify platform items within the shared operational model. |
| **Vulnerability and patch management** | S-1, S-2, S-3, S-4 | OR-3 | To proactively scan for weaknesses and apply security patches to the platform. |
| **Security monitoring and response** | S-1, S-2, S-3, S-4 | OR-10 | To watch for misuse and tampering 24x7, specifically protecting audit log integrity. |
| **Cost management** | S-1, S-2, S-3, S-4 | OR-6 | To compile Google Cloud landing zone run costs for the monthly operational report. |
| **Service level management** | S-1, S-2, S-3, S-4 | OR-6 | To track SLA achievements and compile the monthly service level report. |
| **Platform product management** | S-1, S-2, S-3, S-4 | OR-8 | To manage the foundation as a product, prioritizing features by what slows down development teams. |
| **Self-service and golden paths** | S-1, S-3 | OR-4, OR-8 | To offer automated, friction-free defaults for pipeline and network modifications. |
| **Enablement** | S-1, S-2, S-3, S-4 | OR-8 | To assist and pair with developers adopting the platform in a shared service model. |
| **Delivery and developer experience measurement** | S-3 | OR-4 | To measure delivery speed, lead time, and friction to ensure changes deploy quickly and safely. |
| **Supplier management** | S-1, S-2, S-3, S-4 | OR-8, OR-9 | To monitor external service providers and guarantee operational delivery only from the UK, Poland, and India. |
| **Regulatory evidence and reporting** | S-2 | OR-10 | To retain and produce logs as evidence specified by EU DORA. |
# Sources
The capabilities chosen above draw on the following industry frameworks. *Please note that these references are unverified.* The operating model does not claim or certify compliance with any framework.
* **ITIL 4** (PeopleCert)
* Incident management practice
* Monitoring and event management practice
* Problem management practice
* Service request management practice
* Change enablement practice
* Release management and Deployment management practices
* Service configuration management practice
* Service continuity management practice
* Capacity and performance management practice
* Service level management practice
* Supplier management practice
* **Site Reliability Engineering: How Google Runs Production Systems** (Google / O'Reilly)
* Managing Incidents
* Monitoring Distributed Systems
* Postmortem Culture: Learning from Failure
* Release Engineering
* Service Level Objectives
* **ISO/IEC 20000-1**
* Incident management
* Service request management
* Change management
* Service continuity management
* Capacity management
* Service level management
* Supplier management
* **Regulation (EU) 2022/2554, the Digital Operational Resilience Act** (European Union)
* Article 9, Protection and prevention
* Article 10, Detection
* Article 11, Response and recovery
* Article 12, Backup policies and procedures, restoration and recovery procedures and methods
* Article 17, ICT-related incident management process
* Article 19, Reporting of major ICT-related incidents
* Article 28, General principles on ICT third-party risk
* **NIST Cybersecurity Framework 2.0**
* Detect: Continuous Monitoring
* Identify: Asset Management
* Recover: Incident Recovery Plan Execution
* Protect: Identity Management, Authentication, and Access Control
* Protect: Platform Security
* Detect: Adverse Event Analysis; Respond: Incident Management
* **ISO/IEC 27001**
* Access control
* Management of technical vulnerabilities
* Information security incident management
* Compliance with legal and contractual requirements
* **DevOps Research and Assessment (DORA) software delivery metrics**
* Change failure rate
* Deployment frequency and lead time for changes
* Time to restore service
* **FinOps Framework** (FinOps Foundation)
* Allocation; Budgeting; Forecasting; Anomaly Management
* **Team Topologies: Organizing Business and Technology Teams for Fast Flow** (IT Revolution)
* Platform team; Thinnest viable platform
* X-as-a-Service interaction mode
* Enabling team; Facilitating interaction mode
* **CNCF Platforms White Paper (platform as a product)** (Cloud Native Computing Foundation)
* Platform as a product; Measuring platform success
* Platform capabilities; Self-service
* **The SPACE of Developer Productivity**
* Satisfaction and well-being; Performance; Activity; Communication and collaboration; Efficiency and flow
* **DevEx: What Actually Drives Productivity**
* Feedback loops; Cognitive load; Flow state
# Assumptions
- **Service Management Tooling**: We assume the use of native Google Cloud operations tooling without an external ITSM integration, as no separate ITSM system was mandated.
- **Change Process**: We assume that standard infrastructure changes proceed via an automated deployment pipeline with peer reviews, while only network changes demand explicit manual approval from the customer platform team.

View File

@@ -0,0 +1,229 @@
# Operating model guide: Google Cloud Landing Zone
## Summary
This guide sets out the target operating model for the Google Cloud landing zone platform foundation, which comprises the hub network and interconnect, the audit log store, the deployment pipeline, and encryption keys. The platform is operated under a shared service model between the customer and an external service provider. The service provider is responsible for incident response, continuous monitoring, and day-to-day administrative maintenance during 24x7 support hours, while the customer platform team operates during business hours, retaining architectural leadership, platform enablement, and final approval authority over all network changes.
Because all operational checks and scenario walk-throughs pass with no open findings and run costs remain within budget, the reader should look first at the assumptions and open questions, specifically the exclusion of hosted application workloads from platform foundation operations and the confirmation of the go-live date.
### Key figures
- Operated: 4 Items, with 3 Conditions to keep true.
- Faults responded to: 24x7 hours.
- Capabilities: 21.
- People: 6.8. Cost a month: 46,252 GBP, from rate card version `draft-2026-10-13` (placeholder prices: an illustration).
- Scenario walk-throughs: 13 of 13 pass.
- Business outcomes: 3, 3 shown by a Measure.
- Findings for whoever owns the design: 0.
## Business outcomes
**BO-1: New payment products reach customers in weeks rather than months.** Target: A change reaches production within a day of approval..
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Lead time for changes | outcome | dora-metrics | Within a day of approval | Delivery and developer experience measurement | Customer Platform Lead |
**BO-2: Payments are never unavailable for long.** Target: Restored within 4 hours..
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Time to restore service | outcome | dora-metrics | Restored within 4 hours | Delivery and developer experience measurement | Customer Platform Lead |
**BO-3: We keep the platform engineers we hire.**
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Developer satisfaction | guardrail | space-framework | | Delivery and developer experience measurement | Customer Platform Lead |
| Developer cognitive load | leading | devex-framework | | Delivery and developer experience measurement | Customer Platform Lead |
## What is operated
| Item | What it is | Kind | Product | From |
| --- | --- | --- | --- | --- |
| S-1 | Hub network and interconnect | network | Cloud Interconnect | |
| S-2 | Audit log store | storage | Cloud Storage | |
| S-3 | Deployment pipeline | pipeline | Cloud Build | |
| S-4 | Encryption keys | keys | Cloud KMS | |
What must be kept true while it is run:
| Condition | On | What must hold | From |
| --- | --- | --- | --- |
| K-1 | S-1 | The platform is available at least 99.9% of each month. | |
| K-2 | S-2 | Audit logs cannot be deleted for seven years. | |
| K-3 | S-4 | Encryption keys are rotated every 90 days. | |
## Operational requirements
| Requirement | Kind | What must be achieved | From |
| --- | --- | --- | --- |
| OR-1 | service_level | A priority 1 fault on any Item is acknowledged within 15 minutes, at any hour. | service_levels.priority_1_response_minutes, operations.support_hours |
| OR-2 | service_level | Service is restored within 4 hours following a priority 1 incident. | service_levels.recovery_time_hours, BO-2 |
| OR-3 | service_level | The hub network and interconnect maintains at least 99.9% availability during each month. | K-1 |
| OR-4 | service_level | An approved change reaches production within one day of approval. | BO-1 |
| OR-5 | process | Every change to the network requires approval from the customer platform team prior to implementation. | REQ-01 |
| OR-6 | process | A report detailing service levels and operational costs is delivered to the customer monthly. | REQ-02 |
| OR-7 | process | Encryption keys are rotated at least once every 90 days. | K-3 |
| OR-8 | organisation | Platform operations is conducted under a shared service model between the customer and an external service provider. | sourcing.model |
| OR-9 | organisation | Operational delivery is conducted exclusively from the United Kingdom, Poland, and India. | sourcing.delivery_countries |
| OR-10 | compliance | Audit logs cannot be deleted for seven years. | K-2 |
## Capabilities
| Capability | What it is | Serves | Covers | Hours | Effort a month |
| --- | --- | --- | --- | --- | --- |
| C-1 | Incident management | OR-1, OR-2 | S-1, S-2, S-3, S-4 | 24x7 | 40 h |
| C-2 | Monitoring and alerting | OR-1 | S-1, S-2, S-3, S-4 | 24x7 | 30 h |
| C-3 | Problem management | OR-2, OR-3 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-4 | Service request fulfilment | OR-8 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-5 | Change enablement | OR-4, OR-5 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-6 | Release and deployment | OR-4 | S-3 | business | 15 h |
| C-7 | Configuration management | OR-4, OR-5, OR-7 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-8 | Backup and recovery | OR-2, OR-10 | S-2, S-4 | business | 10 h |
| C-9 | Service continuity | OR-3 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-10 | Capacity and performance management | OR-3 | S-1 | business | 5 h |
| C-11 | Access management | OR-8 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-12 | Vulnerability and patch management | OR-3 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-13 | Security monitoring and response | OR-10 | S-1, S-2, S-3, S-4 | 24x7 | 40 h |
| C-14 | Cost management | OR-6 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-15 | Service level management | OR-6 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-16 | Platform product management | OR-8 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-17 | Self-service and golden paths | OR-4, OR-8 | S-1, S-3 | business | 25 h |
| C-18 | Enablement | OR-8 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-19 | Delivery and developer experience measurement | OR-4 | S-3 | business | 15 h |
| C-20 | Supplier management | OR-8, OR-9 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-21 | Regulatory evidence and reporting | OR-10 | S-2 | business | 10 h |
## Who does what
| Role | Party | Country | Level | Hours |
| --- | --- | --- | --- | --- |
| Customer Platform Lead | Customer (customer) | GB | lead | business |
| Customer Platform Engineer | Customer (customer) | GB | senior | business |
| Provider Delivery Lead | Service Provider (provider) | GB | lead | business |
| Provider 24x7 SRE | Service Provider (provider) | PL | senior | 24x7 |
| Provider Platform Engineer | Service Provider (provider) | IN | engineer | business |
The teams, as Team Topologies names their kinds:
| Team | Kind | Party | Roles | Purpose |
| --- | --- | --- | --- | --- |
| Platform team | platform | Customer | Customer Platform Lead, Customer Platform Engineer | Owns the platform roadmap, designs the networking, and provides explicit approvals for structural changes. |
| Provider Operations | platform | Service Provider | Provider Delivery Lead, Provider 24x7 SRE, Provider Platform Engineer | Provides 24x7 incident response, security monitoring, and general infrastructure operational support. |
How the teams work together:
| From | To | Mode | Until | Purpose |
| --- | --- | --- | --- | --- |
| Platform team | Provider Operations | x-as-a-service | | The customer platform team consumes infrastructure monitoring and incident response from the provider operations team as a service. |
| Capability | Customer Platform Lead | Customer Platform Engineer | Provider Delivery Lead | Provider 24x7 SRE | Provider Platform Engineer |
| --- | --- | --- | --- | --- | --- |
| Incident management (C-1) | C | | A | R | |
| Monitoring and alerting (C-2) | C | | A | R | |
| Problem management (C-3) | C | | A | | R |
| Service request fulfilment (C-4) | C | | A | | R |
| Change enablement (C-5) | A | R | | | R |
| Release and deployment (C-6) | A | R | | | |
| Configuration management (C-7) | A | | | | R |
| Backup and recovery (C-8) | C | | A | | R |
| Service continuity (C-9) | C | | A | | R |
| Capacity and performance management (C-10) | A | | | | R |
| Access management (C-11) | C | | A | | R |
| Vulnerability and patch management (C-12) | C | | A | | R |
| Security monitoring and response (C-13) | C | | A | R | |
| Cost management (C-14) | A | | R | | |
| Service level management (C-15) | C | | A/R | | |
| Platform product management (C-16) | A/R | | | | |
| Self-service and golden paths (C-17) | A | R | | | |
| Enablement (C-18) | A | R | | | |
| Delivery and developer experience measurement (C-19) | A | R | | | |
| Supplier management (C-20) | A/R | | | | |
| Regulatory evidence and reporting (C-21) | C | | A | | R |
A accountable, R responsible, C consulted, I informed.
## Staffing and cost
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Customer Platform Lead | Customer | GB | lead | business | 30.0 h | 0.2 | not priced |
| Customer Platform Engineer | Customer | GB | senior | business | 85.0 h | 0.6 | not priced |
| Provider Delivery Lead | Service Provider | GB | lead | business | 20.0 h | 0.1 | 2,212 GBP |
| Provider 24x7 SRE | Service Provider | PL | senior | 24x7 | 110.0 h | 5.0 | 41,640 GBP |
| Provider Platform Engineer | Service Provider | IN | engineer | business | 135.0 h | 0.9 | 2,400 GBP |
6.8 people in all. Cost a month: 46,252 GBP.
The monthly budget is 60,000 GBP: this is within it.
Worked from rate card `rate-card`, version `draft-2026-10-13`. **Its figures are placeholders: no price has been set, and this cost is an illustration.**
Converted from USD at 0.79, a rate set on 2026-10-13.
The customer's own staff are counted and not priced. A Role that covers hours wider than a working day is never smaller than the team that can cover them.
## Validation
| Check | What must hold | Verdict | Evidence |
| --- | --- | --- | --- |
| OC-1 | The hub network and interconnect maintains at least 99.9% availability during each month. | pass | Capability C-1 is responsible for incident management with 24x7 coverage by the Provider 24x7 SRE role (R-4), which is sufficient to maintain highly available operations by responding to faults around the clock. |
| OC-2 | Audit logs are retained for seven years and cannot be deleted during this period. | pass | Capability C-8 manages backup and recovery, validating retention policies for audit logs. It is appropriately staffed during business hours. |
| OC-3 | Encryption keys are rotated at least once every 90 days. | pass | Capability C-7 covers configuration management including tracking key rotation cycles, with the Customer Platform Lead (R-1) accountable and Provider Platform Engineer (R-5) responsible. |
| OC-4 | A priority 1 fault on any Item is acknowledged within 15 minutes, at any hour. | pass | Capability C-1 covers incident management 24x7 with the Provider 24x7 SRE (R-4) responsible, ensuring 15-minute acknowledgement at any hour. |
| OC-5 | Service is restored within 4 hours following a priority 1 incident. | pass | Capability C-1 provides 24x7 incident response, ensuring that service is restored within the 4-hour target following a priority 1 incident. |
| OC-6 | An approved change reaches production within one day of approval. | pass | Capability C-6 manages release and deployment, with the Customer Platform Engineer (R-2) responsible, ensuring approved changes reach production within a day. |
| OC-7 | Every change to the network requires explicit approval from the customer platform team prior to implementation. | pass | Capability C-5 manages change enablement, with the Customer Platform Lead (R-1) accountable and engineers responsible, ensuring network changes require explicit approval. |
| OC-8 | A report detailing service levels is delivered to the customer monthly. | pass | Capability C-15 covers service level management to measure SLA achievement and deliver the monthly report, with the Provider Delivery Lead (R-3) accountable and responsible. |
| OC-9 | Platform operations is conducted under a shared service model between the customer and external provider. | pass | Capability C-20 handles supplier management to ensure shared service model compliance, with the Customer Platform Lead (R-1) accountable and responsible. |
| OC-10 | The Customer Platform Lead role is located in the UK. | pass | The Customer Platform Lead role (R-1) is defined with country 'GB' (UK). |
| OC-11 | The Customer Platform Engineer role is located in the UK. | pass | The Customer Platform Engineer role (R-2) is defined with country 'GB' (UK). |
| OC-12 | The Provider Delivery Lead role is located in the UK. | pass | The Provider Delivery Lead role (R-3) is defined with country 'GB' (UK). |
| OC-13 | The Provider 24x7 SRE role is located in Poland. | pass | The Provider 24x7 SRE role (R-4) is defined with country 'PL' (Poland). |
| OC-14 | The Provider Platform Engineer role is located in India. | pass | The Provider Platform Engineer role (R-5) is defined with country 'IN' (India). |
| OC-15 | A report detailing operational costs is delivered to the customer monthly. | pass | Capability C-14 covers cost management to compile financial reports on monthly landing zone spend, with the Provider Delivery Lead (R-3) responsible. |
Each scenario is generated from the operating model and traced through it by code.
| Scenario | Result | Path |
| --- | --- | --- |
| Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
| Hub network and interconnect (S-1) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
| Audit log store (S-2) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
| Audit log store (S-2) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
| Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
| Deployment pipeline (S-3) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
| Encryption keys (S-4) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
| Encryption keys (S-4) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
| Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. | pass | Check OC-1 on C-1 keeps it true. |
| Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. | pass | Check OC-2 on C-8 keeps it true. |
| Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. | pass | Check OC-3 on C-7 keeps it true. |
| Service Provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
| A month's cost of operating is compared with the budget of 60,000 GBP. | pass | The cost is 46,252 GBP, within the budget. |
## Findings and open questions
No findings: the solution provides what operating it needs.
Assumed for the customer, and open to change when they answer:
- `intent.exclusions`: Application workloads and services hosted on the platform foundation. Assumed based on platform foundation scope: workloads hosted on top of the landing zone are out of scope for this operating model.
- `operations.change_process`: Changes go through a deployment pipeline with peer review, with explicit customer platform team approval required for all network changes.. Pipeline-driven changes with peer review, with customer platform team approval required for network changes per REQ-01.
- `service_management.tooling`: Google Cloud operations suite and native Cloud provider tooling, with no separate external ITSM system.. Default native GCP operations tooling used as no external ITSM was specified.
## Sources
The Capabilities are from our own capability catalogue, which draws on these frameworks. It cites them and certifies nothing against them.
- ITIL 4: Incident management practice; Monitoring and event management practice; Problem management practice; Service request management practice; Change enablement practice; Release management and Deployment management practices; Service configuration management practice; Service continuity management practice; Capacity and performance management practice; Service level management practice; Supplier management practice
- Site Reliability Engineering: How Google Runs Production Systems: Managing Incidents; Monitoring Distributed Systems; Postmortem Culture: Learning from Failure; Release Engineering; Service Level Objectives
- ISO/IEC 20000-1: Incident management; Service request management; Change management; Service continuity management; Capacity management; Service level management; Supplier management
- Regulation (EU) 2022/2554, the Digital Operational Resilience Act: Article 17, ICT-related incident management process; Article 10, Detection; Article 12, Backup policies and procedures, restoration and recovery procedures and methods; Article 11, Response and recovery; Article 9, Protection and prevention; Article 28, General principles on ICT third-party risk; Article 19, Reporting of major ICT-related incidents
- NIST Cybersecurity Framework: Detect: Continuous Monitoring; Identify: Asset Management; Recover: Incident Recovery Plan Execution; Protect: Identity Management, Authentication, and Access Control; Protect: Platform Security; Detect: Adverse Event Analysis; Respond: Incident Management
- DevOps Research and Assessment (DORA) software delivery metrics: Change failure rate; Deployment frequency and lead time for changes; Deployment frequency; Lead time for changes; Change failure rate; Time to restore service
- ISO/IEC 27001: Access control; Management of technical vulnerabilities; Information security incident management; Compliance with legal and contractual requirements
- FinOps Framework: Allocation; Budgeting; Forecasting; Anomaly Management
- CNCF Platforms White Paper (platform as a product): Platform as a product; Measuring platform success; Platform capabilities; Self-service; Platform as a product
- Team Topologies: Organizing Business and Technology Teams for Fast Flow: Platform team; Thinnest viable platform; X-as-a-Service interaction mode; Enabling team; Facilitating interaction mode
- The SPACE of Developer Productivity: Satisfaction and well-being; Performance; Activity; Communication and collaboration; Efficiency and flow
- DevEx: What Actually Drives Productivity: Feedback loops; Cognitive load; Flow state
**These references have not been checked against the frameworks by a person.** Treat each as a pointer to where to look.

View File

@@ -0,0 +1,39 @@
# Scope statement
Operations covers the Google Cloud landing zone platform foundation, comprising the hub network and interconnect, the audit log store, the deployment pipeline, and encryption keys. The platform is operated under a shared service model between the customer's platform team based in the United Kingdom and a service provider delivering from the United Kingdom, Poland, and India, with the customer platform team retaining approval authority over all network changes. Operational support and system availability are maintained on a 24x7 basis, with priority 1 incident response within 15 minutes and target recovery within 4 hours. All operational costs are stated in British Pounds (GBP). Application workloads and services hosted on the platform foundation are excluded from operational scope.
## Information register
20 stated by the customer, 0 answered in conversation, 3 assumed, 10 unknown, 0 not applicable.
| Field | Value | From |
| --- | --- | --- |
| engagement.kind | platform_foundation | the scope spec |
| intent.statement | We want our landing zone run as a shared service from go-live. A provider should respond to faults at every hour, and our own platform team keeps the final say over changes to the network. | the scope spec |
| intent.requirements | [{"id": "REQ-01", "statement": "Our platform team approves every change to the network."}, {"id": "REQ-02", "statement": "We receive a monthly report of service levels and cost."}] | the scope spec |
| intent.business_outcomes | [{"id": "BO-1", "outcome": "New payment products reach customers in weeks rather than months.", "target": "A change reaches production within a day of approval."}, {"id": "BO-2", "outcome": "Payments | the scope spec |
| solution.cloud_provider | gcp | the scope spec |
| solution.items | [{"id": "S-1", "name": "Hub network and interconnect", "kind": "network", "product": "Cloud Interconnect"}, {"id": "S-2", "name": "Audit log store", "kind": "storage", "product": "Cloud Storage"}, {"i | the scope spec |
| solution.conditions | [{"id": "K-1", "on": ["S-1"], "condition": "The platform is available at least 99.9% of each month."}, {"id": "K-2", "on": ["S-2"], "condition": "Audit logs cannot be deleted for seven years."}, {"id" | the scope spec |
| solution.build.duration_days | 36 | the scope spec |
| operations.support_hours | 24x7 | the scope spec |
| operations.availability_hours | 24x7 | the scope spec |
| sourcing.model | shared | the scope spec |
| sourcing.delivery_countries | ["GB", "PL", "IN"] | the scope spec |
| organisation.existing_teams | [{"name": "Platform team", "party": "customer", "hours": "business", "country": "GB"}] | the scope spec |
| service_levels.priority_1_response_minutes | 15 | the scope spec |
| service_levels.recovery_time_hours | 4 | the scope spec |
| compliance.frameworks | ["DORA"] | the scope spec |
| commercial.currency | GBP | the scope spec |
| commercial.monthly_run_budget | 60000 | the scope spec |
| intent.exclusions | ["Application workloads and services hosted on the platform foundation"] | assumed |
| operations.change_process | Changes go through a deployment pipeline with peer review, with explicit customer platform team approval required for all network changes. | assumed |
| service_management.tooling | Google Cloud operations suite and native Cloud provider tooling, with no separate external ITSM system. | assumed |
### Assumptions
| Id | Assumption | If it is wrong |
| --- | --- | --- |
| ASSUMP-01 | Assumed intent.exclusions is ['Application workloads and services hosted on the platform foundation']. Assumed based on platform foundation scope: workloads hosted on top of the landing zone are out of scope for this operating model. | Changes which Capabilities are designed. |
| ASSUMP-02 | Assumed operations.change_process is Changes go through a deployment pipeline with peer review, with explicit customer platform team approval required for all network changes.. Pipeline-driven changes with peer review, with customer platform team approval required for network changes per REQ-01. | Changes change enablement and release. |
| ASSUMP-03 | Assumed service_management.tooling is Google Cloud operations suite and native Cloud provider tooling, with no separate external ITSM system.. Default native GCP operations tooling used as no external ITSM was specified. | Changes tooling and the processes written for it. |

View File

@@ -0,0 +1,45 @@
# Operational requirements
The operational requirements specify what running the Google Cloud platform foundation must achieve. Each requirement is derived directly from customer statements, binding scoping parameters, solution conditions, or stated business outcomes.
### Service level requirements
- **OR-1**: A priority 1 fault on any Item is acknowledged within 15 minutes, at any hour (24x7 coverage).
- **OR-2**: Service is restored within 4 hours following a priority 1 incident or critical failure.
- **OR-3**: The hub network and interconnect maintains at least 99.9% availability during each calendar month.
- **OR-4**: An approved change reaches production deployment within one day of approval.
### Process requirements
- **OR-5**: Every change to the network requires explicit approval from the customer platform team prior to implementation.
- **OR-6**: A report detailing operational service levels and run costs is delivered to the customer on a monthly basis.
- **OR-7**: Cryptographic encryption keys are rotated at least once every 90 days.
### Organisation requirements
- **OR-8**: Platform operations is conducted under a shared service model between the customer and an external service provider.
- **OR-9**: Operational delivery activities are conducted exclusively from the United Kingdom, Poland, and India.
### Compliance requirements
- **OR-10**: Audit logs stored in the audit log store cannot be deleted for seven years.
---
# What was not stated
The operating specification leaves certain operational aspects assumed or unknown. If answered differently by the customer, these would alter the operational requirements.
## Assumptions
- **Scope exclusions (`intent.exclusions`)**: It is assumed that application workloads and services hosted on top of the platform foundation are excluded from operations. If customer workloads were included in scope, additional operational requirements would be needed for workload availability, deployment pipeline maintenance, and application incident response.
- **Change process (`operations.change_process`)**: It is assumed that changes proceed through a continuous deployment pipeline with automated checks and peer review, with customer approval reserved specifically for network modifications. If a centralised Change Advisory Board (CAB) or multi-tier manual approval process were required across all components, change velocity requirements would be directly affected.
- **Service management tooling (`service_management.tooling`)**: It is assumed that Google Cloud native operations suite tooling is utilized without a separate enterprise ITSM platform. If an external ITSM or specific ticketing system were mandated, dedicated tooling integration requirements would apply.
## Unknowns
- **Go-live date (`transition.go_live_date`)**: The target operational cutover date was not specified, leaving transitional readiness timelines to be determined.
- **Customer-owned build components (`solution.build.customer_owned`)**: The exact division of build ownership between customer and suppliers was not defined, which may influence handoff requirements.
- **Inherited risks (`solution.inherited_risks`)**: No existing technical debt or inherited design risks were declared; if identified, specific operational monitoring or mitigation guardrails would be required.
- **Monitoring integrations (`operations.monitoring`)**: Specific external monitoring, log ingestion, or enterprise SIEM destinations were not stated beyond the native audit log store.
- **Operational headcount limits (`organisation.headcount_limit`)**: No upper bound on staffing was set, with staffing to be determined strictly by service hours and capability requirements.

View File

@@ -0,0 +1,66 @@
# Design rationale
## Sourcing and Division of Work
The operating model establishes a shared service model between the Customer (P-1) and an external Service Provider (P-2).
- The **Customer Platform team** (T-1) retains accountability for the platform's architectural integrity and roadmap, as well as operational decisions surrounding changes to the network. The team handles change enablement, self-service golden paths, delivery and developer experience measurement, and capacity management.
- The **Provider Operations team** (T-2) is tasked with delivering 24x7 visibility and stability. They provide incident management, security monitoring, access management, backup and recovery, and handle routine service requests. This arrangement allows the Customer to focus on enablement and evolving the platform product rather than daily operational toil.
## Roles, Countries, and Levels
The Roles map directly to the `sourcing.delivery_countries` constraints (GB, PL, IN) and specific support hours:
- **Customer Platform Lead (GB, Lead, Business hours)**: Ensures accountability and oversees the platform's product roadmap, holding final approval over network changes to meet governance requirements.
- **Customer Platform Engineer (GB, Senior, Business hours)**: Focuses on engineering tasks, automation, enablement, and maintaining the deployment pipeline during standard business hours.
- **Provider Delivery Lead (GB, Lead, Business hours)**: Acts as the primary point of contact for the Service Provider. They are accountable for incident management, security monitoring, and compiling monthly reports (detailing service levels and costs) ensuring strict governance.
- **Provider 24x7 SRE (PL, Senior, 24x7)**: Selected in Poland to offer around-the-clock incident response, event monitoring, and security oversight, ensuring 15-minute response times and four-hour restoration for priority incidents. A senior level is appropriate to diagnose unfamiliar faults and autonomously lead shifts.
- **Provider Platform Engineer (IN, Engineer, Business hours)**: Located in India to provide cost-efficient business-hours support for routine service requests, problem management, access requests, patch management, and configuration tasks.
*(Note: Costs derived from this operating model will use placeholders as the rate card remains in draft.)*
## Assumptions
- We assume that the customer platform team can review and approve network changes within the pipeline seamlessly, without becoming a bottleneck that prevents the 1-day deployment target.
- We assume that natively available GCP tools (like Cloud Monitoring and Cloud Logging) are used for alert configuration and routing to the 24x7 SRE team, avoiding the need for third-party integrations or findings for specific tools.
- We assume backup and recovery policies will be enforced through configuration mechanisms as opposed to creating distinct tools requiring external findings.
## Responsibility matrix
| Capability | Customer Platform Lead | Customer Platform Engineer | Provider Delivery Lead | Provider 24x7 SRE | Provider Platform Engineer |
| --- | --- | --- | --- | --- | --- |
| Incident management (C-1) | C | | A | R | |
| Monitoring and alerting (C-2) | C | | A | R | |
| Problem management (C-3) | C | | A | | R |
| Service request fulfilment (C-4) | C | | A | | R |
| Change enablement (C-5) | A | R | | | R |
| Release and deployment (C-6) | A | R | | | |
| Configuration management (C-7) | A | | | | R |
| Backup and recovery (C-8) | C | | A | | R |
| Service continuity (C-9) | C | | A | | R |
| Capacity and performance management (C-10) | A | | | | R |
| Access management (C-11) | C | | A | | R |
| Vulnerability and patch management (C-12) | C | | A | | R |
| Security monitoring and response (C-13) | C | | A | R | |
| Cost management (C-14) | A | | R | | |
| Service level management (C-15) | C | | A/R | | |
| Platform product management (C-16) | A/R | | | | |
| Self-service and golden paths (C-17) | A | R | | | |
| Enablement (C-18) | A | R | | | |
| Delivery and developer experience measurement (C-19) | A | R | | | |
| Supplier management (C-20) | A/R | | | | |
| Regulatory evidence and reporting (C-21) | C | | A | | R |
A accountable, R responsible, C consulted, I informed.
## Staffing and cost
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Customer Platform Lead | Customer | GB | lead | business | 30.0 h | 0.2 | not priced |
| Customer Platform Engineer | Customer | GB | senior | business | 85.0 h | 0.6 | not priced |
| Provider Delivery Lead | Service Provider | GB | lead | business | 20.0 h | 0.1 | 2,212 GBP |
| Provider 24x7 SRE | Service Provider | PL | senior | 24x7 | 110.0 h | 5.0 | 41,640 GBP |
| Provider Platform Engineer | Service Provider | IN | engineer | business | 135.0 h | 0.9 | 2,400 GBP |
6.8 people in all. Cost a month: 46,252 GBP.
The monthly budget is 60,000 GBP: this is within it.
Worked from rate card `rate-card`, version `draft-2026-10-13`. **Its figures are placeholders: no price has been set, and this cost is an illustration.**
Converted from USD at 0.79, a rate set on 2026-10-13.
The customer's own staff are counted and not priced. A Role that covers hours wider than a working day is never smaller than the team that can cover them.

View File

@@ -0,0 +1,42 @@
# Check verdicts
All checks against the target operating model have successfully passed. The operating model is capable of meeting the defined conditions and requirements as designed.
- **OC-1**: **Pass**. Capability C-1 is responsible for incident management with 24x7 coverage by the Provider 24x7 SRE role (R-4), which is sufficient to maintain highly available operations by responding to faults around the clock.
- **OC-2**: **Pass**. Capability C-8 manages backup and recovery, validating retention policies for audit logs. It is appropriately staffed during business hours.
- **OC-3**: **Pass**. Capability C-7 covers configuration management including tracking key rotation cycles, with the Customer Platform Lead (R-1) accountable and Provider Platform Engineer (R-5) responsible.
- **OC-4**: **Pass**. Capability C-1 covers incident management 24x7 with the Provider 24x7 SRE (R-4) responsible, ensuring 15-minute acknowledgement at any hour.
- **OC-5**: **Pass**. Capability C-1 provides 24x7 incident response, ensuring that service is restored within the 4-hour target following a priority 1 incident.
- **OC-6**: **Pass**. Capability C-6 manages release and deployment, with the Customer Platform Engineer (R-2) responsible, ensuring approved changes reach production within a day.
- **OC-7**: **Pass**. Capability C-5 manages change enablement, with the Customer Platform Lead (R-1) accountable and engineers responsible, ensuring network changes require explicit approval.
- **OC-8**: **Pass**. Capability C-15 covers service level management to measure SLA achievement and deliver the monthly report, with the Provider Delivery Lead (R-3) accountable and responsible.
- **OC-9**: **Pass**. Capability C-20 handles supplier management to ensure shared service model compliance, with the Customer Platform Lead (R-1) accountable and responsible.
- **OC-10**: **Pass**. The Customer Platform Lead role (R-1) is defined with country 'GB' (UK).
- **OC-11**: **Pass**. The Customer Platform Engineer role (R-2) is defined with country 'GB' (UK).
- **OC-12**: **Pass**. The Provider Delivery Lead role (R-3) is defined with country 'GB' (UK).
- **OC-13**: **Pass**. The Provider 24x7 SRE role (R-4) is defined with country 'PL' (Poland).
- **OC-14**: **Pass**. The Provider Platform Engineer role (R-5) is defined with country 'IN' (India).
- **OC-15**: **Pass**. Capability C-14 covers cost management to compile financial reports on monthly landing zone spend, with the Provider Delivery Lead (R-3) responsible.
**Overall Verdict**
**Pass**. The target operating model successfully satisfies all required operational checks.
## Scenario walk-throughs
Each scenario is generated from the operating model and traced through it by code.
| Scenario | Result | Path |
| --- | --- | --- |
| Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
| Hub network and interconnect (S-1) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
| Audit log store (S-2) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
| Audit log store (S-2) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
| Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
| Deployment pipeline (S-3) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
| Encryption keys (S-4) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
| Encryption keys (S-4) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
| Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. | pass | Check OC-1 on C-1 keeps it true. |
| Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. | pass | Check OC-2 on C-8 keeps it true. |
| Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. | pass | Check OC-3 on C-7 keeps it true. |
| Service Provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
| A month's cost of operating is compared with the budget of 60,000 GBP. | pass | The cost is 46,252 GBP, within the budget. |

View File

@@ -0,0 +1,113 @@
{
"customer_case": "bench-landing-zone-shared",
"execution_id": "case-01-landing-zone-shared-r1",
"session_id": "9fe31b7a-c779-4d34-bcee-cc2e36533a1d",
"intent_version": 1,
"workflow_request": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.",
"baseline": null,
"overlay_skills": {},
"options": {},
"sources": {},
"scope": {
"status": "BASELINE_LOCKED",
"readiness": {
"supplied": 20,
"answered": 0,
"assumed": 3,
"unknown": 10,
"not_applicable": 0
}
},
"status": "completed",
"warnings": [],
"risks": [],
"assessment": null,
"phases": {
"scoping": "approved",
"operational_requirements": "approved",
"operating_model_design": "approved",
"validation": "approved",
"packaging": "approved"
},
"final_document": "operating-model-guide.md",
"changes": null,
"deliverables": {
"operating_scope": {
"document": "deliverables/operating_scope.md",
"attachments": [
"scope.json",
"scope.yaml"
],
"status": "submitted"
},
"operational_requirements": {
"document": "deliverables/operational_requirements.md",
"attachments": [
"operational-requirements.json"
],
"status": "submitted"
},
"capability_model": {
"document": "deliverables/capability_model.md",
"attachments": [
"capabilities.json"
],
"status": "submitted"
},
"target_operating_model": {
"document": "deliverables/target_operating_model.md",
"attachments": [
"findings.json",
"organisation.mmd",
"staffing.json",
"target-operating-model.json"
],
"status": "submitted"
},
"validation_results": {
"document": "deliverables/validation_results.md",
"attachments": [
"scenarios.json",
"verdicts.json"
],
"status": "submitted"
},
"operating_model_guide": {
"document": "deliverables/operating_model_guide.md",
"attachments": [],
"status": "submitted"
}
},
"files": [
"capabilities.json",
"deliverables/capability_model.md",
"deliverables/operating_model_guide.md",
"deliverables/operating_scope.md",
"deliverables/operational_requirements.md",
"deliverables/target_operating_model.md",
"deliverables/validation_results.md",
"findings.json",
"operating-model-guide.md",
"operational-requirements.json",
"organisation.mmd",
"scenarios.json",
"scope.json",
"scope.yaml",
"staffing.json",
"target-operating-model.json",
"verdicts.json"
],
"staffing": {
"people": 6.8,
"cost_per_month": 46252,
"currency": "GBP",
"rate_card": {
"name": "rate-card",
"version": "draft-2026-10-13",
"draft": true
}
},
"findings": [],
"change_request": null,
"capability_sources_verified": false
}

View File

@@ -0,0 +1,229 @@
# Operating model guide: Google Cloud Landing Zone
## Summary
This guide sets out the target operating model for the Google Cloud landing zone platform foundation, which comprises the hub network and interconnect, the audit log store, the deployment pipeline, and encryption keys. The platform is operated under a shared service model between the customer and an external service provider. The service provider is responsible for incident response, continuous monitoring, and day-to-day administrative maintenance during 24x7 support hours, while the customer platform team operates during business hours, retaining architectural leadership, platform enablement, and final approval authority over all network changes.
Because all operational checks and scenario walk-throughs pass with no open findings and run costs remain within budget, the reader should look first at the assumptions and open questions, specifically the exclusion of hosted application workloads from platform foundation operations and the confirmation of the go-live date.
### Key figures
- Operated: 4 Items, with 3 Conditions to keep true.
- Faults responded to: 24x7 hours.
- Capabilities: 21.
- People: 6.8. Cost a month: 46,252 GBP, from rate card version `draft-2026-10-13` (placeholder prices: an illustration).
- Scenario walk-throughs: 13 of 13 pass.
- Business outcomes: 3, 3 shown by a Measure.
- Findings for whoever owns the design: 0.
## Business outcomes
**BO-1: New payment products reach customers in weeks rather than months.** Target: A change reaches production within a day of approval..
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Lead time for changes | outcome | dora-metrics | Within a day of approval | Delivery and developer experience measurement | Customer Platform Lead |
**BO-2: Payments are never unavailable for long.** Target: Restored within 4 hours..
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Time to restore service | outcome | dora-metrics | Restored within 4 hours | Delivery and developer experience measurement | Customer Platform Lead |
**BO-3: We keep the platform engineers we hire.**
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Developer satisfaction | guardrail | space-framework | | Delivery and developer experience measurement | Customer Platform Lead |
| Developer cognitive load | leading | devex-framework | | Delivery and developer experience measurement | Customer Platform Lead |
## What is operated
| Item | What it is | Kind | Product | From |
| --- | --- | --- | --- | --- |
| S-1 | Hub network and interconnect | network | Cloud Interconnect | |
| S-2 | Audit log store | storage | Cloud Storage | |
| S-3 | Deployment pipeline | pipeline | Cloud Build | |
| S-4 | Encryption keys | keys | Cloud KMS | |
What must be kept true while it is run:
| Condition | On | What must hold | From |
| --- | --- | --- | --- |
| K-1 | S-1 | The platform is available at least 99.9% of each month. | |
| K-2 | S-2 | Audit logs cannot be deleted for seven years. | |
| K-3 | S-4 | Encryption keys are rotated every 90 days. | |
## Operational requirements
| Requirement | Kind | What must be achieved | From |
| --- | --- | --- | --- |
| OR-1 | service_level | A priority 1 fault on any Item is acknowledged within 15 minutes, at any hour. | service_levels.priority_1_response_minutes, operations.support_hours |
| OR-2 | service_level | Service is restored within 4 hours following a priority 1 incident. | service_levels.recovery_time_hours, BO-2 |
| OR-3 | service_level | The hub network and interconnect maintains at least 99.9% availability during each month. | K-1 |
| OR-4 | service_level | An approved change reaches production within one day of approval. | BO-1 |
| OR-5 | process | Every change to the network requires approval from the customer platform team prior to implementation. | REQ-01 |
| OR-6 | process | A report detailing service levels and operational costs is delivered to the customer monthly. | REQ-02 |
| OR-7 | process | Encryption keys are rotated at least once every 90 days. | K-3 |
| OR-8 | organisation | Platform operations is conducted under a shared service model between the customer and an external service provider. | sourcing.model |
| OR-9 | organisation | Operational delivery is conducted exclusively from the United Kingdom, Poland, and India. | sourcing.delivery_countries |
| OR-10 | compliance | Audit logs cannot be deleted for seven years. | K-2 |
## Capabilities
| Capability | What it is | Serves | Covers | Hours | Effort a month |
| --- | --- | --- | --- | --- | --- |
| C-1 | Incident management | OR-1, OR-2 | S-1, S-2, S-3, S-4 | 24x7 | 40 h |
| C-2 | Monitoring and alerting | OR-1 | S-1, S-2, S-3, S-4 | 24x7 | 30 h |
| C-3 | Problem management | OR-2, OR-3 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-4 | Service request fulfilment | OR-8 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-5 | Change enablement | OR-4, OR-5 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-6 | Release and deployment | OR-4 | S-3 | business | 15 h |
| C-7 | Configuration management | OR-4, OR-5, OR-7 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-8 | Backup and recovery | OR-2, OR-10 | S-2, S-4 | business | 10 h |
| C-9 | Service continuity | OR-3 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-10 | Capacity and performance management | OR-3 | S-1 | business | 5 h |
| C-11 | Access management | OR-8 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-12 | Vulnerability and patch management | OR-3 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-13 | Security monitoring and response | OR-10 | S-1, S-2, S-3, S-4 | 24x7 | 40 h |
| C-14 | Cost management | OR-6 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-15 | Service level management | OR-6 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-16 | Platform product management | OR-8 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-17 | Self-service and golden paths | OR-4, OR-8 | S-1, S-3 | business | 25 h |
| C-18 | Enablement | OR-8 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-19 | Delivery and developer experience measurement | OR-4 | S-3 | business | 15 h |
| C-20 | Supplier management | OR-8, OR-9 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-21 | Regulatory evidence and reporting | OR-10 | S-2 | business | 10 h |
## Who does what
| Role | Party | Country | Level | Hours |
| --- | --- | --- | --- | --- |
| Customer Platform Lead | Customer (customer) | GB | lead | business |
| Customer Platform Engineer | Customer (customer) | GB | senior | business |
| Provider Delivery Lead | Service Provider (provider) | GB | lead | business |
| Provider 24x7 SRE | Service Provider (provider) | PL | senior | 24x7 |
| Provider Platform Engineer | Service Provider (provider) | IN | engineer | business |
The teams, as Team Topologies names their kinds:
| Team | Kind | Party | Roles | Purpose |
| --- | --- | --- | --- | --- |
| Platform team | platform | Customer | Customer Platform Lead, Customer Platform Engineer | Owns the platform roadmap, designs the networking, and provides explicit approvals for structural changes. |
| Provider Operations | platform | Service Provider | Provider Delivery Lead, Provider 24x7 SRE, Provider Platform Engineer | Provides 24x7 incident response, security monitoring, and general infrastructure operational support. |
How the teams work together:
| From | To | Mode | Until | Purpose |
| --- | --- | --- | --- | --- |
| Platform team | Provider Operations | x-as-a-service | | The customer platform team consumes infrastructure monitoring and incident response from the provider operations team as a service. |
| Capability | Customer Platform Lead | Customer Platform Engineer | Provider Delivery Lead | Provider 24x7 SRE | Provider Platform Engineer |
| --- | --- | --- | --- | --- | --- |
| Incident management (C-1) | C | | A | R | |
| Monitoring and alerting (C-2) | C | | A | R | |
| Problem management (C-3) | C | | A | | R |
| Service request fulfilment (C-4) | C | | A | | R |
| Change enablement (C-5) | A | R | | | R |
| Release and deployment (C-6) | A | R | | | |
| Configuration management (C-7) | A | | | | R |
| Backup and recovery (C-8) | C | | A | | R |
| Service continuity (C-9) | C | | A | | R |
| Capacity and performance management (C-10) | A | | | | R |
| Access management (C-11) | C | | A | | R |
| Vulnerability and patch management (C-12) | C | | A | | R |
| Security monitoring and response (C-13) | C | | A | R | |
| Cost management (C-14) | A | | R | | |
| Service level management (C-15) | C | | A/R | | |
| Platform product management (C-16) | A/R | | | | |
| Self-service and golden paths (C-17) | A | R | | | |
| Enablement (C-18) | A | R | | | |
| Delivery and developer experience measurement (C-19) | A | R | | | |
| Supplier management (C-20) | A/R | | | | |
| Regulatory evidence and reporting (C-21) | C | | A | | R |
A accountable, R responsible, C consulted, I informed.
## Staffing and cost
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Customer Platform Lead | Customer | GB | lead | business | 30.0 h | 0.2 | not priced |
| Customer Platform Engineer | Customer | GB | senior | business | 85.0 h | 0.6 | not priced |
| Provider Delivery Lead | Service Provider | GB | lead | business | 20.0 h | 0.1 | 2,212 GBP |
| Provider 24x7 SRE | Service Provider | PL | senior | 24x7 | 110.0 h | 5.0 | 41,640 GBP |
| Provider Platform Engineer | Service Provider | IN | engineer | business | 135.0 h | 0.9 | 2,400 GBP |
6.8 people in all. Cost a month: 46,252 GBP.
The monthly budget is 60,000 GBP: this is within it.
Worked from rate card `rate-card`, version `draft-2026-10-13`. **Its figures are placeholders: no price has been set, and this cost is an illustration.**
Converted from USD at 0.79, a rate set on 2026-10-13.
The customer's own staff are counted and not priced. A Role that covers hours wider than a working day is never smaller than the team that can cover them.
## Validation
| Check | What must hold | Verdict | Evidence |
| --- | --- | --- | --- |
| OC-1 | The hub network and interconnect maintains at least 99.9% availability during each month. | pass | Capability C-1 is responsible for incident management with 24x7 coverage by the Provider 24x7 SRE role (R-4), which is sufficient to maintain highly available operations by responding to faults around the clock. |
| OC-2 | Audit logs are retained for seven years and cannot be deleted during this period. | pass | Capability C-8 manages backup and recovery, validating retention policies for audit logs. It is appropriately staffed during business hours. |
| OC-3 | Encryption keys are rotated at least once every 90 days. | pass | Capability C-7 covers configuration management including tracking key rotation cycles, with the Customer Platform Lead (R-1) accountable and Provider Platform Engineer (R-5) responsible. |
| OC-4 | A priority 1 fault on any Item is acknowledged within 15 minutes, at any hour. | pass | Capability C-1 covers incident management 24x7 with the Provider 24x7 SRE (R-4) responsible, ensuring 15-minute acknowledgement at any hour. |
| OC-5 | Service is restored within 4 hours following a priority 1 incident. | pass | Capability C-1 provides 24x7 incident response, ensuring that service is restored within the 4-hour target following a priority 1 incident. |
| OC-6 | An approved change reaches production within one day of approval. | pass | Capability C-6 manages release and deployment, with the Customer Platform Engineer (R-2) responsible, ensuring approved changes reach production within a day. |
| OC-7 | Every change to the network requires explicit approval from the customer platform team prior to implementation. | pass | Capability C-5 manages change enablement, with the Customer Platform Lead (R-1) accountable and engineers responsible, ensuring network changes require explicit approval. |
| OC-8 | A report detailing service levels is delivered to the customer monthly. | pass | Capability C-15 covers service level management to measure SLA achievement and deliver the monthly report, with the Provider Delivery Lead (R-3) accountable and responsible. |
| OC-9 | Platform operations is conducted under a shared service model between the customer and external provider. | pass | Capability C-20 handles supplier management to ensure shared service model compliance, with the Customer Platform Lead (R-1) accountable and responsible. |
| OC-10 | The Customer Platform Lead role is located in the UK. | pass | The Customer Platform Lead role (R-1) is defined with country 'GB' (UK). |
| OC-11 | The Customer Platform Engineer role is located in the UK. | pass | The Customer Platform Engineer role (R-2) is defined with country 'GB' (UK). |
| OC-12 | The Provider Delivery Lead role is located in the UK. | pass | The Provider Delivery Lead role (R-3) is defined with country 'GB' (UK). |
| OC-13 | The Provider 24x7 SRE role is located in Poland. | pass | The Provider 24x7 SRE role (R-4) is defined with country 'PL' (Poland). |
| OC-14 | The Provider Platform Engineer role is located in India. | pass | The Provider Platform Engineer role (R-5) is defined with country 'IN' (India). |
| OC-15 | A report detailing operational costs is delivered to the customer monthly. | pass | Capability C-14 covers cost management to compile financial reports on monthly landing zone spend, with the Provider Delivery Lead (R-3) responsible. |
Each scenario is generated from the operating model and traced through it by code.
| Scenario | Result | Path |
| --- | --- | --- |
| Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
| Hub network and interconnect (S-1) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
| Audit log store (S-2) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
| Audit log store (S-2) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
| Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
| Deployment pipeline (S-3) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
| Encryption keys (S-4) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
| Encryption keys (S-4) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
| Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. | pass | Check OC-1 on C-1 keeps it true. |
| Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. | pass | Check OC-2 on C-8 keeps it true. |
| Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. | pass | Check OC-3 on C-7 keeps it true. |
| Service Provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
| A month's cost of operating is compared with the budget of 60,000 GBP. | pass | The cost is 46,252 GBP, within the budget. |
## Findings and open questions
No findings: the solution provides what operating it needs.
Assumed for the customer, and open to change when they answer:
- `intent.exclusions`: Application workloads and services hosted on the platform foundation. Assumed based on platform foundation scope: workloads hosted on top of the landing zone are out of scope for this operating model.
- `operations.change_process`: Changes go through a deployment pipeline with peer review, with explicit customer platform team approval required for all network changes.. Pipeline-driven changes with peer review, with customer platform team approval required for network changes per REQ-01.
- `service_management.tooling`: Google Cloud operations suite and native Cloud provider tooling, with no separate external ITSM system.. Default native GCP operations tooling used as no external ITSM was specified.
## Sources
The Capabilities are from our own capability catalogue, which draws on these frameworks. It cites them and certifies nothing against them.
- ITIL 4: Incident management practice; Monitoring and event management practice; Problem management practice; Service request management practice; Change enablement practice; Release management and Deployment management practices; Service configuration management practice; Service continuity management practice; Capacity and performance management practice; Service level management practice; Supplier management practice
- Site Reliability Engineering: How Google Runs Production Systems: Managing Incidents; Monitoring Distributed Systems; Postmortem Culture: Learning from Failure; Release Engineering; Service Level Objectives
- ISO/IEC 20000-1: Incident management; Service request management; Change management; Service continuity management; Capacity management; Service level management; Supplier management
- Regulation (EU) 2022/2554, the Digital Operational Resilience Act: Article 17, ICT-related incident management process; Article 10, Detection; Article 12, Backup policies and procedures, restoration and recovery procedures and methods; Article 11, Response and recovery; Article 9, Protection and prevention; Article 28, General principles on ICT third-party risk; Article 19, Reporting of major ICT-related incidents
- NIST Cybersecurity Framework: Detect: Continuous Monitoring; Identify: Asset Management; Recover: Incident Recovery Plan Execution; Protect: Identity Management, Authentication, and Access Control; Protect: Platform Security; Detect: Adverse Event Analysis; Respond: Incident Management
- DevOps Research and Assessment (DORA) software delivery metrics: Change failure rate; Deployment frequency and lead time for changes; Deployment frequency; Lead time for changes; Change failure rate; Time to restore service
- ISO/IEC 27001: Access control; Management of technical vulnerabilities; Information security incident management; Compliance with legal and contractual requirements
- FinOps Framework: Allocation; Budgeting; Forecasting; Anomaly Management
- CNCF Platforms White Paper (platform as a product): Platform as a product; Measuring platform success; Platform capabilities; Self-service; Platform as a product
- Team Topologies: Organizing Business and Technology Teams for Fast Flow: Platform team; Thinnest viable platform; X-as-a-Service interaction mode; Enabling team; Facilitating interaction mode
- The SPACE of Developer Productivity: Satisfaction and well-being; Performance; Activity; Communication and collaboration; Efficiency and flow
- DevEx: What Actually Drives Productivity: Feedback loops; Cognitive load; Flow state
**These references have not been checked against the frameworks by a person.** Treat each as a pointer to where to look.

View File

@@ -0,0 +1,84 @@
[
{
"id": "OR-1",
"kind": "service_level",
"statement": "A priority 1 fault on any Item is acknowledged within 15 minutes, at any hour.",
"source": [
"service_levels.priority_1_response_minutes",
"operations.support_hours"
]
},
{
"id": "OR-2",
"kind": "service_level",
"statement": "Service is restored within 4 hours following a priority 1 incident.",
"source": [
"service_levels.recovery_time_hours",
"BO-2"
]
},
{
"id": "OR-3",
"kind": "service_level",
"statement": "The hub network and interconnect maintains at least 99.9% availability during each month.",
"source": [
"K-1"
]
},
{
"id": "OR-4",
"kind": "service_level",
"statement": "An approved change reaches production within one day of approval.",
"source": [
"BO-1"
]
},
{
"id": "OR-5",
"kind": "process",
"statement": "Every change to the network requires approval from the customer platform team prior to implementation.",
"source": [
"REQ-01"
]
},
{
"id": "OR-6",
"kind": "process",
"statement": "A report detailing service levels and operational costs is delivered to the customer monthly.",
"source": [
"REQ-02"
]
},
{
"id": "OR-7",
"kind": "process",
"statement": "Encryption keys are rotated at least once every 90 days.",
"source": [
"K-3"
]
},
{
"id": "OR-8",
"kind": "organisation",
"statement": "Platform operations is conducted under a shared service model between the customer and an external service provider.",
"source": [
"sourcing.model"
]
},
{
"id": "OR-9",
"kind": "organisation",
"statement": "Operational delivery is conducted exclusively from the United Kingdom, Poland, and India.",
"source": [
"sourcing.delivery_countries"
]
},
{
"id": "OR-10",
"kind": "compliance",
"statement": "Audit logs cannot be deleted for seven years.",
"source": [
"K-2"
]
}
]

View File

@@ -0,0 +1,15 @@
flowchart TB
subgraph P_1["Customer (customer)"]
subgraph T_1["Platform team (platform team)"]
R_1["Customer Platform Lead<br/>GB, lead, business"]
R_2["Customer Platform Engineer<br/>GB, senior, business"]
end
end
subgraph P_2["Service Provider (provider)"]
subgraph T_2["Provider Operations (platform team)"]
R_3["Provider Delivery Lead<br/>GB, lead, business"]
R_4["Provider 24x7 SRE<br/>PL, senior, 24x7"]
R_5["Provider Platform Engineer<br/>IN, engineer, business"]
end
end
T_1 -- "x-as-a-service" --> T_2

View File

@@ -0,0 +1,93 @@
[
{
"id": "SC-fault-S-1",
"scenario": "Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7).",
"about": "S-1",
"passes": true,
"path": "Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
},
{
"id": "SC-change-S-1",
"scenario": "Hub network and interconnect (S-1) must be changed.",
"about": "S-1",
"passes": true,
"path": "Customer Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-2",
"scenario": "Audit log store (S-2) fails at an hour faults are responded to (24x7).",
"about": "S-2",
"passes": true,
"path": "Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
},
{
"id": "SC-change-S-2",
"scenario": "Audit log store (S-2) must be changed.",
"about": "S-2",
"passes": true,
"path": "Customer Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-3",
"scenario": "Deployment pipeline (S-3) fails at an hour faults are responded to (24x7).",
"about": "S-3",
"passes": true,
"path": "Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
},
{
"id": "SC-change-S-3",
"scenario": "Deployment pipeline (S-3) must be changed.",
"about": "S-3",
"passes": true,
"path": "Customer Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-4",
"scenario": "Encryption keys (S-4) fails at an hour faults are responded to (24x7).",
"about": "S-4",
"passes": true,
"path": "Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
},
{
"id": "SC-change-S-4",
"scenario": "Encryption keys (S-4) must be changed.",
"about": "S-4",
"passes": true,
"path": "Customer Platform Engineer makes the change under C-5."
},
{
"id": "SC-condition-K-1",
"scenario": "Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month.",
"about": "K-1",
"passes": true,
"path": "Check OC-1 on C-1 keeps it true."
},
{
"id": "SC-condition-K-2",
"scenario": "Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years.",
"about": "K-2",
"passes": true,
"path": "Check OC-2 on C-8 keeps it true."
},
{
"id": "SC-condition-K-3",
"scenario": "Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days.",
"about": "K-3",
"passes": true,
"path": "Check OC-3 on C-7 keeps it true."
},
{
"id": "SC-party-P-2",
"scenario": "Service Provider cannot be reached.",
"about": "P-2",
"passes": true,
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
},
{
"id": "SC-budget",
"scenario": "A month's cost of operating is compared with the budget of 60,000 GBP.",
"about": "commercial.monthly_run_budget",
"passes": true,
"path": "The cost is 46,252 GBP, within the budget."
}
]

View File

@@ -0,0 +1,202 @@
{
"kind": "platform_foundation",
"stated": {
"engagement": {
"kind": "platform_foundation"
},
"intent": {
"statement": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.\n",
"requirements": [
{
"id": "REQ-01",
"statement": "Our platform team approves every change to the network."
},
{
"id": "REQ-02",
"statement": "We receive a monthly report of service levels and cost."
}
],
"business_outcomes": [
{
"id": "BO-1",
"outcome": "New payment products reach customers in weeks rather than months.",
"target": "A change reaches production within a day of approval."
},
{
"id": "BO-2",
"outcome": "Payments are never unavailable for long.",
"target": "Restored within 4 hours."
},
{
"id": "BO-3",
"outcome": "We keep the platform engineers we hire."
}
]
},
"solution": {
"cloud_provider": "gcp",
"items": [
{
"id": "S-1",
"name": "Hub network and interconnect",
"kind": "network",
"product": "Cloud Interconnect"
},
{
"id": "S-2",
"name": "Audit log store",
"kind": "storage",
"product": "Cloud Storage"
},
{
"id": "S-3",
"name": "Deployment pipeline",
"kind": "pipeline",
"product": "Cloud Build"
},
{
"id": "S-4",
"name": "Encryption keys",
"kind": "keys",
"product": "Cloud KMS"
}
],
"conditions": [
{
"id": "K-1",
"on": [
"S-1"
],
"condition": "The platform is available at least 99.9% of each month."
},
{
"id": "K-2",
"on": [
"S-2"
],
"condition": "Audit logs cannot be deleted for seven years."
},
{
"id": "K-3",
"on": [
"S-4"
],
"condition": "Encryption keys are rotated every 90 days."
}
],
"build": {
"duration_days": 36
}
},
"operations": {
"support_hours": "24x7",
"availability_hours": "24x7"
},
"sourcing": {
"model": "shared",
"delivery_countries": [
"GB",
"PL",
"IN"
]
},
"organisation": {
"existing_teams": [
{
"name": "Platform team",
"party": "customer",
"hours": "business",
"country": "GB"
}
]
},
"service_levels": {
"priority_1_response_minutes": 15,
"recovery_time_hours": 4
},
"compliance": {
"frameworks": [
"DORA"
]
},
"commercial": {
"currency": "GBP",
"monthly_run_budget": 60000
}
},
"binding": [
"operations.support_hours",
"sourcing.model",
"sourcing.delivery_countries",
"service_levels.priority_1_response_minutes",
"service_levels.recovery_time_hours"
],
"assumed": [
{
"field": "intent.exclusions",
"value": [
"Application workloads and services hosted on the platform foundation"
],
"why": "Assumed based on platform foundation scope: workloads hosted on top of the landing zone are out of scope for this operating model."
},
{
"field": "operations.change_process",
"value": "Changes go through a deployment pipeline with peer review, with explicit customer platform team approval required for all network changes.",
"why": "Pipeline-driven changes with peer review, with customer platform team approval required for network changes per REQ-01."
},
{
"field": "service_management.tooling",
"value": "Google Cloud operations suite and native Cloud provider tooling, with no separate external ITSM system.",
"why": "Default native GCP operations tooling used as no external ITSM was specified."
}
],
"to_decide": [],
"to_ask": [
{
"field": "metadata.client_name",
"prompt": "What is metadata.client_name?",
"severity": "LOW"
},
{
"field": "metadata.author",
"prompt": "What is metadata.author?",
"severity": "LOW"
},
{
"field": "metadata.revision",
"prompt": "What is metadata.revision?",
"severity": "LOW"
},
{
"field": "metadata.source",
"prompt": "What is metadata.source?",
"severity": "LOW"
},
{
"field": "solution.build.customer_owned",
"prompt": "Which parts of the build does the customer or their supplier own?",
"severity": "LOW"
},
{
"field": "solution.inherited_risks",
"prompt": "What is already known to be unverified or at risk in the solution?",
"severity": "LOW"
},
{
"field": "operations.monitoring",
"prompt": "Which monitoring and alerting is already in place or required?",
"severity": "LOW"
},
{
"field": "organisation.headcount_limit",
"prompt": "Is there a limit on the number of people operating this?",
"severity": "LOW"
},
{
"field": "transition.go_live_date",
"prompt": "When must the solution be in operation?",
"severity": "LOW"
}
],
"not_applicable": []
}

View File

@@ -0,0 +1,198 @@
schema_version: 1
metadata:
customer_case: bench-landing-zone-shared
client_name: ask
author: ask
revision: ask
source: ask
status: BASELINE_LOCKED
engagement:
kind: platform_foundation
intent:
statement: 'We want our landing zone run as a shared service from go-live. A provider
should
respond to faults at every hour, and our own platform team keeps the final say
over changes to the network.
'
requirements:
- id: REQ-01
statement: Our platform team approves every change to the network.
- id: REQ-02
statement: We receive a monthly report of service levels and cost.
business_outcomes:
- id: BO-1
outcome: New payment products reach customers in weeks rather than months.
target: A change reaches production within a day of approval.
- id: BO-2
outcome: Payments are never unavailable for long.
target: Restored within 4 hours.
- id: BO-3
outcome: We keep the platform engineers we hire.
exclusions:
- Application workloads and services hosted on the platform foundation
solution:
cloud_provider: gcp
items:
- id: S-1
name: Hub network and interconnect
kind: network
product: Cloud Interconnect
- id: S-2
name: Audit log store
kind: storage
product: Cloud Storage
- id: S-3
name: Deployment pipeline
kind: pipeline
product: Cloud Build
- id: S-4
name: Encryption keys
kind: keys
product: Cloud KMS
conditions:
- id: K-1
'on':
- S-1
condition: The platform is available at least 99.9% of each month.
- id: K-2
'on':
- S-2
condition: Audit logs cannot be deleted for seven years.
- id: K-3
'on':
- S-4
condition: Encryption keys are rotated every 90 days.
build:
duration_days: 36
customer_owned: ask
inherited_risks: ask
operations:
support_hours: 24x7
availability_hours: 24x7
change_process: Changes go through a deployment pipeline with peer review, with
explicit customer platform team approval required for all network changes.
monitoring: ask
sourcing:
model: shared
delivery_countries:
- GB
- PL
- IN
organisation:
existing_teams:
- name: Platform team
party: customer
hours: business
country: GB
headcount_limit: ask
service_management:
tooling: Google Cloud operations suite and native Cloud provider tooling, with no
separate external ITSM system.
service_levels:
priority_1_response_minutes: 15
recovery_time_hours: 4
compliance:
frameworks:
- DORA
commercial:
currency: GBP
monthly_run_budget: 60000
transition:
go_live_date: ask
run:
pre_approved: true
overlay_skills: ask
inferred_assumptions:
- id: ASSUMP-01
field: intent.exclusions
statement: 'Assumed intent.exclusions is [''Application workloads and services hosted
on the platform foundation'']. Assumed based on platform foundation scope: workloads
hosted on top of the landing zone are out of scope for this operating model.'
impact_if_invalid: Changes which Capabilities are designed.
- id: ASSUMP-02
field: operations.change_process
statement: Assumed operations.change_process is Changes go through a deployment
pipeline with peer review, with explicit customer platform team approval required
for all network changes.. Pipeline-driven changes with peer review, with customer
platform team approval required for network changes per REQ-01.
impact_if_invalid: Changes change enablement and release.
- id: ASSUMP-03
field: service_management.tooling
statement: Assumed service_management.tooling is Google Cloud operations suite and
native Cloud provider tooling, with no separate external ITSM system.. Default
native GCP operations tooling used as no external ITSM was specified.
impact_if_invalid: Changes tooling and the processes written for it.
discovery_gaps:
- field: metadata.client_name
prompt: What is metadata.client_name?
severity: LOW
- field: metadata.author
prompt: What is metadata.author?
severity: LOW
- field: metadata.revision
prompt: What is metadata.revision?
severity: LOW
- field: metadata.source
prompt: What is metadata.source?
severity: LOW
- field: solution.build.customer_owned
prompt: Which parts of the build does the customer or their supplier own?
severity: LOW
- field: solution.inherited_risks
prompt: What is already known to be unverified or at risk in the solution?
severity: LOW
- field: operations.monitoring
prompt: Which monitoring and alerting is already in place or required?
severity: LOW
- field: organisation.headcount_limit
prompt: Is there a limit on the number of people operating this?
severity: LOW
- field: transition.go_live_date
prompt: When must the solution be in operation?
severity: LOW
- field: run.overlay_skills
prompt: Which overlay Skills should this Execution load?
severity: LOW
provenance:
commercial.currency: supplied
commercial.monthly_run_budget: supplied
compliance.frameworks: supplied
engagement.kind: supplied
intent.business_outcomes: supplied
intent.exclusions: assumed
intent.requirements: supplied
intent.statement: supplied
metadata.author: unknown
metadata.client_name: unknown
metadata.customer_case: supplied
metadata.revision: unknown
metadata.source: unknown
operations.availability_hours: supplied
operations.change_process: assumed
operations.monitoring: unknown
operations.support_hours: supplied
organisation.existing_teams: supplied
organisation.headcount_limit: unknown
run.overlay_skills: unknown
run.pre_approved: supplied
service_levels.priority_1_response_minutes: supplied
service_levels.recovery_time_hours: supplied
service_management.tooling: assumed
solution.build.customer_owned: unknown
solution.build.duration_days: supplied
solution.cloud_provider: supplied
solution.conditions: supplied
solution.inherited_risks: unknown
solution.items: supplied
sourcing.delivery_countries: supplied
sourcing.model: supplied
transition.go_live_date: unknown
readiness:
supplied: 20
answered: 0
assumed: 3
unknown: 10
not_applicable: 0

View File

@@ -0,0 +1,102 @@
{
"currency": "GBP",
"rate_card": {
"name": "rate-card",
"version": "draft-2026-10-13",
"draft": true
},
"conversion": {
"from": "USD",
"rate": 0.79,
"as_of": "2026-10-13"
},
"roles": [
{
"role": "R-1",
"name": "Customer Platform Lead",
"party": "P-1",
"party_name": "Customer",
"country": "GB",
"level": "lead",
"hours": "business",
"effort_hours_per_month": 30.0,
"people": 0.2,
"cost_per_month": null
},
{
"role": "R-2",
"name": "Customer Platform Engineer",
"party": "P-1",
"party_name": "Customer",
"country": "GB",
"level": "senior",
"hours": "business",
"effort_hours_per_month": 85.0,
"people": 0.6,
"cost_per_month": null
},
{
"role": "R-3",
"name": "Provider Delivery Lead",
"party": "P-2",
"party_name": "Service Provider",
"country": "GB",
"level": "lead",
"hours": "business",
"effort_hours_per_month": 20.0,
"people": 0.1,
"cost_per_month": 2212
},
{
"role": "R-4",
"name": "Provider 24x7 SRE",
"party": "P-2",
"party_name": "Service Provider",
"country": "PL",
"level": "senior",
"hours": "24x7",
"effort_hours_per_month": 110.0,
"people": 5.0,
"cost_per_month": 41640
},
{
"role": "R-5",
"name": "Provider Platform Engineer",
"party": "P-2",
"party_name": "Service Provider",
"country": "IN",
"level": "engineer",
"hours": "business",
"effort_hours_per_month": 135.0,
"people": 0.9,
"cost_per_month": 2400
}
],
"people": 6.8,
"cost_per_month": 46252,
"by_party": {
"P-2": 46252
},
"by_country": {
"GB": 2212,
"PL": 41640,
"IN": 2400
},
"by_capability": {
"C-14": 1106,
"C-15": 1106,
"C-1": 15142,
"C-2": 11356,
"C-13": 15142,
"C-3": 267,
"C-4": 355,
"C-5": 178,
"C-7": 355,
"C-8": 178,
"C-9": 178,
"C-10": 89,
"C-11": 267,
"C-12": 355,
"C-21": 178
}
}

View File

@@ -0,0 +1,540 @@
{
"parties": [
{
"kind": "customer",
"id": "P-1",
"name": "Customer"
},
{
"kind": "provider",
"name": "Service Provider",
"id": "P-2"
}
],
"teams": [
{
"party": "P-1",
"id": "T-1",
"name": "Platform team",
"type": "platform",
"purpose": "Owns the platform roadmap, designs the networking, and provides explicit approvals for structural changes."
},
{
"purpose": "Provides 24x7 incident response, security monitoring, and general infrastructure operational support.",
"id": "T-2",
"type": "platform",
"name": "Provider Operations",
"party": "P-2"
}
],
"roles": [
{
"team": "T-1",
"country": "GB",
"party": "P-1",
"level": "lead",
"id": "R-1",
"hours": "business",
"name": "Customer Platform Lead"
},
{
"hours": "business",
"team": "T-1",
"level": "senior",
"id": "R-2",
"name": "Customer Platform Engineer",
"country": "GB",
"party": "P-1"
},
{
"party": "P-2",
"country": "GB",
"team": "T-2",
"hours": "business",
"id": "R-3",
"name": "Provider Delivery Lead",
"level": "lead"
},
{
"hours": "24x7",
"country": "PL",
"level": "senior",
"team": "T-2",
"name": "Provider 24x7 SRE",
"party": "P-2",
"id": "R-4"
},
{
"party": "P-2",
"country": "IN",
"name": "Provider Platform Engineer",
"team": "T-2",
"hours": "business",
"id": "R-5",
"level": "engineer"
}
],
"interactions": [
{
"id": "I-1",
"from": "T-1",
"purpose": "The customer platform team consumes infrastructure monitoring and incident response from the provider operations team as a service.",
"mode": "x_as_a_service",
"to": "T-2"
}
],
"measures": [
{
"id": "M-1",
"framework": "dora-metrics",
"measured_by": "C-19",
"target": "Within a day of approval",
"name": "Lead time for changes",
"layer": "outcome",
"outcome": "BO-1"
},
{
"target": "Restored within 4 hours",
"name": "Time to restore service",
"outcome": "BO-2",
"framework": "dora-metrics",
"id": "M-2",
"measured_by": "C-19",
"layer": "outcome"
},
{
"framework": "space-framework",
"name": "Developer satisfaction",
"measured_by": "C-19",
"outcome": "BO-3",
"layer": "guardrail",
"id": "M-3"
},
{
"framework": "devex-framework",
"outcome": "BO-3",
"name": "Developer cognitive load",
"layer": "leading",
"measured_by": "C-19",
"id": "M-4"
}
],
"responsibilities": [
{
"capability": "C-1",
"kind": "accountable",
"role": "R-3",
"id": "RS-1"
},
{
"kind": "responsible",
"capability": "C-1",
"id": "RS-2",
"role": "R-4"
},
{
"kind": "consulted",
"id": "RS-3",
"capability": "C-1",
"role": "R-1"
},
{
"capability": "C-2",
"role": "R-3",
"kind": "accountable",
"id": "RS-4"
},
{
"kind": "responsible",
"capability": "C-2",
"id": "RS-5",
"role": "R-4"
},
{
"capability": "C-2",
"role": "R-1",
"kind": "consulted",
"id": "RS-6"
},
{
"kind": "accountable",
"id": "RS-7",
"capability": "C-3",
"role": "R-3"
},
{
"role": "R-5",
"id": "RS-8",
"capability": "C-3",
"kind": "responsible"
},
{
"kind": "consulted",
"capability": "C-3",
"id": "RS-9",
"role": "R-1"
},
{
"capability": "C-4",
"kind": "accountable",
"id": "RS-10",
"role": "R-3"
},
{
"id": "RS-11",
"capability": "C-4",
"kind": "responsible",
"role": "R-5"
},
{
"capability": "C-4",
"kind": "consulted",
"id": "RS-12",
"role": "R-1"
},
{
"role": "R-1",
"capability": "C-5",
"id": "RS-13",
"kind": "accountable"
},
{
"capability": "C-5",
"kind": "responsible",
"id": "RS-14",
"role": "R-2"
},
{
"capability": "C-5",
"role": "R-5",
"id": "RS-15",
"kind": "responsible"
},
{
"kind": "accountable",
"role": "R-1",
"capability": "C-6",
"id": "RS-16"
},
{
"role": "R-2",
"id": "RS-17",
"capability": "C-6",
"kind": "responsible"
},
{
"kind": "accountable",
"capability": "C-7",
"id": "RS-18",
"role": "R-1"
},
{
"kind": "responsible",
"id": "RS-19",
"capability": "C-7",
"role": "R-5"
},
{
"id": "RS-20",
"kind": "accountable",
"capability": "C-8",
"role": "R-3"
},
{
"capability": "C-8",
"role": "R-5",
"kind": "responsible",
"id": "RS-21"
},
{
"capability": "C-8",
"kind": "consulted",
"id": "RS-22",
"role": "R-1"
},
{
"role": "R-3",
"capability": "C-9",
"kind": "accountable",
"id": "RS-23"
},
{
"kind": "responsible",
"id": "RS-24",
"capability": "C-9",
"role": "R-5"
},
{
"capability": "C-9",
"id": "RS-25",
"role": "R-1",
"kind": "consulted"
},
{
"kind": "accountable",
"capability": "C-10",
"id": "RS-26",
"role": "R-1"
},
{
"kind": "responsible",
"capability": "C-10",
"id": "RS-27",
"role": "R-5"
},
{
"capability": "C-11",
"id": "RS-28",
"kind": "accountable",
"role": "R-3"
},
{
"capability": "C-11",
"kind": "responsible",
"role": "R-5",
"id": "RS-29"
},
{
"role": "R-1",
"capability": "C-11",
"id": "RS-30",
"kind": "consulted"
},
{
"kind": "accountable",
"capability": "C-12",
"id": "RS-31",
"role": "R-3"
},
{
"capability": "C-12",
"id": "RS-32",
"role": "R-5",
"kind": "responsible"
},
{
"kind": "consulted",
"capability": "C-12",
"role": "R-1",
"id": "RS-33"
},
{
"role": "R-3",
"id": "RS-34",
"kind": "accountable",
"capability": "C-13"
},
{
"kind": "responsible",
"id": "RS-35",
"role": "R-4",
"capability": "C-13"
},
{
"role": "R-1",
"kind": "consulted",
"capability": "C-13",
"id": "RS-36"
},
{
"kind": "accountable",
"id": "RS-37",
"role": "R-1",
"capability": "C-14"
},
{
"role": "R-3",
"capability": "C-14",
"id": "RS-38",
"kind": "responsible"
},
{
"role": "R-3",
"id": "RS-39",
"capability": "C-15",
"kind": "accountable"
},
{
"kind": "responsible",
"role": "R-3",
"id": "RS-40",
"capability": "C-15"
},
{
"role": "R-1",
"id": "RS-41",
"capability": "C-15",
"kind": "consulted"
},
{
"kind": "accountable",
"capability": "C-16",
"id": "RS-42",
"role": "R-1"
},
{
"role": "R-1",
"kind": "responsible",
"id": "RS-43",
"capability": "C-16"
},
{
"kind": "accountable",
"role": "R-1",
"id": "RS-44",
"capability": "C-17"
},
{
"kind": "responsible",
"id": "RS-45",
"role": "R-2",
"capability": "C-17"
},
{
"role": "R-1",
"capability": "C-18",
"id": "RS-46",
"kind": "accountable"
},
{
"id": "RS-47",
"kind": "responsible",
"role": "R-2",
"capability": "C-18"
},
{
"role": "R-1",
"id": "RS-48",
"capability": "C-19",
"kind": "accountable"
},
{
"role": "R-2",
"kind": "responsible",
"capability": "C-19",
"id": "RS-49"
},
{
"role": "R-1",
"capability": "C-20",
"id": "RS-50",
"kind": "accountable"
},
{
"id": "RS-51",
"kind": "responsible",
"capability": "C-20",
"role": "R-1"
},
{
"id": "RS-52",
"kind": "accountable",
"capability": "C-21",
"role": "R-3"
},
{
"id": "RS-53",
"role": "R-5",
"kind": "responsible",
"capability": "C-21"
},
{
"role": "R-1",
"id": "RS-54",
"capability": "C-21",
"kind": "consulted"
}
],
"checks": [
{
"condition": "The hub network and interconnect maintains at least 99.9% availability during each month.",
"id": "OC-1",
"source": "K-1",
"on": "C-1"
},
{
"condition": "Audit logs are retained for seven years and cannot be deleted during this period.",
"on": "C-8",
"source": "K-2",
"id": "OC-2"
},
{
"on": "C-7",
"condition": "Encryption keys are rotated at least once every 90 days.",
"source": "K-3",
"id": "OC-3"
},
{
"condition": "A priority 1 fault on any Item is acknowledged within 15 minutes, at any hour.",
"id": "OC-4",
"source": "OR-1",
"on": "C-1"
},
{
"id": "OC-5",
"condition": "Service is restored within 4 hours following a priority 1 incident.",
"on": "C-1",
"source": "OR-2"
},
{
"condition": "An approved change reaches production within one day of approval.",
"on": "C-6",
"source": "OR-4",
"id": "OC-6"
},
{
"source": "OR-5",
"id": "OC-7",
"on": "C-5",
"condition": "Every change to the network requires explicit approval from the customer platform team prior to implementation."
},
{
"source": "OR-6",
"id": "OC-8",
"condition": "A report detailing service levels is delivered to the customer monthly.",
"on": "C-15"
},
{
"on": "C-20",
"source": "OR-8",
"condition": "Platform operations is conducted under a shared service model between the customer and external provider.",
"id": "OC-9"
},
{
"on": "R-1",
"condition": "The Customer Platform Lead role is located in the UK.",
"source": "OR-9",
"id": "OC-10"
},
{
"source": "OR-9",
"on": "R-2",
"condition": "The Customer Platform Engineer role is located in the UK.",
"id": "OC-11"
},
{
"on": "R-3",
"condition": "The Provider Delivery Lead role is located in the UK.",
"source": "OR-9",
"id": "OC-12"
},
{
"id": "OC-13",
"condition": "The Provider 24x7 SRE role is located in Poland.",
"on": "R-4",
"source": "OR-9"
},
{
"id": "OC-14",
"condition": "The Provider Platform Engineer role is located in India.",
"source": "OR-9",
"on": "R-5"
},
{
"source": "OR-6",
"on": "C-14",
"id": "OC-15",
"condition": "A report detailing operational costs is delivered to the customer monthly."
}
]
}

View File

@@ -0,0 +1,149 @@
{
"dry_run": {
"verdict": "pass",
"evidence": "13 of 13 scenario walk-throughs pass."
},
"checks": [
{
"check": "OC-1",
"verdict": "pass",
"evidence": "Capability C-1 is responsible for incident management with 24x7 coverage by the Provider 24x7 SRE role (R-4), which is sufficient to maintain highly available operations by responding to faults around the clock."
},
{
"check": "OC-2",
"evidence": "Capability C-8 manages backup and recovery, validating retention policies for audit logs. It is appropriately staffed during business hours.",
"verdict": "pass"
},
{
"check": "OC-3",
"evidence": "Capability C-7 covers configuration management including tracking key rotation cycles, with the Customer Platform Lead (R-1) accountable and Provider Platform Engineer (R-5) responsible.",
"verdict": "pass"
},
{
"verdict": "pass",
"evidence": "Capability C-1 covers incident management 24x7 with the Provider 24x7 SRE (R-4) responsible, ensuring 15-minute acknowledgement at any hour.",
"check": "OC-4"
},
{
"check": "OC-5",
"verdict": "pass",
"evidence": "Capability C-1 provides 24x7 incident response, ensuring that service is restored within the 4-hour target following a priority 1 incident."
},
{
"verdict": "pass",
"evidence": "Capability C-6 manages release and deployment, with the Customer Platform Engineer (R-2) responsible, ensuring approved changes reach production within a day.",
"check": "OC-6"
},
{
"verdict": "pass",
"evidence": "Capability C-5 manages change enablement, with the Customer Platform Lead (R-1) accountable and engineers responsible, ensuring network changes require explicit approval.",
"check": "OC-7"
},
{
"verdict": "pass",
"check": "OC-8",
"evidence": "Capability C-15 covers service level management to measure SLA achievement and deliver the monthly report, with the Provider Delivery Lead (R-3) accountable and responsible."
},
{
"evidence": "Capability C-20 handles supplier management to ensure shared service model compliance, with the Customer Platform Lead (R-1) accountable and responsible.",
"verdict": "pass",
"check": "OC-9"
},
{
"check": "OC-10",
"verdict": "pass",
"evidence": "The Customer Platform Lead role (R-1) is defined with country 'GB' (UK)."
},
{
"verdict": "pass",
"check": "OC-11",
"evidence": "The Customer Platform Engineer role (R-2) is defined with country 'GB' (UK)."
},
{
"check": "OC-12",
"evidence": "The Provider Delivery Lead role (R-3) is defined with country 'GB' (UK).",
"verdict": "pass"
},
{
"verdict": "pass",
"evidence": "The Provider 24x7 SRE role (R-4) is defined with country 'PL' (Poland).",
"check": "OC-13"
},
{
"check": "OC-14",
"verdict": "pass",
"evidence": "The Provider Platform Engineer role (R-5) is defined with country 'IN' (India)."
},
{
"check": "OC-15",
"evidence": "Capability C-14 covers cost management to compile financial reports on monthly landing zone spend, with the Provider Delivery Lead (R-3) responsible.",
"verdict": "pass"
},
{
"check": "SC-fault-S-1",
"verdict": "pass",
"evidence": "Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
},
{
"check": "SC-change-S-1",
"verdict": "pass",
"evidence": "Hub network and interconnect (S-1) must be changed. Customer Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-2",
"verdict": "pass",
"evidence": "Audit log store (S-2) fails at an hour faults are responded to (24x7). Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
},
{
"check": "SC-change-S-2",
"verdict": "pass",
"evidence": "Audit log store (S-2) must be changed. Customer Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-3",
"verdict": "pass",
"evidence": "Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
},
{
"check": "SC-change-S-3",
"verdict": "pass",
"evidence": "Deployment pipeline (S-3) must be changed. Customer Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-4",
"verdict": "pass",
"evidence": "Encryption keys (S-4) fails at an hour faults are responded to (24x7). Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
},
{
"check": "SC-change-S-4",
"verdict": "pass",
"evidence": "Encryption keys (S-4) must be changed. Customer Platform Engineer makes the change under C-5."
},
{
"check": "SC-condition-K-1",
"verdict": "pass",
"evidence": "Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. Check OC-1 on C-1 keeps it true."
},
{
"check": "SC-condition-K-2",
"verdict": "pass",
"evidence": "Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. Check OC-2 on C-8 keeps it true."
},
{
"check": "SC-condition-K-3",
"verdict": "pass",
"evidence": "Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. Check OC-3 on C-7 keeps it true."
},
{
"check": "SC-party-P-2",
"verdict": "pass",
"evidence": "Service Provider cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
},
{
"check": "SC-budget",
"verdict": "pass",
"evidence": "A month's cost of operating is compared with the budget of 60,000 GBP. The cost is 46,252 GBP, within the budget."
}
],
"proposed_additions": []
}

View File

@@ -0,0 +1,329 @@
[
{
"id": "C-1",
"catalogue": "incident-management",
"serves": [
"OR-1",
"OR-2"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "24x7",
"effort_hours_per_month": 20,
"basis": "Triage of platform alerts and handling an estimated 1-2 major incidents per month."
},
{
"id": "C-2",
"catalogue": "monitoring-and-alerting",
"serves": [
"OR-1",
"OR-3"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "24x7",
"effort_hours_per_month": 24,
"basis": "Continuous watching of alerts and maintaining dashboard configurations across all foundational components."
},
{
"id": "C-3",
"catalogue": "problem-management",
"serves": [
"OR-2",
"OR-3"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 12,
"basis": "Conducting post-mortems and root cause analysis for any significant platform degradation."
},
{
"id": "C-4",
"catalogue": "service-request-fulfilment",
"serves": [
"OR-6"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 15,
"basis": "Handling access requests, log extraction, or ad-hoc platform configuration inquiries from the customer team."
},
{
"id": "C-5",
"catalogue": "change-enablement",
"serves": [
"OR-4"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Reviewing and coordinating hub network modifications requiring customer team approvals."
},
{
"id": "C-6",
"catalogue": "release-and-deployment",
"serves": [
"OR-4"
],
"items": [
"S-1",
"S-3"
],
"hours": "business",
"effort_hours_per_month": 12,
"basis": "Overseeing automated pipeline executions and intervening in any failed pipeline deployments."
},
{
"id": "C-7",
"catalogue": "configuration-management",
"serves": [
"OR-4"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 8,
"basis": "Validating infrastructure-as-code state drifts and ensuring configuration matches approved deployments."
},
{
"id": "C-8",
"catalogue": "backup-and-recovery",
"serves": [
"OR-2"
],
"items": [
"S-2",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 4,
"basis": "Periodic testing of key recovery procedures and verifying log retention accessibility."
},
{
"id": "C-9",
"catalogue": "service-continuity",
"serves": [
"OR-2",
"OR-3"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 8,
"basis": "Quarterly rehearsal of regional failover scenarios amortized monthly."
},
{
"id": "C-10",
"catalogue": "capacity-and-performance",
"serves": [
"OR-3"
],
"items": [
"S-1",
"S-3"
],
"hours": "business",
"effort_hours_per_month": 4,
"basis": "Reviewing hub network interconnect utilization and deployment pipeline throughput."
},
{
"id": "C-11",
"catalogue": "access-management",
"serves": [
"OR-8"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Managing and auditing IAM access limits to ensure the immutability of the audit log store."
},
{
"id": "C-12",
"catalogue": "vulnerability-and-patch-management",
"serves": [
"OR-3"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 16,
"basis": "Routine scanning and applying necessary patches or mitigations to the cloud foundation components."
},
{
"id": "C-13",
"catalogue": "security-monitoring-and-response",
"serves": [
"OR-1",
"OR-8"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "24x7",
"effort_hours_per_month": 24,
"basis": "Monitoring security event signals and investigating potential unauthorized access attempts across all hours."
},
{
"id": "C-14",
"catalogue": "cost-management",
"serves": [
"OR-5"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 6,
"basis": "Reconciling cloud spend against budget and preparing the financial sections of the monthly report."
},
{
"id": "C-15",
"catalogue": "service-level-management",
"serves": [
"OR-5"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 8,
"basis": "Aggregating metrics to produce the monthly reporting package on SLA achievements."
},
{
"id": "C-16",
"catalogue": "platform-product-management",
"serves": [
"OR-6"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 12,
"basis": "Prioritizing the internal platform backlog to address friction reported by the customer engineering team."
},
{
"id": "C-17",
"catalogue": "self-service-and-golden-paths",
"serves": [
"OR-4",
"OR-6"
],
"items": [
"S-3"
],
"hours": "business",
"effort_hours_per_month": 16,
"basis": "Maintaining default pipeline configurations and automating network modification paths for easier customer team adoption."
},
{
"id": "C-18",
"catalogue": "enablement",
"serves": [
"OR-6"
],
"items": [
"S-3"
],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Onboarding the customer platform team to the delivery pipelines and providing guidance on self-service usage."
},
{
"id": "C-19",
"catalogue": "delivery-and-developer-experience-measurement",
"serves": [
"OR-5"
],
"items": [
"S-3"
],
"hours": "business",
"effort_hours_per_month": 8,
"basis": "Measuring deployment frequency, change failure rate, and surveying developer productivity and friction."
},
{
"id": "C-20",
"catalogue": "supplier-management",
"serves": [
"OR-6",
"OR-7"
],
"items": [
"S-1",
"S-2",
"S-3",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 4,
"basis": "Overseeing the shared operational delivery structure and ensuring alignment with location restrictions."
},
{
"id": "C-21",
"catalogue": "regulatory-evidence",
"serves": [
"OR-8",
"OR-9"
],
"items": [
"S-2",
"S-4"
],
"hours": "business",
"effort_hours_per_month": 8,
"basis": "Collecting evidence for 90-day cryptographic key rotations and long-term audit log retention to support DORA alignment."
}
]

View File

@@ -0,0 +1,54 @@
## Capabilities
The following capabilities establish what the operating organisation must be able to execute to satisfy the defined operational requirements.
*(Note: While the attached rate card remains a draft, any costs computed downstream from these capabilities are strictly placeholders.)*
| ID | Capability | Purpose / Why it is needed | Items covered | Serves |
| :--- | :--- | :--- | :--- | :--- |
| **C-1** | Incident management | To restore normal service after a fault and handle Priority 1 incidents round-the-clock. | S-1, S-2, S-3, S-4 | OR-1, OR-2 |
| **C-2** | Monitoring and alerting | To detect platform faults, track 99.9% availability, and trigger instant alerts across 24x7 hours. | S-1, S-2, S-3, S-4 | OR-1, OR-3 |
| **C-3** | Problem management | To perform root cause analysis and prevent the recurrence of high-impact platform incidents. | S-1, S-2, S-3, S-4 | OR-2, OR-3 |
| **C-4** | Service request fulfilment | To manage standard requests and access requests between the shared sourcing teams. | S-1, S-2, S-3, S-4 | OR-6 |
| **C-5** | Change enablement | To review risks and ensure all hub network changes receive customer platform team approval. | S-1, S-2, S-3, S-4 | OR-4 |
| **C-6** | Release and deployment | To execute automated pipelines smoothly and roll back any failing changes. | S-1, S-3 | OR-4 |
| **C-7** | Configuration management | To maintain infrastructure-as-code state accuracy for all network and key configurations. | S-1, S-2, S-3, S-4 | OR-4 |
| **C-8** | Backup and recovery | To ensure data resilience, key backups, and recovery from catastrophic component loss. | S-2, S-4 | OR-2 |
| **C-9** | Service continuity | To rehearse and ensure the platform foundation recovers within 4 hours in disaster scenarios. | S-1, S-2, S-3, S-4 | OR-2, OR-3 |
| **C-10** | Capacity and performance management | To monitor hub network bandwidth and pipeline usage against limits. | S-1, S-3 | OR-3 |
| **C-11** | Access management | To restrict log and key access tightly, preventing unauthorized deletion of audit logs. | S-1, S-2, S-3, S-4 | OR-8 |
| **C-12** | Vulnerability and patch management | To routinely scan for flaws and apply necessary mitigations, protecting platform availability. | S-1, S-2, S-3, S-4 | OR-3 |
| **C-13** | Security monitoring and response | To monitor security incidents 24x7 and rapidly react to malicious events. | S-1, S-2, S-3, S-4 | OR-1, OR-8 |
| **C-14** | Cost management | To track cloud spend against budget and compile the cost segment of the monthly report. | S-1, S-2, S-3, S-4 | OR-5 |
| **C-15** | Service level management | To measure compliance with stated SLAs and package the findings into the monthly customer report. | S-1, S-2, S-3, S-4 | OR-5 |
| **C-16** | Platform product management | To manage the foundation as a product, prioritizing improvements based on developer feedback. | S-1, S-2, S-3, S-4 | OR-6 |
| **C-17** | Self-service and golden paths | To offer default, streamlined pipeline deployment paths for easier developer adoption. | S-3 | OR-4, OR-6 |
| **C-18** | Enablement | To assist the customer team with using the foundational deployment pipelines via pairing and training. | S-3 | OR-6 |
| **C-19** | Delivery and developer experience measurement | To report on metrics such as deployment speed and team satisfaction, supporting continuous improvement. | S-3 | OR-5 |
| **C-20** | Supplier management | To govern the multi-location external provider and ensure location constraints are enforced. | S-1, S-2, S-3, S-4 | OR-6, OR-7 |
| **C-21** | Regulatory evidence and reporting | To collect audit evidence of 90-day key rotations and 7-year log retention for compliance alignment. | S-2, S-4 | OR-8, OR-9 |
## Sources
The capability catalogue draws heavily on prominent industry frameworks.
*(Note: All sources referenced in this capability model are currently flagged as **unverified** because they are drawn from the catalogue's register, whose status indicates they were drafted from general knowledge. They have not been independently certified. The capability catalogue draws on them and promises nothing regarding compliance.)*
* **ITIL 4** (PeopleCert, version 4): Incident management practice, Monitoring and event management practice, Problem management practice, Service request management practice, Change enablement practice, Release management and Deployment management practices, Service configuration management practice, Service continuity management practice, Capacity and performance management practice, Supplier management practice, Service level management practice.
* **Site Reliability Engineering: How Google Runs Production Systems** (Google / O'Reilly, 2016): Managing Incidents, Monitoring Distributed Systems, Postmortem Culture: Learning from Failure, Release Engineering, Service Level Objectives.
* **ISO/IEC 20000-1** (ISO/IEC, 2018): Incident management, Service request management, Change management, Service continuity management, Capacity management, Service level management, Supplier management.
* **Regulation (EU) 2022/2554, the Digital Operational Resilience Act** (European Union, 2022): Article 9, Protection and prevention; Article 10, Detection; Article 11, Response and recovery; Article 12, Backup policies and procedures, restoration and recovery procedures and methods; Article 17, ICT-related incident management process; Article 19, Reporting of major ICT-related incidents; Article 28, General principles on ICT third-party risk.
* **NIST Cybersecurity Framework** (National Institute of Standards and Technology, 2.0): Detect: Continuous Monitoring; Detect: Adverse Event Analysis; Respond: Incident Management; Identify: Asset Management; Recover: Incident Recovery Plan Execution; Protect: Identity Management, Authentication, and Access Control; Protect: Platform Security.
* **ISO/IEC 27001** (ISO/IEC, 2022): Access control, Management of technical vulnerabilities, Information security incident management, Compliance with legal and contractual requirements.
* **FinOps Framework** (FinOps Foundation, 2024): Allocation; Budgeting; Forecasting; Anomaly Management.
* **Team Topologies: Organizing Business and Technology Teams for Fast Flow** (IT Revolution, 2019): Platform team; Thinnest viable platform; X-as-a-Service interaction mode; Enabling team; Facilitating interaction mode.
* **CNCF Platforms White Paper (platform as a product)** (Cloud Native Computing Foundation, 2023): Platform as a product; Measuring platform success; Platform capabilities; Self-service.
* **DevOps Research and Assessment (DORA) software delivery metrics** (Google Cloud, 2023): Change failure rate, Deployment frequency and lead time for changes, Time to restore service.
* **The SPACE of Developer Productivity** (Forsgren et al., ACM Queue, 2021): Satisfaction and well-being; Performance; Activity; Communication and collaboration; Efficiency and flow.
* **DevEx: What Actually Drives Productivity** (Noda et al., ACM Queue, 2023): Feedback loops; Cognitive load; Flow state.
## Assumptions
Since pre-approved execution is enabled, the following assumptions were made regarding capability assignments and requirements:
- Single instances of each capability per catalogue entry are sufficient, rather than splitting capabilities based on differing items. The shared sourcing model's division of duties is expected to be managed later at the Role layer.
- Operational capabilities associated with "delivery-and-developer experience measurement" actively apply due to the business intent to streamline delivery and preserve developer retention. These are adopted to provide transparent progress towards these goals without mandating complex underlying toolchains.

View File

@@ -0,0 +1,234 @@
# Operating model guide: Google Cloud landing zone foundation
## Summary
This guide defines the target operating model for running the Google Cloud Platform landing zone foundation, comprising the hub network and interconnect, audit log store, deployment pipeline, and cryptographic keys, while application workloads deployed onto the foundation remain out of operational scope. Operations are shared between the customer platform team and an external service provider across the United Kingdom, Poland, and India. The customer platform team retains platform product ownership and final approval authority over all network changes, while the external service provider delivers continuous monitoring and rapid fault response alongside pipeline maintenance and enablement.
Operational support and platform availability operate continuously round the clock, with the provider handling fault response across all hours, while change enablement, platform engineering, and governance occur during business hours. Readers should look first at the findings and open questions section to review the unconfirmed operational assumptions and unstated items—including the native operations tooling baseline and workload boundaries—as well as the provisional nature of the draft rate card.
### Key figures
- Operated: 4 Items, with 3 Conditions to keep true.
- Faults responded to: 24x7 hours.
- Capabilities: 21.
- People: 11.0. Cost a month: 44,720 GBP, from rate card version `draft-2026-10-13` (placeholder prices: an illustration).
- Scenario walk-throughs: 13 of 13 pass.
- Business outcomes: 3, 3 shown by a Measure.
- Findings for whoever owns the design: 0.
## Business outcomes
**BO-1: New payment products reach customers in weeks rather than months.** Target: A change reaches production within a day of approval..
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Deployment frequency | outcome | dora-metrics | A change reaches production within a day of approval. | Delivery and developer experience measurement | Operations Lead |
**BO-2: Payments are never unavailable for long.** Target: Restored within 4 hours..
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Time to restore service | outcome | dora-metrics | Restored within 4 hours. | Delivery and developer experience measurement | Operations Lead |
**BO-3: We keep the platform engineers we hire.**
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Satisfaction and well-being | guardrail | space-framework | | Delivery and developer experience measurement | Operations Lead |
| Friction and cognitive load | leading | devex-framework | | Delivery and developer experience measurement | Operations Lead |
## What is operated
| Item | What it is | Kind | Product | From |
| --- | --- | --- | --- | --- |
| S-1 | Hub network and interconnect | network | Cloud Interconnect | |
| S-2 | Audit log store | storage | Cloud Storage | |
| S-3 | Deployment pipeline | pipeline | Cloud Build | |
| S-4 | Encryption keys | keys | Cloud KMS | |
What must be kept true while it is run:
| Condition | On | What must hold | From |
| --- | --- | --- | --- |
| K-1 | S-1 | The platform is available at least 99.9% of each month. | |
| K-2 | S-2 | Audit logs cannot be deleted for seven years. | |
| K-3 | S-4 | Encryption keys are rotated every 90 days. | |
## Operational requirements
| Requirement | Kind | What must be achieved | From |
| --- | --- | --- | --- |
| OR-1 | service_level | A Priority 1 fault on any landing zone component is acknowledged and responded to within 15 minutes, at any hour (24x7). | service_levels.priority_1_response_minutes, operations.support_hours |
| OR-2 | service_level | Normal platform operations are restored within 4 hours of a Priority 1 incident occurring. | service_levels.recovery_time_hours |
| OR-3 | service_level | The platform foundation maintains an operational availability of at least 99.9% across all hours (24x7) of each calendar month. | K-1, operations.availability_hours |
| OR-4 | process | Every change to the hub network requires customer platform team approval prior to deployment. | REQ-01 |
| OR-5 | process | A reporting package detailing achieved service levels and operational costs is delivered to the customer on a monthly basis. | REQ-02 |
| OR-6 | organisation | Platform foundation operations are delivered under a shared sourcing model between the customer and an external service provider. | sourcing.model |
| OR-7 | organisation | Operational services are delivered exclusively from the United Kingdom, Poland, and India. | sourcing.delivery_countries |
| OR-8 | compliance | Audit logs stored in the audit log store cannot be deleted and are retained for at least seven years. | K-2 |
| OR-9 | compliance | Cryptographic encryption keys are rotated at least once every 90 days. | K-3 |
## Capabilities
| Capability | What it is | Serves | Covers | Hours | Effort a month |
| --- | --- | --- | --- | --- | --- |
| C-1 | Incident management | OR-1, OR-2 | S-1, S-2, S-3, S-4 | 24x7 | 20 h |
| C-2 | Monitoring and alerting | OR-1, OR-3 | S-1, S-2, S-3, S-4 | 24x7 | 24 h |
| C-3 | Problem management | OR-2, OR-3 | S-1, S-2, S-3, S-4 | business | 12 h |
| C-4 | Service request fulfilment | OR-6 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-5 | Change enablement | OR-4 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-6 | Release and deployment | OR-4 | S-1, S-3 | business | 12 h |
| C-7 | Configuration management | OR-4 | S-1, S-2, S-3, S-4 | business | 8 h |
| C-8 | Backup and recovery | OR-2 | S-2, S-4 | business | 4 h |
| C-9 | Service continuity | OR-2, OR-3 | S-1, S-2, S-3, S-4 | business | 8 h |
| C-10 | Capacity and performance management | OR-3 | S-1, S-3 | business | 4 h |
| C-11 | Access management | OR-8 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-12 | Vulnerability and patch management | OR-3 | S-1, S-2, S-3, S-4 | business | 16 h |
| C-13 | Security monitoring and response | OR-1, OR-8 | S-1, S-2, S-3, S-4 | 24x7 | 24 h |
| C-14 | Cost management | OR-5 | S-1, S-2, S-3, S-4 | business | 6 h |
| C-15 | Service level management | OR-5 | S-1, S-2, S-3, S-4 | business | 8 h |
| C-16 | Platform product management | OR-6 | S-1, S-2, S-3, S-4 | business | 12 h |
| C-17 | Self-service and golden paths | OR-4, OR-6 | S-3 | business | 16 h |
| C-18 | Enablement | OR-6 | S-3 | business | 10 h |
| C-19 | Delivery and developer experience measurement | OR-5 | S-3 | business | 8 h |
| C-20 | Supplier management | OR-6, OR-7 | S-1, S-2, S-3, S-4 | business | 4 h |
| C-21 | Regulatory evidence and reporting | OR-8, OR-9 | S-2, S-4 | business | 8 h |
## Who does what
| Role | Party | Country | Level | Hours |
| --- | --- | --- | --- | --- |
| Platform Lead | Customer platform team (customer) | GB | lead | business |
| Platform Engineer | Customer platform team (customer) | GB | engineer | business |
| Operations Lead | External service provider (provider) | PL | lead | business |
| Operations Engineer | External service provider (provider) | IN | engineer | 24x7 |
| Security Operations Engineer | External service provider (provider) | IN | senior | 24x7 |
| Senior SRE | External service provider (provider) | IN | senior | business |
| Enablement Engineer | External service provider (provider) | IN | senior | business |
The teams, as Team Topologies names their kinds:
| Team | Kind | Party | Roles | Purpose |
| --- | --- | --- | --- | --- |
| Platform team | platform | Customer platform team | Platform Lead, Platform Engineer | Customer platform foundation ownership |
| Shared operations | platform | External service provider | Operations Lead, Operations Engineer, Security Operations Engineer, Senior SRE | Shared operational delivery of platform foundations |
| Enablement team | enabling | External service provider | Enablement Engineer | Facilitating adoption of pipelines |
How the teams work together:
| From | To | Mode | Until | Purpose |
| --- | --- | --- | --- | --- |
| Platform team | Shared operations | x-as-a-service | | Customer platform team consumes shared operational services and platforms provided by the external provider. |
| Enablement team | Platform team | facilitating | Adoption of foundational pipelines is complete and customer team is self-sufficient. | Provider enablement team assists the customer with adopting foundational deployment pipelines. |
| Capability | Platform Lead | Platform Engineer | Operations Lead | Operations Engineer | Security Operations Engineer | Senior SRE | Enablement Engineer |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Incident management (C-1) | | C | A | R | | | |
| Monitoring and alerting (C-2) | | C | A | R | | | |
| Problem management (C-3) | | C | A | | | R | |
| Service request fulfilment (C-4) | | C | A | R | | | |
| Change enablement (C-5) | A | R | | | | C | |
| Release and deployment (C-6) | | C | A | | | R | |
| Configuration management (C-7) | | C | A | | | R | |
| Backup and recovery (C-8) | | C | A | | | R | |
| Service continuity (C-9) | | C | A | | | R | |
| Capacity and performance management (C-10) | | C | A | | | R | |
| Access management (C-11) | | C | A | | R | | |
| Vulnerability and patch management (C-12) | | C | A | | | R | |
| Security monitoring and response (C-13) | | C | A | | R | | |
| Cost management (C-14) | C | | A | | | R | |
| Service level management (C-15) | C | | A | | | R | |
| Platform product management (C-16) | A/R | | | | | | |
| Self-service and golden paths (C-17) | | C | A | | | R | |
| Enablement (C-18) | | C | A | | | | R |
| Delivery and developer experience measurement (C-19) | C | | A | | | R | |
| Supplier management (C-20) | A/R | | | | | | |
| Regulatory evidence and reporting (C-21) | | C | A | | | R | |
A accountable, R responsible, C consulted, I informed.
## Staffing and cost
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Platform Lead | Customer platform team | GB | lead | business | 16.0 h | 0.1 | not priced |
| Platform Engineer | Customer platform team | GB | engineer | business | 10.0 h | 0.1 | not priced |
| Operations Lead | External service provider | PL | lead | business | 0.0 h | 0.0 | 0 GBP |
| Operations Engineer | External service provider | IN | engineer | 24x7 | 59.0 h | 5.0 | 17,034 GBP |
| Security Operations Engineer | External service provider | IN | senior | 24x7 | 34.0 h | 5.0 | 24,605 GBP |
| Senior SRE | External service provider | IN | senior | business | 110.0 h | 0.7 | 2,824 GBP |
| Enablement Engineer | External service provider | IN | senior | business | 10.0 h | 0.1 | 257 GBP |
11.0 people in all. Cost a month: 44,720 GBP.
The monthly budget is 60,000 GBP: this is within it.
Worked from rate card `rate-card`, version `draft-2026-10-13`. **Its figures are placeholders: no price has been set, and this cost is an illustration.**
Converted from USD at 0.79, a rate set on 2026-10-13.
The customer's own staff are counted and not priced. A Role that covers hours wider than a working day is never smaller than the team that can cover them.
## Validation
| Check | What must hold | Verdict | Evidence |
| --- | --- | --- | --- |
| OC-1 | A Priority 1 fault on the platform is acknowledged and responded to within 15 minutes, at any hour. | pass | Capability C-1 covers incident management and operates 24x7. Role R-4 (Operations Engineer) is responsible and operates 24x7. |
| OC-2 | Normal platform operations are restored within 4 hours of a Priority 1 incident occurring. | pass | Capability C-1 operates 24x7 and responds to incidents. |
| OC-3 | The hub network (S-1) is monitored to verify it maintains at least 99.9% availability. | pass | Capability C-2 covers monitoring and operates 24x7, with Role R-4 responsible. The operating model configures native Google Cloud monitoring tools to fulfill this. |
| OC-4 | Changes to the hub network (S-1) are blocked unless approved by the customer platform team. | pass | Capability C-5 covers change enablement. Role R-1 (Platform Lead from the customer team) is accountable and Role R-2 (Platform Engineer from the customer team) is responsible, giving the customer final approval. |
| OC-5 | A reporting package detailing achieved service levels and operational costs is delivered to the customer monthly. | pass | Capability C-15 covers service level management. Role R-6 (Senior SRE) is responsible for producing the monthly reporting package. |
| OC-6 | Platform foundation operations are governed under a shared sourcing model. | pass | Capability C-20 covers supplier management to govern the shared sourcing model. Role R-1 (Platform Lead) is accountable and responsible. |
| OC-7 | Access controls prevent audit logs in the audit log store (S-2) from being deleted for at least seven years. | pass | Capability C-11 covers access management. Role R-5 (Security Operations Engineer) is responsible. |
| OC-8 | Evidence is collected to demonstrate cryptographic encryption keys (S-4) are rotated at least once every 90 days. | pass | Capability C-21 covers regulatory evidence collection. Role R-6 (Senior SRE) is responsible. |
| OC-9 | The Operations Lead role sits in Poland (PL). | pass | Role R-3 (Operations Lead) is defined with country 'PL' (Poland). |
| OC-10 | The Operations Engineer role sits in India (IN). | pass | Role R-4 (Operations Engineer) is defined with country 'IN' (India). |
| OC-11 | The Security Operations Engineer role sits in India (IN). | pass | Role R-5 (Security Operations Engineer) is defined with country 'IN' (India). |
| OC-12 | The Senior SRE role sits in India (IN). | pass | Role R-6 (Senior SRE) is defined with country 'IN' (India). |
| OC-13 | The Enablement Engineer role sits in India (IN). | pass | Role R-7 (Enablement Engineer) is defined with country 'IN' (India). |
| OC-14 | The Platform Lead role sits in the United Kingdom (GB). | pass | Role R-1 (Platform Lead) is defined with country 'GB' (United Kingdom). |
| OC-15 | The Platform Engineer role sits in the United Kingdom (GB). | pass | Role R-2 (Platform Engineer) is defined with country 'GB' (United Kingdom). |
Each scenario is generated from the operating model and traced through it by code.
| Scenario | Result | Path |
| --- | --- | --- |
| Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Hub network and interconnect (S-1) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Audit log store (S-2) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Audit log store (S-2) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Deployment pipeline (S-3) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Encryption keys (S-4) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Encryption keys (S-4) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. | pass | Check OC-3 on C-2 keeps it true. |
| Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. | pass | Check OC-7 on C-11 keeps it true. |
| Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. | pass | Check OC-8 on C-21 keeps it true. |
| External service provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
| A month's cost of operating is compared with the budget of 60,000 GBP. | pass | The cost is 44,720 GBP, within the budget. |
## Findings and open questions
No findings: the solution provides what operating it needs.
Assumed for the customer, and open to change when they answer:
- `intent.exclusions`: Application workloads deployed onto the platform foundation. Workloads deployed onto the platform foundation are excluded; operations is confined to the landing zone foundation itself.
- `operations.change_process`: Changes go through automated pipelines with peer review; changes affecting the hub network require customer platform team approval prior to release.. Changes follow automated deployment pipelines with peer review, with network changes requiring explicit customer platform team approval per REQ-01.
- `service_management.tooling`: Google Cloud native operations tooling (Cloud Monitoring and Cloud Logging), with no separate service management system.. Defaulting to GCP native operations tooling with no separate ITSM system.
## Sources
The Capabilities are from our own capability catalogue, which draws on these frameworks. It cites them and certifies nothing against them.
- ITIL 4: Incident management practice; Monitoring and event management practice; Problem management practice; Service request management practice; Change enablement practice; Release management and Deployment management practices; Service configuration management practice; Service continuity management practice; Capacity and performance management practice; Service level management practice; Supplier management practice
- Site Reliability Engineering: How Google Runs Production Systems: Managing Incidents; Monitoring Distributed Systems; Postmortem Culture: Learning from Failure; Release Engineering; Service Level Objectives
- ISO/IEC 20000-1: Incident management; Service request management; Change management; Service continuity management; Capacity management; Service level management; Supplier management
- Regulation (EU) 2022/2554, the Digital Operational Resilience Act: Article 17, ICT-related incident management process; Article 10, Detection; Article 12, Backup policies and procedures, restoration and recovery procedures and methods; Article 11, Response and recovery; Article 9, Protection and prevention; Article 28, General principles on ICT third-party risk; Article 19, Reporting of major ICT-related incidents
- NIST Cybersecurity Framework: Detect: Continuous Monitoring; Identify: Asset Management; Recover: Incident Recovery Plan Execution; Protect: Identity Management, Authentication, and Access Control; Protect: Platform Security; Detect: Adverse Event Analysis; Respond: Incident Management
- DevOps Research and Assessment (DORA) software delivery metrics: Change failure rate; Deployment frequency and lead time for changes; Deployment frequency; Lead time for changes; Change failure rate; Time to restore service
- ISO/IEC 27001: Access control; Management of technical vulnerabilities; Information security incident management; Compliance with legal and contractual requirements
- FinOps Framework: Allocation; Budgeting; Forecasting; Anomaly Management
- CNCF Platforms White Paper (platform as a product): Platform as a product; Measuring platform success; Platform capabilities; Self-service; Platform as a product
- Team Topologies: Organizing Business and Technology Teams for Fast Flow: Platform team; Thinnest viable platform; X-as-a-Service interaction mode; Enabling team; Facilitating interaction mode
- The SPACE of Developer Productivity: Satisfaction and well-being; Performance; Activity; Communication and collaboration; Efficiency and flow
- DevEx: What Actually Drives Productivity: Feedback loops; Cognitive load; Flow state
**These references have not been checked against the frameworks by a person.** Treat each as a pointer to where to look.

View File

@@ -0,0 +1,39 @@
## Scope statement
This operating scope covers the ongoing operation of the customer's Google Cloud Platform landing zone platform foundation, comprising the hub network and interconnect, audit log store, deployment pipeline, and encryption keys. Operations are delivered under a shared sourcing model between the customer's platform team and a service provider operating from the United Kingdom, Poland, and India, with the customer platform team retaining approval authority over all network changes. The service is operated continuously with 24x7 availability and 24x7 fault response, targeting a 15-minute response time for Priority 1 incidents and a 4-hour recovery time. All operational costs for this service are stated in British Pounds (GBP). Application workloads and hosted services deployed onto the platform foundation are out of scope for operations.
## Information register
20 stated by the customer, 0 answered in conversation, 3 assumed, 10 unknown, 0 not applicable.
| Field | Value | From |
| --- | --- | --- |
| engagement.kind | platform_foundation | the scope spec |
| intent.statement | We want our landing zone run as a shared service from go-live. A provider should respond to faults at every hour, and our own platform team keeps the final say over changes to the network. | the scope spec |
| intent.requirements | [{"id": "REQ-01", "statement": "Our platform team approves every change to the network."}, {"id": "REQ-02", "statement": "We receive a monthly report of service levels and cost."}] | the scope spec |
| intent.business_outcomes | [{"id": "BO-1", "outcome": "New payment products reach customers in weeks rather than months.", "target": "A change reaches production within a day of approval."}, {"id": "BO-2", "outcome": "Payments | the scope spec |
| solution.cloud_provider | gcp | the scope spec |
| solution.items | [{"id": "S-1", "name": "Hub network and interconnect", "kind": "network", "product": "Cloud Interconnect"}, {"id": "S-2", "name": "Audit log store", "kind": "storage", "product": "Cloud Storage"}, {"i | the scope spec |
| solution.conditions | [{"id": "K-1", "on": ["S-1"], "condition": "The platform is available at least 99.9% of each month."}, {"id": "K-2", "on": ["S-2"], "condition": "Audit logs cannot be deleted for seven years."}, {"id" | the scope spec |
| solution.build.duration_days | 36 | the scope spec |
| operations.support_hours | 24x7 | the scope spec |
| operations.availability_hours | 24x7 | the scope spec |
| sourcing.model | shared | the scope spec |
| sourcing.delivery_countries | ["GB", "PL", "IN"] | the scope spec |
| organisation.existing_teams | [{"name": "Platform team", "party": "customer", "hours": "business", "country": "GB"}] | the scope spec |
| service_levels.priority_1_response_minutes | 15 | the scope spec |
| service_levels.recovery_time_hours | 4 | the scope spec |
| compliance.frameworks | ["DORA"] | the scope spec |
| commercial.currency | GBP | the scope spec |
| commercial.monthly_run_budget | 60000 | the scope spec |
| intent.exclusions | ["Application workloads deployed onto the platform foundation"] | assumed |
| operations.change_process | Changes go through automated pipelines with peer review; changes affecting the hub network require customer platform team approval prior to release. | assumed |
| service_management.tooling | Google Cloud native operations tooling (Cloud Monitoring and Cloud Logging), with no separate service management system. | assumed |
### Assumptions
| Id | Assumption | If it is wrong |
| --- | --- | --- |
| ASSUMP-01 | Assumed intent.exclusions is ['Application workloads deployed onto the platform foundation']. Workloads deployed onto the platform foundation are excluded; operations is confined to the landing zone foundation itself. | Changes which Capabilities are designed. |
| ASSUMP-02 | Assumed operations.change_process is Changes go through automated pipelines with peer review; changes affecting the hub network require customer platform team approval prior to release.. Changes follow automated deployment pipelines with peer review, with network changes requiring explicit customer platform team approval per REQ-01. | Changes change enablement and release. |
| ASSUMP-03 | Assumed service_management.tooling is Google Cloud native operations tooling (Cloud Monitoring and Cloud Logging), with no separate service management system.. Defaulting to GCP native operations tooling with no separate ITSM system. | Changes tooling and the processes written for it. |

View File

@@ -0,0 +1,74 @@
## Operational requirements
The operational requirements define what running the landing zone platform foundation must achieve. Every requirement is traced directly to the customer's stated requirements, binding operating fields, or architectural conditions.
### Service level requirements
- **OR-1**: A Priority 1 fault on any landing zone component is acknowledged and responded to within 15 minutes, at any hour (24x7).
*Source: `service_levels.priority_1_response_minutes`, `operations.support_hours`.*
This ensures round-the-clock fault intake and immediate response capabilities across the entire platform foundation without interruption.
- **OR-2**: Normal platform operations are restored within 4 hours of a Priority 1 incident occurring.
*Source: `service_levels.recovery_time_hours`.*
This establishes the mandatory maximum recovery duration for high-impact platform outages to preserve business continuity.
- **OR-3**: The platform foundation maintains an operational availability of at least 99.9% across all hours (24x7) of each calendar month.
*Source: `K-1`, `operations.availability_hours`.*
This bounds total allowable platform downtime across the hub network and core infrastructure to maintain continuous landing zone operations.
### Process requirements
- **OR-4**: Every change to the hub network requires customer platform team approval prior to deployment.
*Source: `REQ-01`.*
This preserves the customer platform team's governance and authoritative control over network modifications while allowing automated deployment pipelines elsewhere.
- **OR-5**: A reporting package detailing achieved service levels and operational costs is delivered to the customer on a monthly basis.
*Source: `REQ-02`.*
This ensures operational transparency, providing monthly verification of SLA performance and run expenditure.
### Organisation requirements
- **OR-6**: Platform foundation operations are delivered under a shared sourcing model between the customer and an external service provider.
*Source: `sourcing.model`.*
This establishes joint delivery boundaries between the customer's internal engineering team and external partner operations.
- **OR-7**: Operational services are delivered exclusively from the United Kingdom, Poland, and India.
*Source: `sourcing.delivery_countries`.*
This restricts operational execution, personnel locations, and data access to the customer-approved jurisdictions.
### Compliance requirements
- **OR-8**: Audit logs stored in the audit log store cannot be deleted and are retained for at least seven years.
*Source: `K-2`.*
This ensures non-repudiation and regulatory compliance for audit evidence by preventing log deletion across the required 7-year retention period.
- **OR-9**: Cryptographic encryption keys are rotated at least once every 90 days.
*Source: `K-3`.*
This enforces key lifecycle governance to limit cryptographic exposure across the landing zone.
---
## What was not stated
The operating specification leaves several operational parameters either assumed or unknown. If answered differently by the customer, these would alter the operational requirements and downstream target operating model design.
### Assumptions
Because execution is running in pre-approved mode, the following operational assumptions have been adopted from the scoping phase:
| Assumption ID | Field | Assumed Value | Impact if Different |
| :--- | :--- | :--- | :--- |
| **ASSUMP-01** | `intent.exclusions` | Application workloads deployed onto the platform foundation are excluded from operations. | If application workloads were included in scope, operational requirements would need to expand to cover application-level SLAs, deployment support, database maintenance, and tenant runtime monitoring. |
| **ASSUMP-02** | `operations.change_process` | Changes go through automated pipelines with peer review; changes affecting the hub network require customer platform team approval prior to release. | If the change process required manual change advisory board (CAB) reviews for all platform changes, release cadence requirements would slow and change review mechanisms would expand. |
| **ASSUMP-03** | `service_management.tooling` | Google Cloud native operations tooling (Cloud Monitoring and Cloud Logging) is used, with no separate external service management system. | If an enterprise ITSM platform (such as ServiceNow or Jira Service Management) were mandated, additional tooling integration and ticket-routing requirements would apply. |
### Unknowns
The operating spec identifies several unstated fields that remain to be settled:
1. **`operations.monitoring` (Monitoring and alerting baseline)**: The customer has not specified pre-existing monitoring dashboards, synthetic probes, or alert routing mechanisms. If proprietary third-party monitoring or customer-managed SIEM integration is required, specific telemetry ingestion requirements must be established.
2. **`solution.inherited_risks` (Inherited risks and unverified controls)**: Unverified architectural dependencies or single points of failure in Cloud Interconnect or Cloud KMS were not stated. Known single points of failure would require additional failover verification requirements.
3. **`solution.build.customer_owned` (Asset ownership during build)**: Exact boundaries between provider-built landing zone templates and customer-managed components were not explicitly split, which could influence operational handover requirements.
4. **`organisation.headcount_limit` (Staffing constraints)**: Headcount caps were not provided. Operational requirements currently reflect service outcomes and availability rather than headcount caps.
5. **`transition.go_live_date` (Service commencement timeline)**: The cutover date from build to live operations is unknown. A compressed transition window would necessitate specific operational readiness acceptance criteria.
6. **Regulatory framework certification (`compliance.frameworks`)**: While the customer noted DORA as an applicable framework, operational frameworks certify nothing; operational capabilities align with DORA resilience and incident response requirements without making formal certification claims.

View File

@@ -0,0 +1,72 @@
# Target Operating Model
## Design rationale
The target operating model establishes a shared sourcing arrangement to securely and cost-effectively operate the cloud platform foundation, balancing out-of-hours coverage against budget limits.
### Division of work
* **Customer platform team (P-1):** Retains full product ownership, accountability for the platform roadmap, and final approval authority for any changes to the hub network. This ensures the operating model explicitly satisfies the requirement that the internal team retains the final say over the network.
* **External service provider (P-2):** Operates a shared "Platform" team and an "Enabling" team. They hold round-the-clock responsibility for incident response, monitoring, and security telemetry, as well as maintaining the pipeline capabilities. The enablement team interacts with the customer through facilitating modes until the foundational pipelines are successfully adopted.
### Roles and Locations
Due to strict budgetary constraints (£60,000 per month limit), the geographical placement of the provider roles balances coverage, seniority, and cost:
* **Operations Lead (R-3):** Based in Poland (PL) working business hours. This maintains a leadership footprint closer to the customer's UK time zone to facilitate effective governance and escalation.
* **Operations Engineer (R-4) & Security Operations Engineer (R-5):** Based in India (IN) providing 24x7 cover. Operating a 24x7 rota requires a minimum roster of personnel. Placing these roles in India achieves the required round-the-clock incident response (within 15 minutes) while keeping the heavy cost multipliers of 24x7 staffing comfortably within the budget.
* **Senior SRE (R-6) & Enablement Engineer (R-7):** Based in India (IN) during business hours. Initially drafted in Poland, these senior roles were shifted to India to ensure the total monthly run cost remains below the budget.
* **Customer Roles (R-1, R-2):** Based in the UK (GB). Customer headcount does not contribute to the operational run cost.
### Checks and Native Capabilities
Previous versions of this design incorrectly relied on architectural findings for standard operational tasks (e.g., configuring alerts). This has been rectified. The operating model configures native Google Cloud tooling (Cloud Monitoring and Cloud Logging) to fulfill these checks internally without requiring external architectural modifications.
## Assumptions
As this model was generated with pre-approved execution, the following assumptions were made:
* **GCP Tooling:** Operational monitoring, dashboarding, and alerting are entirely achievable within the bounds of the existing native GCP solution components and require no special workarounds.
* **Effort Sizing:** The minimum roster size required to staff a 24x7 position provides sufficient aggregate effort to absorb the estimated monthly capability load without needing additional supplementary FTEs.
* **Client approvals:** The customer has verified that shifting several senior provider engineering roles to India does not violate any unstated data residency or collaboration constraints beyond the explicit list of allowed countries.
## Responsibility matrix
| Capability | Platform Lead | Platform Engineer | Operations Lead | Operations Engineer | Security Operations Engineer | Senior SRE | Enablement Engineer |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Incident management (C-1) | | C | A | R | | | |
| Monitoring and alerting (C-2) | | C | A | R | | | |
| Problem management (C-3) | | C | A | | | R | |
| Service request fulfilment (C-4) | | C | A | R | | | |
| Change enablement (C-5) | A | R | | | | C | |
| Release and deployment (C-6) | | C | A | | | R | |
| Configuration management (C-7) | | C | A | | | R | |
| Backup and recovery (C-8) | | C | A | | | R | |
| Service continuity (C-9) | | C | A | | | R | |
| Capacity and performance management (C-10) | | C | A | | | R | |
| Access management (C-11) | | C | A | | R | | |
| Vulnerability and patch management (C-12) | | C | A | | | R | |
| Security monitoring and response (C-13) | | C | A | | R | | |
| Cost management (C-14) | C | | A | | | R | |
| Service level management (C-15) | C | | A | | | R | |
| Platform product management (C-16) | A/R | | | | | | |
| Self-service and golden paths (C-17) | | C | A | | | R | |
| Enablement (C-18) | | C | A | | | | R |
| Delivery and developer experience measurement (C-19) | C | | A | | | R | |
| Supplier management (C-20) | A/R | | | | | | |
| Regulatory evidence and reporting (C-21) | | C | A | | | R | |
A accountable, R responsible, C consulted, I informed.
## Staffing and cost
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Platform Lead | Customer platform team | GB | lead | business | 16.0 h | 0.1 | not priced |
| Platform Engineer | Customer platform team | GB | engineer | business | 10.0 h | 0.1 | not priced |
| Operations Lead | External service provider | PL | lead | business | 0.0 h | 0.0 | 0 GBP |
| Operations Engineer | External service provider | IN | engineer | 24x7 | 59.0 h | 5.0 | 17,034 GBP |
| Security Operations Engineer | External service provider | IN | senior | 24x7 | 34.0 h | 5.0 | 24,605 GBP |
| Senior SRE | External service provider | IN | senior | business | 110.0 h | 0.7 | 2,824 GBP |
| Enablement Engineer | External service provider | IN | senior | business | 10.0 h | 0.1 | 257 GBP |
11.0 people in all. Cost a month: 44,720 GBP.
The monthly budget is 60,000 GBP: this is within it.
Worked from rate card `rate-card`, version `draft-2026-10-13`. **Its figures are placeholders: no price has been set, and this cost is an illustration.**
Converted from USD at 0.79, a rate set on 2026-10-13.
The customer's own staff are counted and not priced. A Role that covers hours wider than a working day is never smaller than the team that can cover them.

View File

@@ -0,0 +1,50 @@
# Check verdicts
## Passed checks
* **OC-1**: Passed. Capability C-1 covers incident management and operates 24x7. Role R-4 (Operations Engineer) is responsible and operates 24x7.
* **OC-2**: Passed. Capability C-1 operates 24x7 and responds to incidents.
* **OC-3**: Passed. Capability C-2 covers monitoring and operates 24x7, with Role R-4 responsible. The operating model configures native Google Cloud monitoring tools to fulfill this internally.
* **OC-4**: Passed. Capability C-5 covers change enablement. Role R-1 (Platform Lead from the customer team) is accountable and Role R-2 (Platform Engineer from the customer team) is responsible, giving the customer final approval.
* **OC-5**: Passed. Capability C-15 covers service level management. Role R-6 (Senior SRE) is responsible for producing the monthly reporting package.
* **OC-6**: Passed. Capability C-20 covers supplier management to govern the shared sourcing model. Role R-1 (Platform Lead) is accountable and responsible.
* **OC-7**: Passed. Capability C-11 covers access management. Role R-5 (Security Operations Engineer) is responsible.
* **OC-8**: Passed. Capability C-21 covers regulatory evidence collection. Role R-6 (Senior SRE) is responsible.
* **OC-9**: Passed. Role R-3 (Operations Lead) sits in Poland (PL).
* **OC-10**: Passed. Role R-4 (Operations Engineer) sits in India (IN).
* **OC-11**: Passed. Role R-5 (Security Operations Engineer) sits in India (IN).
* **OC-12**: Passed. Role R-6 (Senior SRE) sits in India (IN).
* **OC-13**: Passed. Role R-7 (Enablement Engineer) sits in India (IN).
* **OC-14**: Passed. Role R-1 (Platform Lead) sits in the United Kingdom (GB).
* **OC-15**: Passed. Role R-2 (Platform Engineer) sits in the United Kingdom (GB).
## Failed checks
None.
## Not verifiable checks
None.
## Assumptions
* No further assumptions were made during this validation run.
## Overall verdict
**Pass**: The target operating model successfully meets all operational requirements and conditions.
## Scenario walk-throughs
Each scenario is generated from the operating model and traced through it by code.
| Scenario | Result | Path |
| --- | --- | --- |
| Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Hub network and interconnect (S-1) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Audit log store (S-2) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Audit log store (S-2) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Deployment pipeline (S-3) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Encryption keys (S-4) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Encryption keys (S-4) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. | pass | Check OC-3 on C-2 keeps it true. |
| Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. | pass | Check OC-7 on C-11 keeps it true. |
| Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. | pass | Check OC-8 on C-21 keeps it true. |
| External service provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
| A month's cost of operating is compared with the budget of 60,000 GBP. | pass | The cost is 44,720 GBP, within the budget. |

View File

@@ -0,0 +1,113 @@
{
"customer_case": "bench-landing-zone-shared",
"execution_id": "case-01-landing-zone-shared-r2",
"session_id": "c7cf78e8-2f3b-4f26-bd2f-850de41fe1d6",
"intent_version": 2,
"workflow_request": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.",
"baseline": null,
"overlay_skills": {},
"options": {},
"sources": {},
"scope": {
"status": "BASELINE_LOCKED",
"readiness": {
"supplied": 20,
"answered": 0,
"assumed": 3,
"unknown": 10,
"not_applicable": 0
}
},
"status": "completed",
"warnings": [],
"risks": [],
"assessment": null,
"phases": {
"scoping": "approved",
"operational_requirements": "approved",
"operating_model_design": "approved",
"validation": "approved",
"packaging": "approved"
},
"final_document": "operating-model-guide.md",
"changes": null,
"deliverables": {
"operating_scope": {
"document": "deliverables/operating_scope.md",
"attachments": [
"scope.json",
"scope.yaml"
],
"status": "submitted"
},
"operational_requirements": {
"document": "deliverables/operational_requirements.md",
"attachments": [
"operational-requirements.json"
],
"status": "submitted"
},
"capability_model": {
"document": "deliverables/capability_model.md",
"attachments": [
"capabilities.json"
],
"status": "submitted"
},
"target_operating_model": {
"document": "deliverables/target_operating_model.md",
"attachments": [
"findings.json",
"organisation.mmd",
"staffing.json",
"target-operating-model.json"
],
"status": "submitted"
},
"validation_results": {
"document": "deliverables/validation_results.md",
"attachments": [
"scenarios.json",
"verdicts.json"
],
"status": "submitted"
},
"operating_model_guide": {
"document": "deliverables/operating_model_guide.md",
"attachments": [],
"status": "submitted"
}
},
"files": [
"capabilities.json",
"deliverables/capability_model.md",
"deliverables/operating_model_guide.md",
"deliverables/operating_scope.md",
"deliverables/operational_requirements.md",
"deliverables/target_operating_model.md",
"deliverables/validation_results.md",
"findings.json",
"operating-model-guide.md",
"operational-requirements.json",
"organisation.mmd",
"scenarios.json",
"scope.json",
"scope.yaml",
"staffing.json",
"target-operating-model.json",
"verdicts.json"
],
"staffing": {
"people": 11.0,
"cost_per_month": 44720,
"currency": "GBP",
"rate_card": {
"name": "rate-card",
"version": "draft-2026-10-13",
"draft": true
}
},
"findings": [],
"change_request": null,
"capability_sources_verified": false
}

View File

@@ -0,0 +1,234 @@
# Operating model guide: Google Cloud landing zone foundation
## Summary
This guide defines the target operating model for running the Google Cloud Platform landing zone foundation, comprising the hub network and interconnect, audit log store, deployment pipeline, and cryptographic keys, while application workloads deployed onto the foundation remain out of operational scope. Operations are shared between the customer platform team and an external service provider across the United Kingdom, Poland, and India. The customer platform team retains platform product ownership and final approval authority over all network changes, while the external service provider delivers continuous monitoring and rapid fault response alongside pipeline maintenance and enablement.
Operational support and platform availability operate continuously round the clock, with the provider handling fault response across all hours, while change enablement, platform engineering, and governance occur during business hours. Readers should look first at the findings and open questions section to review the unconfirmed operational assumptions and unstated items—including the native operations tooling baseline and workload boundaries—as well as the provisional nature of the draft rate card.
### Key figures
- Operated: 4 Items, with 3 Conditions to keep true.
- Faults responded to: 24x7 hours.
- Capabilities: 21.
- People: 11.0. Cost a month: 44,720 GBP, from rate card version `draft-2026-10-13` (placeholder prices: an illustration).
- Scenario walk-throughs: 13 of 13 pass.
- Business outcomes: 3, 3 shown by a Measure.
- Findings for whoever owns the design: 0.
## Business outcomes
**BO-1: New payment products reach customers in weeks rather than months.** Target: A change reaches production within a day of approval..
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Deployment frequency | outcome | dora-metrics | A change reaches production within a day of approval. | Delivery and developer experience measurement | Operations Lead |
**BO-2: Payments are never unavailable for long.** Target: Restored within 4 hours..
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Time to restore service | outcome | dora-metrics | Restored within 4 hours. | Delivery and developer experience measurement | Operations Lead |
**BO-3: We keep the platform engineers we hire.**
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Satisfaction and well-being | guardrail | space-framework | | Delivery and developer experience measurement | Operations Lead |
| Friction and cognitive load | leading | devex-framework | | Delivery and developer experience measurement | Operations Lead |
## What is operated
| Item | What it is | Kind | Product | From |
| --- | --- | --- | --- | --- |
| S-1 | Hub network and interconnect | network | Cloud Interconnect | |
| S-2 | Audit log store | storage | Cloud Storage | |
| S-3 | Deployment pipeline | pipeline | Cloud Build | |
| S-4 | Encryption keys | keys | Cloud KMS | |
What must be kept true while it is run:
| Condition | On | What must hold | From |
| --- | --- | --- | --- |
| K-1 | S-1 | The platform is available at least 99.9% of each month. | |
| K-2 | S-2 | Audit logs cannot be deleted for seven years. | |
| K-3 | S-4 | Encryption keys are rotated every 90 days. | |
## Operational requirements
| Requirement | Kind | What must be achieved | From |
| --- | --- | --- | --- |
| OR-1 | service_level | A Priority 1 fault on any landing zone component is acknowledged and responded to within 15 minutes, at any hour (24x7). | service_levels.priority_1_response_minutes, operations.support_hours |
| OR-2 | service_level | Normal platform operations are restored within 4 hours of a Priority 1 incident occurring. | service_levels.recovery_time_hours |
| OR-3 | service_level | The platform foundation maintains an operational availability of at least 99.9% across all hours (24x7) of each calendar month. | K-1, operations.availability_hours |
| OR-4 | process | Every change to the hub network requires customer platform team approval prior to deployment. | REQ-01 |
| OR-5 | process | A reporting package detailing achieved service levels and operational costs is delivered to the customer on a monthly basis. | REQ-02 |
| OR-6 | organisation | Platform foundation operations are delivered under a shared sourcing model between the customer and an external service provider. | sourcing.model |
| OR-7 | organisation | Operational services are delivered exclusively from the United Kingdom, Poland, and India. | sourcing.delivery_countries |
| OR-8 | compliance | Audit logs stored in the audit log store cannot be deleted and are retained for at least seven years. | K-2 |
| OR-9 | compliance | Cryptographic encryption keys are rotated at least once every 90 days. | K-3 |
## Capabilities
| Capability | What it is | Serves | Covers | Hours | Effort a month |
| --- | --- | --- | --- | --- | --- |
| C-1 | Incident management | OR-1, OR-2 | S-1, S-2, S-3, S-4 | 24x7 | 20 h |
| C-2 | Monitoring and alerting | OR-1, OR-3 | S-1, S-2, S-3, S-4 | 24x7 | 24 h |
| C-3 | Problem management | OR-2, OR-3 | S-1, S-2, S-3, S-4 | business | 12 h |
| C-4 | Service request fulfilment | OR-6 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-5 | Change enablement | OR-4 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-6 | Release and deployment | OR-4 | S-1, S-3 | business | 12 h |
| C-7 | Configuration management | OR-4 | S-1, S-2, S-3, S-4 | business | 8 h |
| C-8 | Backup and recovery | OR-2 | S-2, S-4 | business | 4 h |
| C-9 | Service continuity | OR-2, OR-3 | S-1, S-2, S-3, S-4 | business | 8 h |
| C-10 | Capacity and performance management | OR-3 | S-1, S-3 | business | 4 h |
| C-11 | Access management | OR-8 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-12 | Vulnerability and patch management | OR-3 | S-1, S-2, S-3, S-4 | business | 16 h |
| C-13 | Security monitoring and response | OR-1, OR-8 | S-1, S-2, S-3, S-4 | 24x7 | 24 h |
| C-14 | Cost management | OR-5 | S-1, S-2, S-3, S-4 | business | 6 h |
| C-15 | Service level management | OR-5 | S-1, S-2, S-3, S-4 | business | 8 h |
| C-16 | Platform product management | OR-6 | S-1, S-2, S-3, S-4 | business | 12 h |
| C-17 | Self-service and golden paths | OR-4, OR-6 | S-3 | business | 16 h |
| C-18 | Enablement | OR-6 | S-3 | business | 10 h |
| C-19 | Delivery and developer experience measurement | OR-5 | S-3 | business | 8 h |
| C-20 | Supplier management | OR-6, OR-7 | S-1, S-2, S-3, S-4 | business | 4 h |
| C-21 | Regulatory evidence and reporting | OR-8, OR-9 | S-2, S-4 | business | 8 h |
## Who does what
| Role | Party | Country | Level | Hours |
| --- | --- | --- | --- | --- |
| Platform Lead | Customer platform team (customer) | GB | lead | business |
| Platform Engineer | Customer platform team (customer) | GB | engineer | business |
| Operations Lead | External service provider (provider) | PL | lead | business |
| Operations Engineer | External service provider (provider) | IN | engineer | 24x7 |
| Security Operations Engineer | External service provider (provider) | IN | senior | 24x7 |
| Senior SRE | External service provider (provider) | IN | senior | business |
| Enablement Engineer | External service provider (provider) | IN | senior | business |
The teams, as Team Topologies names their kinds:
| Team | Kind | Party | Roles | Purpose |
| --- | --- | --- | --- | --- |
| Platform team | platform | Customer platform team | Platform Lead, Platform Engineer | Customer platform foundation ownership |
| Shared operations | platform | External service provider | Operations Lead, Operations Engineer, Security Operations Engineer, Senior SRE | Shared operational delivery of platform foundations |
| Enablement team | enabling | External service provider | Enablement Engineer | Facilitating adoption of pipelines |
How the teams work together:
| From | To | Mode | Until | Purpose |
| --- | --- | --- | --- | --- |
| Platform team | Shared operations | x-as-a-service | | Customer platform team consumes shared operational services and platforms provided by the external provider. |
| Enablement team | Platform team | facilitating | Adoption of foundational pipelines is complete and customer team is self-sufficient. | Provider enablement team assists the customer with adopting foundational deployment pipelines. |
| Capability | Platform Lead | Platform Engineer | Operations Lead | Operations Engineer | Security Operations Engineer | Senior SRE | Enablement Engineer |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Incident management (C-1) | | C | A | R | | | |
| Monitoring and alerting (C-2) | | C | A | R | | | |
| Problem management (C-3) | | C | A | | | R | |
| Service request fulfilment (C-4) | | C | A | R | | | |
| Change enablement (C-5) | A | R | | | | C | |
| Release and deployment (C-6) | | C | A | | | R | |
| Configuration management (C-7) | | C | A | | | R | |
| Backup and recovery (C-8) | | C | A | | | R | |
| Service continuity (C-9) | | C | A | | | R | |
| Capacity and performance management (C-10) | | C | A | | | R | |
| Access management (C-11) | | C | A | | R | | |
| Vulnerability and patch management (C-12) | | C | A | | | R | |
| Security monitoring and response (C-13) | | C | A | | R | | |
| Cost management (C-14) | C | | A | | | R | |
| Service level management (C-15) | C | | A | | | R | |
| Platform product management (C-16) | A/R | | | | | | |
| Self-service and golden paths (C-17) | | C | A | | | R | |
| Enablement (C-18) | | C | A | | | | R |
| Delivery and developer experience measurement (C-19) | C | | A | | | R | |
| Supplier management (C-20) | A/R | | | | | | |
| Regulatory evidence and reporting (C-21) | | C | A | | | R | |
A accountable, R responsible, C consulted, I informed.
## Staffing and cost
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Platform Lead | Customer platform team | GB | lead | business | 16.0 h | 0.1 | not priced |
| Platform Engineer | Customer platform team | GB | engineer | business | 10.0 h | 0.1 | not priced |
| Operations Lead | External service provider | PL | lead | business | 0.0 h | 0.0 | 0 GBP |
| Operations Engineer | External service provider | IN | engineer | 24x7 | 59.0 h | 5.0 | 17,034 GBP |
| Security Operations Engineer | External service provider | IN | senior | 24x7 | 34.0 h | 5.0 | 24,605 GBP |
| Senior SRE | External service provider | IN | senior | business | 110.0 h | 0.7 | 2,824 GBP |
| Enablement Engineer | External service provider | IN | senior | business | 10.0 h | 0.1 | 257 GBP |
11.0 people in all. Cost a month: 44,720 GBP.
The monthly budget is 60,000 GBP: this is within it.
Worked from rate card `rate-card`, version `draft-2026-10-13`. **Its figures are placeholders: no price has been set, and this cost is an illustration.**
Converted from USD at 0.79, a rate set on 2026-10-13.
The customer's own staff are counted and not priced. A Role that covers hours wider than a working day is never smaller than the team that can cover them.
## Validation
| Check | What must hold | Verdict | Evidence |
| --- | --- | --- | --- |
| OC-1 | A Priority 1 fault on the platform is acknowledged and responded to within 15 minutes, at any hour. | pass | Capability C-1 covers incident management and operates 24x7. Role R-4 (Operations Engineer) is responsible and operates 24x7. |
| OC-2 | Normal platform operations are restored within 4 hours of a Priority 1 incident occurring. | pass | Capability C-1 operates 24x7 and responds to incidents. |
| OC-3 | The hub network (S-1) is monitored to verify it maintains at least 99.9% availability. | pass | Capability C-2 covers monitoring and operates 24x7, with Role R-4 responsible. The operating model configures native Google Cloud monitoring tools to fulfill this. |
| OC-4 | Changes to the hub network (S-1) are blocked unless approved by the customer platform team. | pass | Capability C-5 covers change enablement. Role R-1 (Platform Lead from the customer team) is accountable and Role R-2 (Platform Engineer from the customer team) is responsible, giving the customer final approval. |
| OC-5 | A reporting package detailing achieved service levels and operational costs is delivered to the customer monthly. | pass | Capability C-15 covers service level management. Role R-6 (Senior SRE) is responsible for producing the monthly reporting package. |
| OC-6 | Platform foundation operations are governed under a shared sourcing model. | pass | Capability C-20 covers supplier management to govern the shared sourcing model. Role R-1 (Platform Lead) is accountable and responsible. |
| OC-7 | Access controls prevent audit logs in the audit log store (S-2) from being deleted for at least seven years. | pass | Capability C-11 covers access management. Role R-5 (Security Operations Engineer) is responsible. |
| OC-8 | Evidence is collected to demonstrate cryptographic encryption keys (S-4) are rotated at least once every 90 days. | pass | Capability C-21 covers regulatory evidence collection. Role R-6 (Senior SRE) is responsible. |
| OC-9 | The Operations Lead role sits in Poland (PL). | pass | Role R-3 (Operations Lead) is defined with country 'PL' (Poland). |
| OC-10 | The Operations Engineer role sits in India (IN). | pass | Role R-4 (Operations Engineer) is defined with country 'IN' (India). |
| OC-11 | The Security Operations Engineer role sits in India (IN). | pass | Role R-5 (Security Operations Engineer) is defined with country 'IN' (India). |
| OC-12 | The Senior SRE role sits in India (IN). | pass | Role R-6 (Senior SRE) is defined with country 'IN' (India). |
| OC-13 | The Enablement Engineer role sits in India (IN). | pass | Role R-7 (Enablement Engineer) is defined with country 'IN' (India). |
| OC-14 | The Platform Lead role sits in the United Kingdom (GB). | pass | Role R-1 (Platform Lead) is defined with country 'GB' (United Kingdom). |
| OC-15 | The Platform Engineer role sits in the United Kingdom (GB). | pass | Role R-2 (Platform Engineer) is defined with country 'GB' (United Kingdom). |
Each scenario is generated from the operating model and traced through it by code.
| Scenario | Result | Path |
| --- | --- | --- |
| Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Hub network and interconnect (S-1) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Audit log store (S-2) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Audit log store (S-2) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Deployment pipeline (S-3) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Encryption keys (S-4) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Encryption keys (S-4) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. | pass | Check OC-3 on C-2 keeps it true. |
| Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. | pass | Check OC-7 on C-11 keeps it true. |
| Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. | pass | Check OC-8 on C-21 keeps it true. |
| External service provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
| A month's cost of operating is compared with the budget of 60,000 GBP. | pass | The cost is 44,720 GBP, within the budget. |
## Findings and open questions
No findings: the solution provides what operating it needs.
Assumed for the customer, and open to change when they answer:
- `intent.exclusions`: Application workloads deployed onto the platform foundation. Workloads deployed onto the platform foundation are excluded; operations is confined to the landing zone foundation itself.
- `operations.change_process`: Changes go through automated pipelines with peer review; changes affecting the hub network require customer platform team approval prior to release.. Changes follow automated deployment pipelines with peer review, with network changes requiring explicit customer platform team approval per REQ-01.
- `service_management.tooling`: Google Cloud native operations tooling (Cloud Monitoring and Cloud Logging), with no separate service management system.. Defaulting to GCP native operations tooling with no separate ITSM system.
## Sources
The Capabilities are from our own capability catalogue, which draws on these frameworks. It cites them and certifies nothing against them.
- ITIL 4: Incident management practice; Monitoring and event management practice; Problem management practice; Service request management practice; Change enablement practice; Release management and Deployment management practices; Service configuration management practice; Service continuity management practice; Capacity and performance management practice; Service level management practice; Supplier management practice
- Site Reliability Engineering: How Google Runs Production Systems: Managing Incidents; Monitoring Distributed Systems; Postmortem Culture: Learning from Failure; Release Engineering; Service Level Objectives
- ISO/IEC 20000-1: Incident management; Service request management; Change management; Service continuity management; Capacity management; Service level management; Supplier management
- Regulation (EU) 2022/2554, the Digital Operational Resilience Act: Article 17, ICT-related incident management process; Article 10, Detection; Article 12, Backup policies and procedures, restoration and recovery procedures and methods; Article 11, Response and recovery; Article 9, Protection and prevention; Article 28, General principles on ICT third-party risk; Article 19, Reporting of major ICT-related incidents
- NIST Cybersecurity Framework: Detect: Continuous Monitoring; Identify: Asset Management; Recover: Incident Recovery Plan Execution; Protect: Identity Management, Authentication, and Access Control; Protect: Platform Security; Detect: Adverse Event Analysis; Respond: Incident Management
- DevOps Research and Assessment (DORA) software delivery metrics: Change failure rate; Deployment frequency and lead time for changes; Deployment frequency; Lead time for changes; Change failure rate; Time to restore service
- ISO/IEC 27001: Access control; Management of technical vulnerabilities; Information security incident management; Compliance with legal and contractual requirements
- FinOps Framework: Allocation; Budgeting; Forecasting; Anomaly Management
- CNCF Platforms White Paper (platform as a product): Platform as a product; Measuring platform success; Platform capabilities; Self-service; Platform as a product
- Team Topologies: Organizing Business and Technology Teams for Fast Flow: Platform team; Thinnest viable platform; X-as-a-Service interaction mode; Enabling team; Facilitating interaction mode
- The SPACE of Developer Productivity: Satisfaction and well-being; Performance; Activity; Communication and collaboration; Efficiency and flow
- DevEx: What Actually Drives Productivity: Feedback loops; Cognitive load; Flow state
**These references have not been checked against the frameworks by a person.** Treat each as a pointer to where to look.

View File

@@ -0,0 +1,76 @@
[
{
"id": "OR-1",
"kind": "service_level",
"statement": "A Priority 1 fault on any landing zone component is acknowledged and responded to within 15 minutes, at any hour (24x7).",
"source": [
"service_levels.priority_1_response_minutes",
"operations.support_hours"
]
},
{
"id": "OR-2",
"kind": "service_level",
"statement": "Normal platform operations are restored within 4 hours of a Priority 1 incident occurring.",
"source": [
"service_levels.recovery_time_hours"
]
},
{
"id": "OR-3",
"kind": "service_level",
"statement": "The platform foundation maintains an operational availability of at least 99.9% across all hours (24x7) of each calendar month.",
"source": [
"K-1",
"operations.availability_hours"
]
},
{
"id": "OR-4",
"kind": "process",
"statement": "Every change to the hub network requires customer platform team approval prior to deployment.",
"source": [
"REQ-01"
]
},
{
"id": "OR-5",
"kind": "process",
"statement": "A reporting package detailing achieved service levels and operational costs is delivered to the customer on a monthly basis.",
"source": [
"REQ-02"
]
},
{
"id": "OR-6",
"kind": "organisation",
"statement": "Platform foundation operations are delivered under a shared sourcing model between the customer and an external service provider.",
"source": [
"sourcing.model"
]
},
{
"id": "OR-7",
"kind": "organisation",
"statement": "Operational services are delivered exclusively from the United Kingdom, Poland, and India.",
"source": [
"sourcing.delivery_countries"
]
},
{
"id": "OR-8",
"kind": "compliance",
"statement": "Audit logs stored in the audit log store cannot be deleted and are retained for at least seven years.",
"source": [
"K-2"
]
},
{
"id": "OR-9",
"kind": "compliance",
"statement": "Cryptographic encryption keys are rotated at least once every 90 days.",
"source": [
"K-3"
]
}
]

View File

@@ -0,0 +1,20 @@
flowchart TB
subgraph P_1["Customer platform team (customer)"]
subgraph T_1["Platform team (platform team)"]
R_1["Platform Lead<br/>GB, lead, business"]
R_2["Platform Engineer<br/>GB, engineer, business"]
end
end
subgraph P_2["External service provider (provider)"]
subgraph T_2["Shared operations (platform team)"]
R_3["Operations Lead<br/>PL, lead, business"]
R_4["Operations Engineer<br/>IN, engineer, 24x7"]
R_5["Security Operations Engineer<br/>IN, senior, 24x7"]
R_6["Senior SRE<br/>IN, senior, business"]
end
subgraph T_3["Enablement team (enabling team)"]
R_7["Enablement Engineer<br/>IN, senior, business"]
end
end
T_1 -- "x-as-a-service" --> T_2
T_3 -- "facilitating until Adoption of foundational pipelines is complete and customer team is self-sufficient." --> T_1

View File

@@ -0,0 +1,93 @@
[
{
"id": "SC-fault-S-1",
"scenario": "Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7).",
"about": "S-1",
"passes": true,
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"id": "SC-change-S-1",
"scenario": "Hub network and interconnect (S-1) must be changed.",
"about": "S-1",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-2",
"scenario": "Audit log store (S-2) fails at an hour faults are responded to (24x7).",
"about": "S-2",
"passes": true,
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"id": "SC-change-S-2",
"scenario": "Audit log store (S-2) must be changed.",
"about": "S-2",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-3",
"scenario": "Deployment pipeline (S-3) fails at an hour faults are responded to (24x7).",
"about": "S-3",
"passes": true,
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"id": "SC-change-S-3",
"scenario": "Deployment pipeline (S-3) must be changed.",
"about": "S-3",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-4",
"scenario": "Encryption keys (S-4) fails at an hour faults are responded to (24x7).",
"about": "S-4",
"passes": true,
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"id": "SC-change-S-4",
"scenario": "Encryption keys (S-4) must be changed.",
"about": "S-4",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-condition-K-1",
"scenario": "Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month.",
"about": "K-1",
"passes": true,
"path": "Check OC-3 on C-2 keeps it true."
},
{
"id": "SC-condition-K-2",
"scenario": "Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years.",
"about": "K-2",
"passes": true,
"path": "Check OC-7 on C-11 keeps it true."
},
{
"id": "SC-condition-K-3",
"scenario": "Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days.",
"about": "K-3",
"passes": true,
"path": "Check OC-8 on C-21 keeps it true."
},
{
"id": "SC-party-P-2",
"scenario": "External service provider cannot be reached.",
"about": "P-2",
"passes": true,
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
},
{
"id": "SC-budget",
"scenario": "A month's cost of operating is compared with the budget of 60,000 GBP.",
"about": "commercial.monthly_run_budget",
"passes": true,
"path": "The cost is 44,720 GBP, within the budget."
}
]

View File

@@ -0,0 +1,202 @@
{
"kind": "platform_foundation",
"stated": {
"engagement": {
"kind": "platform_foundation"
},
"intent": {
"statement": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.\n",
"requirements": [
{
"id": "REQ-01",
"statement": "Our platform team approves every change to the network."
},
{
"id": "REQ-02",
"statement": "We receive a monthly report of service levels and cost."
}
],
"business_outcomes": [
{
"id": "BO-1",
"outcome": "New payment products reach customers in weeks rather than months.",
"target": "A change reaches production within a day of approval."
},
{
"id": "BO-2",
"outcome": "Payments are never unavailable for long.",
"target": "Restored within 4 hours."
},
{
"id": "BO-3",
"outcome": "We keep the platform engineers we hire."
}
]
},
"solution": {
"cloud_provider": "gcp",
"items": [
{
"id": "S-1",
"name": "Hub network and interconnect",
"kind": "network",
"product": "Cloud Interconnect"
},
{
"id": "S-2",
"name": "Audit log store",
"kind": "storage",
"product": "Cloud Storage"
},
{
"id": "S-3",
"name": "Deployment pipeline",
"kind": "pipeline",
"product": "Cloud Build"
},
{
"id": "S-4",
"name": "Encryption keys",
"kind": "keys",
"product": "Cloud KMS"
}
],
"conditions": [
{
"id": "K-1",
"on": [
"S-1"
],
"condition": "The platform is available at least 99.9% of each month."
},
{
"id": "K-2",
"on": [
"S-2"
],
"condition": "Audit logs cannot be deleted for seven years."
},
{
"id": "K-3",
"on": [
"S-4"
],
"condition": "Encryption keys are rotated every 90 days."
}
],
"build": {
"duration_days": 36
}
},
"operations": {
"support_hours": "24x7",
"availability_hours": "24x7"
},
"sourcing": {
"model": "shared",
"delivery_countries": [
"GB",
"PL",
"IN"
]
},
"organisation": {
"existing_teams": [
{
"name": "Platform team",
"party": "customer",
"hours": "business",
"country": "GB"
}
]
},
"service_levels": {
"priority_1_response_minutes": 15,
"recovery_time_hours": 4
},
"compliance": {
"frameworks": [
"DORA"
]
},
"commercial": {
"currency": "GBP",
"monthly_run_budget": 60000
}
},
"binding": [
"operations.support_hours",
"sourcing.model",
"sourcing.delivery_countries",
"service_levels.priority_1_response_minutes",
"service_levels.recovery_time_hours"
],
"assumed": [
{
"field": "intent.exclusions",
"value": [
"Application workloads deployed onto the platform foundation"
],
"why": "Workloads deployed onto the platform foundation are excluded; operations is confined to the landing zone foundation itself."
},
{
"field": "operations.change_process",
"value": "Changes go through automated pipelines with peer review; changes affecting the hub network require customer platform team approval prior to release.",
"why": "Changes follow automated deployment pipelines with peer review, with network changes requiring explicit customer platform team approval per REQ-01."
},
{
"field": "service_management.tooling",
"value": "Google Cloud native operations tooling (Cloud Monitoring and Cloud Logging), with no separate service management system.",
"why": "Defaulting to GCP native operations tooling with no separate ITSM system."
}
],
"to_decide": [],
"to_ask": [
{
"field": "metadata.client_name",
"prompt": "What is metadata.client_name?",
"severity": "LOW"
},
{
"field": "metadata.author",
"prompt": "What is metadata.author?",
"severity": "LOW"
},
{
"field": "metadata.revision",
"prompt": "What is metadata.revision?",
"severity": "LOW"
},
{
"field": "metadata.source",
"prompt": "What is metadata.source?",
"severity": "LOW"
},
{
"field": "solution.build.customer_owned",
"prompt": "Which parts of the build does the customer or their supplier own?",
"severity": "LOW"
},
{
"field": "solution.inherited_risks",
"prompt": "What is already known to be unverified or at risk in the solution?",
"severity": "LOW"
},
{
"field": "operations.monitoring",
"prompt": "Which monitoring and alerting is already in place or required?",
"severity": "LOW"
},
{
"field": "organisation.headcount_limit",
"prompt": "Is there a limit on the number of people operating this?",
"severity": "LOW"
},
{
"field": "transition.go_live_date",
"prompt": "When must the solution be in operation?",
"severity": "LOW"
}
],
"not_applicable": []
}

View File

@@ -0,0 +1,199 @@
schema_version: 1
metadata:
customer_case: bench-landing-zone-shared
client_name: ask
author: ask
revision: ask
source: ask
status: BASELINE_LOCKED
engagement:
kind: platform_foundation
intent:
statement: 'We want our landing zone run as a shared service from go-live. A provider
should
respond to faults at every hour, and our own platform team keeps the final say
over changes to the network.
'
requirements:
- id: REQ-01
statement: Our platform team approves every change to the network.
- id: REQ-02
statement: We receive a monthly report of service levels and cost.
business_outcomes:
- id: BO-1
outcome: New payment products reach customers in weeks rather than months.
target: A change reaches production within a day of approval.
- id: BO-2
outcome: Payments are never unavailable for long.
target: Restored within 4 hours.
- id: BO-3
outcome: We keep the platform engineers we hire.
exclusions:
- Application workloads deployed onto the platform foundation
solution:
cloud_provider: gcp
items:
- id: S-1
name: Hub network and interconnect
kind: network
product: Cloud Interconnect
- id: S-2
name: Audit log store
kind: storage
product: Cloud Storage
- id: S-3
name: Deployment pipeline
kind: pipeline
product: Cloud Build
- id: S-4
name: Encryption keys
kind: keys
product: Cloud KMS
conditions:
- id: K-1
'on':
- S-1
condition: The platform is available at least 99.9% of each month.
- id: K-2
'on':
- S-2
condition: Audit logs cannot be deleted for seven years.
- id: K-3
'on':
- S-4
condition: Encryption keys are rotated every 90 days.
build:
duration_days: 36
customer_owned: ask
inherited_risks: ask
operations:
support_hours: 24x7
availability_hours: 24x7
change_process: Changes go through automated pipelines with peer review; changes
affecting the hub network require customer platform team approval prior to release.
monitoring: ask
sourcing:
model: shared
delivery_countries:
- GB
- PL
- IN
organisation:
existing_teams:
- name: Platform team
party: customer
hours: business
country: GB
headcount_limit: ask
service_management:
tooling: Google Cloud native operations tooling (Cloud Monitoring and Cloud Logging),
with no separate service management system.
service_levels:
priority_1_response_minutes: 15
recovery_time_hours: 4
compliance:
frameworks:
- DORA
commercial:
currency: GBP
monthly_run_budget: 60000
transition:
go_live_date: ask
run:
pre_approved: true
overlay_skills: ask
inferred_assumptions:
- id: ASSUMP-01
field: intent.exclusions
statement: Assumed intent.exclusions is ['Application workloads deployed onto the
platform foundation']. Workloads deployed onto the platform foundation are excluded;
operations is confined to the landing zone foundation itself.
impact_if_invalid: Changes which Capabilities are designed.
- id: ASSUMP-02
field: operations.change_process
statement: Assumed operations.change_process is Changes go through automated pipelines
with peer review; changes affecting the hub network require customer platform
team approval prior to release.. Changes follow automated deployment pipelines
with peer review, with network changes requiring explicit customer platform team
approval per REQ-01.
impact_if_invalid: Changes change enablement and release.
- id: ASSUMP-03
field: service_management.tooling
statement: Assumed service_management.tooling is Google Cloud native operations
tooling (Cloud Monitoring and Cloud Logging), with no separate service management
system.. Defaulting to GCP native operations tooling with no separate ITSM system.
impact_if_invalid: Changes tooling and the processes written for it.
discovery_gaps:
- field: metadata.client_name
prompt: What is metadata.client_name?
severity: LOW
- field: metadata.author
prompt: What is metadata.author?
severity: LOW
- field: metadata.revision
prompt: What is metadata.revision?
severity: LOW
- field: metadata.source
prompt: What is metadata.source?
severity: LOW
- field: solution.build.customer_owned
prompt: Which parts of the build does the customer or their supplier own?
severity: LOW
- field: solution.inherited_risks
prompt: What is already known to be unverified or at risk in the solution?
severity: LOW
- field: operations.monitoring
prompt: Which monitoring and alerting is already in place or required?
severity: LOW
- field: organisation.headcount_limit
prompt: Is there a limit on the number of people operating this?
severity: LOW
- field: transition.go_live_date
prompt: When must the solution be in operation?
severity: LOW
- field: run.overlay_skills
prompt: Which overlay Skills should this Execution load?
severity: LOW
provenance:
commercial.currency: supplied
commercial.monthly_run_budget: supplied
compliance.frameworks: supplied
engagement.kind: supplied
intent.business_outcomes: supplied
intent.exclusions: assumed
intent.requirements: supplied
intent.statement: supplied
metadata.author: unknown
metadata.client_name: unknown
metadata.customer_case: supplied
metadata.revision: unknown
metadata.source: unknown
operations.availability_hours: supplied
operations.change_process: assumed
operations.monitoring: unknown
operations.support_hours: supplied
organisation.existing_teams: supplied
organisation.headcount_limit: unknown
run.overlay_skills: unknown
run.pre_approved: supplied
service_levels.priority_1_response_minutes: supplied
service_levels.recovery_time_hours: supplied
service_management.tooling: assumed
solution.build.customer_owned: unknown
solution.build.duration_days: supplied
solution.cloud_provider: supplied
solution.conditions: supplied
solution.inherited_risks: unknown
solution.items: supplied
sourcing.delivery_countries: supplied
sourcing.model: supplied
transition.go_live_date: unknown
readiness:
supplied: 20
answered: 0
assumed: 3
unknown: 10
not_applicable: 0

View File

@@ -0,0 +1,128 @@
{
"currency": "GBP",
"rate_card": {
"name": "rate-card",
"version": "draft-2026-10-13",
"draft": true
},
"conversion": {
"from": "USD",
"rate": 0.79,
"as_of": "2026-10-13"
},
"roles": [
{
"role": "R-1",
"name": "Platform Lead",
"party": "P-1",
"party_name": "Customer platform team",
"country": "GB",
"level": "lead",
"hours": "business",
"effort_hours_per_month": 16.0,
"people": 0.1,
"cost_per_month": null
},
{
"role": "R-2",
"name": "Platform Engineer",
"party": "P-1",
"party_name": "Customer platform team",
"country": "GB",
"level": "engineer",
"hours": "business",
"effort_hours_per_month": 10.0,
"people": 0.1,
"cost_per_month": null
},
{
"role": "R-3",
"name": "Operations Lead",
"party": "P-2",
"party_name": "External service provider",
"country": "PL",
"level": "lead",
"hours": "business",
"effort_hours_per_month": 0.0,
"people": 0.0,
"cost_per_month": 0
},
{
"role": "R-4",
"name": "Operations Engineer",
"party": "P-2",
"party_name": "External service provider",
"country": "IN",
"level": "engineer",
"hours": "24x7",
"effort_hours_per_month": 59.0,
"people": 5.0,
"cost_per_month": 17034
},
{
"role": "R-5",
"name": "Security Operations Engineer",
"party": "P-2",
"party_name": "External service provider",
"country": "IN",
"level": "senior",
"hours": "24x7",
"effort_hours_per_month": 34.0,
"people": 5.0,
"cost_per_month": 24605
},
{
"role": "R-6",
"name": "Senior SRE",
"party": "P-2",
"party_name": "External service provider",
"country": "IN",
"level": "senior",
"hours": "business",
"effort_hours_per_month": 110.0,
"people": 0.7,
"cost_per_month": 2824
},
{
"role": "R-7",
"name": "Enablement Engineer",
"party": "P-2",
"party_name": "External service provider",
"country": "IN",
"level": "senior",
"hours": "business",
"effort_hours_per_month": 10.0,
"people": 0.1,
"cost_per_month": 257
}
],
"people": 11.0,
"cost_per_month": 44720,
"by_party": {
"P-2": 44720
},
"by_country": {
"PL": 0,
"IN": 44720
},
"by_capability": {
"C-1": 5774,
"C-2": 6929,
"C-4": 4331,
"C-11": 7237,
"C-13": 17368,
"C-3": 308,
"C-6": 308,
"C-7": 205,
"C-8": 103,
"C-9": 205,
"C-10": 103,
"C-12": 411,
"C-14": 154,
"C-15": 205,
"C-17": 411,
"C-19": 205,
"C-21": 205,
"C-18": 257
}
}

View File

@@ -0,0 +1,615 @@
{
"parties": [
{
"kind": "customer",
"name": "Customer platform team",
"id": "P-1"
},
{
"id": "P-2",
"kind": "provider",
"name": "External service provider"
}
],
"teams": [
{
"purpose": "Customer platform foundation ownership",
"name": "Platform team",
"id": "T-1",
"party": "P-1",
"type": "platform"
},
{
"name": "Shared operations",
"id": "T-2",
"type": "platform",
"purpose": "Shared operational delivery of platform foundations",
"party": "P-2"
},
{
"type": "enabling",
"party": "P-2",
"purpose": "Facilitating adoption of pipelines",
"id": "T-3",
"name": "Enablement team"
}
],
"roles": [
{
"hours": "business",
"party": "P-1",
"country": "GB",
"level": "lead",
"team": "T-1",
"id": "R-1",
"name": "Platform Lead"
},
{
"country": "GB",
"id": "R-2",
"hours": "business",
"team": "T-1",
"name": "Platform Engineer",
"party": "P-1",
"level": "engineer"
},
{
"hours": "business",
"id": "R-3",
"party": "P-2",
"level": "lead",
"country": "PL",
"team": "T-2",
"name": "Operations Lead"
},
{
"hours": "24x7",
"name": "Operations Engineer",
"level": "engineer",
"id": "R-4",
"country": "IN",
"team": "T-2",
"party": "P-2"
},
{
"country": "IN",
"hours": "24x7",
"name": "Security Operations Engineer",
"team": "T-2",
"id": "R-5",
"level": "senior",
"party": "P-2"
},
{
"level": "senior",
"name": "Senior SRE",
"id": "R-6",
"party": "P-2",
"team": "T-2",
"country": "IN",
"hours": "business"
},
{
"id": "R-7",
"name": "Enablement Engineer",
"hours": "business",
"level": "senior",
"team": "T-3",
"country": "IN",
"party": "P-2"
}
],
"interactions": [
{
"mode": "x_as_a_service",
"from": "T-1",
"to": "T-2",
"id": "I-1",
"purpose": "Customer platform team consumes shared operational services and platforms provided by the external provider."
},
{
"to": "T-1",
"from": "T-3",
"mode": "facilitating",
"purpose": "Provider enablement team assists the customer with adopting foundational deployment pipelines.",
"id": "I-2",
"until": "Adoption of foundational pipelines is complete and customer team is self-sufficient."
}
],
"measures": [
{
"layer": "outcome",
"name": "Deployment frequency",
"framework": "dora-metrics",
"outcome": "BO-1",
"measured_by": "C-19",
"id": "M-1",
"target": "A change reaches production within a day of approval."
},
{
"target": "Restored within 4 hours.",
"outcome": "BO-2",
"layer": "outcome",
"measured_by": "C-19",
"framework": "dora-metrics",
"name": "Time to restore service",
"id": "M-2"
},
{
"outcome": "BO-3",
"layer": "guardrail",
"measured_by": "C-19",
"name": "Satisfaction and well-being",
"id": "M-3",
"framework": "space-framework"
},
{
"measured_by": "C-19",
"layer": "leading",
"id": "M-4",
"name": "Friction and cognitive load",
"framework": "devex-framework",
"outcome": "BO-3"
}
],
"responsibilities": [
{
"kind": "accountable",
"capability": "C-1",
"id": "RS-1A",
"role": "R-3"
},
{
"kind": "responsible",
"role": "R-4",
"capability": "C-1",
"id": "RS-1R"
},
{
"role": "R-2",
"kind": "consulted",
"capability": "C-1",
"id": "RS-1C"
},
{
"capability": "C-2",
"kind": "accountable",
"id": "RS-2A",
"role": "R-3"
},
{
"id": "RS-2R",
"capability": "C-2",
"role": "R-4",
"kind": "responsible"
},
{
"kind": "consulted",
"capability": "C-2",
"id": "RS-2C",
"role": "R-2"
},
{
"id": "RS-3A",
"role": "R-3",
"capability": "C-3",
"kind": "accountable"
},
{
"capability": "C-3",
"kind": "responsible",
"id": "RS-3R",
"role": "R-6"
},
{
"role": "R-2",
"id": "RS-3C",
"capability": "C-3",
"kind": "consulted"
},
{
"role": "R-3",
"capability": "C-4",
"id": "RS-4A",
"kind": "accountable"
},
{
"capability": "C-4",
"id": "RS-4R",
"role": "R-4",
"kind": "responsible"
},
{
"capability": "C-4",
"role": "R-2",
"id": "RS-4C",
"kind": "consulted"
},
{
"kind": "accountable",
"capability": "C-5",
"role": "R-1",
"id": "RS-5A"
},
{
"role": "R-2",
"capability": "C-5",
"id": "RS-5R",
"kind": "responsible"
},
{
"role": "R-6",
"capability": "C-5",
"kind": "consulted",
"id": "RS-5C"
},
{
"id": "RS-6A",
"capability": "C-6",
"kind": "accountable",
"role": "R-3"
},
{
"role": "R-6",
"capability": "C-6",
"id": "RS-6R",
"kind": "responsible"
},
{
"capability": "C-6",
"kind": "consulted",
"id": "RS-6C",
"role": "R-2"
},
{
"capability": "C-7",
"role": "R-3",
"id": "RS-7A",
"kind": "accountable"
},
{
"id": "RS-7R",
"kind": "responsible",
"capability": "C-7",
"role": "R-6"
},
{
"capability": "C-7",
"id": "RS-7C",
"kind": "consulted",
"role": "R-2"
},
{
"role": "R-3",
"capability": "C-8",
"id": "RS-8A",
"kind": "accountable"
},
{
"role": "R-6",
"id": "RS-8R",
"kind": "responsible",
"capability": "C-8"
},
{
"role": "R-2",
"capability": "C-8",
"id": "RS-8C",
"kind": "consulted"
},
{
"kind": "accountable",
"capability": "C-9",
"id": "RS-9A",
"role": "R-3"
},
{
"capability": "C-9",
"role": "R-6",
"id": "RS-9R",
"kind": "responsible"
},
{
"kind": "consulted",
"id": "RS-9C",
"role": "R-2",
"capability": "C-9"
},
{
"role": "R-3",
"capability": "C-10",
"id": "RS-10A",
"kind": "accountable"
},
{
"id": "RS-10R",
"role": "R-6",
"capability": "C-10",
"kind": "responsible"
},
{
"role": "R-2",
"id": "RS-10C",
"capability": "C-10",
"kind": "consulted"
},
{
"id": "RS-11A",
"kind": "accountable",
"role": "R-3",
"capability": "C-11"
},
{
"role": "R-5",
"kind": "responsible",
"capability": "C-11",
"id": "RS-11R"
},
{
"kind": "consulted",
"role": "R-2",
"id": "RS-11C",
"capability": "C-11"
},
{
"role": "R-3",
"capability": "C-12",
"id": "RS-12A",
"kind": "accountable"
},
{
"role": "R-6",
"id": "RS-12R",
"kind": "responsible",
"capability": "C-12"
},
{
"capability": "C-12",
"id": "RS-12C",
"kind": "consulted",
"role": "R-2"
},
{
"id": "RS-13A",
"capability": "C-13",
"kind": "accountable",
"role": "R-3"
},
{
"id": "RS-13R",
"role": "R-5",
"kind": "responsible",
"capability": "C-13"
},
{
"id": "RS-13C",
"role": "R-2",
"capability": "C-13",
"kind": "consulted"
},
{
"kind": "accountable",
"id": "RS-14A",
"capability": "C-14",
"role": "R-3"
},
{
"role": "R-6",
"capability": "C-14",
"id": "RS-14R",
"kind": "responsible"
},
{
"kind": "consulted",
"capability": "C-14",
"role": "R-1",
"id": "RS-14C"
},
{
"kind": "accountable",
"role": "R-3",
"capability": "C-15",
"id": "RS-15A"
},
{
"role": "R-6",
"id": "RS-15R",
"kind": "responsible",
"capability": "C-15"
},
{
"kind": "consulted",
"role": "R-1",
"id": "RS-15C",
"capability": "C-15"
},
{
"id": "RS-16A",
"capability": "C-16",
"role": "R-1",
"kind": "accountable"
},
{
"id": "RS-16R",
"kind": "responsible",
"capability": "C-16",
"role": "R-1"
},
{
"id": "RS-17A",
"capability": "C-17",
"kind": "accountable",
"role": "R-3"
},
{
"id": "RS-17R",
"capability": "C-17",
"kind": "responsible",
"role": "R-6"
},
{
"capability": "C-17",
"role": "R-2",
"id": "RS-17C",
"kind": "consulted"
},
{
"capability": "C-18",
"kind": "accountable",
"id": "RS-18A",
"role": "R-3"
},
{
"role": "R-7",
"capability": "C-18",
"id": "RS-18R",
"kind": "responsible"
},
{
"role": "R-2",
"capability": "C-18",
"id": "RS-18C",
"kind": "consulted"
},
{
"role": "R-3",
"capability": "C-19",
"kind": "accountable",
"id": "RS-19A"
},
{
"id": "RS-19R",
"kind": "responsible",
"capability": "C-19",
"role": "R-6"
},
{
"id": "RS-19C",
"kind": "consulted",
"capability": "C-19",
"role": "R-1"
},
{
"id": "RS-20A",
"role": "R-1",
"capability": "C-20",
"kind": "accountable"
},
{
"capability": "C-20",
"id": "RS-20R",
"role": "R-1",
"kind": "responsible"
},
{
"role": "R-3",
"id": "RS-21A",
"capability": "C-21",
"kind": "accountable"
},
{
"id": "RS-21R",
"kind": "responsible",
"capability": "C-21",
"role": "R-6"
},
{
"kind": "consulted",
"capability": "C-21",
"role": "R-2",
"id": "RS-21C"
}
],
"checks": [
{
"on": "C-1",
"id": "OC-1",
"condition": "A Priority 1 fault on the platform is acknowledged and responded to within 15 minutes, at any hour.",
"source": "OR-1"
},
{
"on": "C-1",
"id": "OC-2",
"source": "OR-2",
"condition": "Normal platform operations are restored within 4 hours of a Priority 1 incident occurring."
},
{
"id": "OC-3",
"on": "C-2",
"condition": "The hub network (S-1) is monitored to verify it maintains at least 99.9% availability.",
"source": "K-1"
},
{
"id": "OC-4",
"source": "OR-4",
"condition": "Changes to the hub network (S-1) are blocked unless approved by the customer platform team.",
"on": "C-5"
},
{
"source": "OR-5",
"id": "OC-5",
"on": "C-15",
"condition": "A reporting package detailing achieved service levels and operational costs is delivered to the customer monthly."
},
{
"id": "OC-6",
"condition": "Platform foundation operations are governed under a shared sourcing model.",
"source": "OR-6",
"on": "C-20"
},
{
"source": "K-2",
"condition": "Access controls prevent audit logs in the audit log store (S-2) from being deleted for at least seven years.",
"id": "OC-7",
"on": "C-11"
},
{
"condition": "Evidence is collected to demonstrate cryptographic encryption keys (S-4) are rotated at least once every 90 days.",
"id": "OC-8",
"source": "K-3",
"on": "C-21"
},
{
"condition": "The Operations Lead role sits in Poland (PL).",
"source": "OR-7",
"id": "OC-9",
"on": "R-3"
},
{
"on": "R-4",
"id": "OC-10",
"source": "OR-7",
"condition": "The Operations Engineer role sits in India (IN)."
},
{
"condition": "The Security Operations Engineer role sits in India (IN).",
"source": "OR-7",
"on": "R-5",
"id": "OC-11"
},
{
"condition": "The Senior SRE role sits in India (IN).",
"on": "R-6",
"id": "OC-12",
"source": "OR-7"
},
{
"condition": "The Enablement Engineer role sits in India (IN).",
"source": "OR-7",
"id": "OC-13",
"on": "R-7"
},
{
"condition": "The Platform Lead role sits in the United Kingdom (GB).",
"id": "OC-14",
"on": "R-1",
"source": "OR-7"
},
{
"on": "R-2",
"condition": "The Platform Engineer role sits in the United Kingdom (GB).",
"id": "OC-15",
"source": "OR-7"
}
]
}

View File

@@ -0,0 +1,149 @@
{
"dry_run": {
"verdict": "pass",
"evidence": "13 of 13 scenario walk-throughs pass."
},
"checks": [
{
"check": "OC-1",
"evidence": "Capability C-1 covers incident management and operates 24x7. Role R-4 (Operations Engineer) is responsible and operates 24x7.",
"verdict": "pass"
},
{
"verdict": "pass",
"evidence": "Capability C-1 operates 24x7 and responds to incidents.",
"check": "OC-2"
},
{
"check": "OC-3",
"verdict": "pass",
"evidence": "Capability C-2 covers monitoring and operates 24x7, with Role R-4 responsible. The operating model configures native Google Cloud monitoring tools to fulfill this."
},
{
"check": "OC-4",
"evidence": "Capability C-5 covers change enablement. Role R-1 (Platform Lead from the customer team) is accountable and Role R-2 (Platform Engineer from the customer team) is responsible, giving the customer final approval.",
"verdict": "pass"
},
{
"verdict": "pass",
"evidence": "Capability C-15 covers service level management. Role R-6 (Senior SRE) is responsible for producing the monthly reporting package.",
"check": "OC-5"
},
{
"evidence": "Capability C-20 covers supplier management to govern the shared sourcing model. Role R-1 (Platform Lead) is accountable and responsible.",
"verdict": "pass",
"check": "OC-6"
},
{
"evidence": "Capability C-11 covers access management. Role R-5 (Security Operations Engineer) is responsible.",
"verdict": "pass",
"check": "OC-7"
},
{
"verdict": "pass",
"check": "OC-8",
"evidence": "Capability C-21 covers regulatory evidence collection. Role R-6 (Senior SRE) is responsible."
},
{
"check": "OC-9",
"verdict": "pass",
"evidence": "Role R-3 (Operations Lead) is defined with country 'PL' (Poland)."
},
{
"evidence": "Role R-4 (Operations Engineer) is defined with country 'IN' (India).",
"verdict": "pass",
"check": "OC-10"
},
{
"verdict": "pass",
"evidence": "Role R-5 (Security Operations Engineer) is defined with country 'IN' (India).",
"check": "OC-11"
},
{
"verdict": "pass",
"evidence": "Role R-6 (Senior SRE) is defined with country 'IN' (India).",
"check": "OC-12"
},
{
"check": "OC-13",
"verdict": "pass",
"evidence": "Role R-7 (Enablement Engineer) is defined with country 'IN' (India)."
},
{
"verdict": "pass",
"check": "OC-14",
"evidence": "Role R-1 (Platform Lead) is defined with country 'GB' (United Kingdom)."
},
{
"verdict": "pass",
"evidence": "Role R-2 (Platform Engineer) is defined with country 'GB' (United Kingdom).",
"check": "OC-15"
},
{
"check": "SC-fault-S-1",
"verdict": "pass",
"evidence": "Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"check": "SC-change-S-1",
"verdict": "pass",
"evidence": "Hub network and interconnect (S-1) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-2",
"verdict": "pass",
"evidence": "Audit log store (S-2) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"check": "SC-change-S-2",
"verdict": "pass",
"evidence": "Audit log store (S-2) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-3",
"verdict": "pass",
"evidence": "Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"check": "SC-change-S-3",
"verdict": "pass",
"evidence": "Deployment pipeline (S-3) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-4",
"verdict": "pass",
"evidence": "Encryption keys (S-4) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"check": "SC-change-S-4",
"verdict": "pass",
"evidence": "Encryption keys (S-4) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-condition-K-1",
"verdict": "pass",
"evidence": "Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. Check OC-3 on C-2 keeps it true."
},
{
"check": "SC-condition-K-2",
"verdict": "pass",
"evidence": "Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. Check OC-7 on C-11 keeps it true."
},
{
"check": "SC-condition-K-3",
"verdict": "pass",
"evidence": "Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. Check OC-8 on C-21 keeps it true."
},
{
"check": "SC-party-P-2",
"verdict": "pass",
"evidence": "External service provider cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
},
{
"check": "SC-budget",
"verdict": "pass",
"evidence": "A month's cost of operating is compared with the budget of 60,000 GBP. The cost is 44,720 GBP, within the budget."
}
],
"proposed_additions": []
}

View File

@@ -0,0 +1,191 @@
[
{
"id": "C-1",
"catalogue": "incident-management",
"serves": ["OR-1", "OR-2"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "24x7",
"effort_hours_per_month": 30,
"basis": "Triaging alerts and handling an estimated 2-4 incidents per month across the 4 platform items."
},
{
"id": "C-2",
"catalogue": "monitoring-and-alerting",
"serves": ["OR-1", "OR-3"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "24x7",
"effort_hours_per_month": 20,
"basis": "Maintaining monitoring configurations and tuning alerts for the 4 Items continuously."
},
{
"id": "C-3",
"catalogue": "problem-management",
"serves": ["OR-2"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Conducting root cause analysis and post-incident reviews for major faults."
},
{
"id": "C-4",
"catalogue": "service-request-fulfilment",
"serves": ["OR-6"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Fulfilling routine non-fault requests such as access provisioning or adjusting limits."
},
{
"id": "C-5",
"catalogue": "change-enablement",
"serves": ["OR-4", "OR-10"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Reviewing change requests and coordinating network change approvals with the customer."
},
{
"id": "C-6",
"catalogue": "release-and-deployment",
"serves": ["OR-10"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Overseeing deployment pipelines to ensure approved changes reach production within a day."
},
{
"id": "C-7",
"catalogue": "configuration-management",
"serves": ["OR-8", "OR-9"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 15,
"basis": "Auditing configuration drift, managing key rotation schedules, and maintaining audit log retention settings."
},
{
"id": "C-8",
"catalogue": "backup-and-recovery",
"serves": ["OR-2", "OR-8"],
"items": ["S-2", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Maintaining backups of audit logs and encryption keys, and testing restore procedures."
},
{
"id": "C-9",
"catalogue": "service-continuity",
"serves": ["OR-2", "OR-3"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Planning and periodic rehearsal of disaster recovery procedures for the platform."
},
{
"id": "C-10",
"catalogue": "capacity-and-performance",
"serves": ["OR-3"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Reviewing capacity trends for interconnect and storage to assure 99.9% availability."
},
{
"id": "C-11",
"catalogue": "access-management",
"serves": ["OR-6", "OR-7"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 15,
"basis": "Managing identity and access boundaries between provider and customer in the specified delivery countries."
},
{
"id": "C-12",
"catalogue": "vulnerability-and-patch-management",
"serves": ["OR-9"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 15,
"basis": "Regular patching and vulnerability remediation of the pipeline and infrastructure components."
},
{
"id": "C-13",
"catalogue": "security-monitoring-and-response",
"serves": ["OR-1", "OR-8"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "24x7",
"effort_hours_per_month": 40,
"basis": "Continuous monitoring of security events and continuous analysis of audit logs."
},
{
"id": "C-14",
"catalogue": "cost-management",
"serves": ["OR-5"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Tracking run rate against budget and reporting costs monthly."
},
{
"id": "C-15",
"catalogue": "service-level-management",
"serves": ["OR-3", "OR-5"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Gathering metrics on 99.9% availability and compiling the monthly operational report."
},
{
"id": "C-16",
"catalogue": "platform-product-management",
"serves": ["OR-6"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 15,
"basis": "Managing the platform's roadmap and backlog based on feedback from the customer platform team."
},
{
"id": "C-17",
"catalogue": "self-service-and-golden-paths",
"serves": ["OR-10"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Building automated self-service paths and maintaining fast-flow deployment pipelines."
},
{
"id": "C-18",
"catalogue": "enablement",
"serves": ["OR-10"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 20,
"basis": "Assisting customer engineers with adopting golden paths and best practices."
},
{
"id": "C-19",
"catalogue": "delivery-and-developer-experience-measurement",
"serves": ["OR-10"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Measuring DORA delivery metrics, developer productivity guardrails, and leading flow signals."
},
{
"id": "C-20",
"catalogue": "supplier-management",
"serves": ["OR-6", "OR-7"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Coordinating responsibilities and hand-offs across shared delivery borders and governance locations."
},
{
"id": "C-21",
"catalogue": "regulatory-evidence",
"serves": ["OR-8"],
"items": ["S-1", "S-2", "S-3", "S-4"],
"hours": "business",
"effort_hours_per_month": 10,
"basis": "Gathering and retaining evidence to meet compliance requirements such as EU DORA."
}
]

View File

@@ -0,0 +1,109 @@
# Capability Model
This capability model outlines what the operating organisation must be able to do to meet the operational requirements. It assigns the capabilities from the standard catalogue to specific items of the platform foundation and estimates steady-state effort. Who specifically performs each capability is not decided here.
## Capabilities
| ID | Capability | Coverage (Items) | Operational Requirements | Hours | Monthly Effort (hrs) | Purpose / Need |
|---|---|---|---|---|---|---|
| **C-1** | Incident management | S-1, S-2, S-3, S-4 | OR-1, OR-2 | 24x7 | 30 | Restore degraded services. Needed for fast fault handling. |
| **C-2** | Monitoring and alerting | S-1, S-2, S-3, S-4 | OR-1, OR-3 | 24x7 | 20 | Know the state of components. Needed to detect faults and track uptime. |
| **C-3** | Problem management | S-1, S-2, S-3, S-4 | OR-2 | business | 10 | Find why incidents happen. Needed to prevent major failures. |
| **C-4** | Service request fulfilment | S-1, S-2, S-3, S-4 | OR-6 | business | 20 | Handle user requests. Needed for the shared operating model. |
| **C-5** | Change enablement | S-1, S-2, S-3, S-4 | OR-4, OR-10 | business | 10 | Manage changes. Needed for customer approvals on network changes. |
| **C-6** | Release and deployment | S-1, S-2, S-3, S-4 | OR-10 | business | 20 | Put approved changes into service. Needed to hit the 1-day deployment target. |
| **C-7** | Configuration management | S-1, S-2, S-3, S-4 | OR-8, OR-9 | business | 15 | Track configs. Needed for key rotation and audit log policies. |
| **C-8** | Backup and recovery | S-2, S-4 | OR-2, OR-8 | business | 10 | Keep copies of logs/keys. Needed for recovery and log retention. |
| **C-9** | Service continuity | S-1, S-2, S-3, S-4 | OR-2, OR-3 | business | 10 | Restore services after loss. Needed for the 4-hour recovery SLA. |
| **C-10** | Capacity and performance management | S-1, S-2, S-3, S-4 | OR-3 | business | 10 | Manage limits. Needed for 99.9% uptime. |
| **C-11** | Access management | S-1, S-2, S-3, S-4 | OR-6, OR-7 | business | 15 | Give/revoke access. Needed for cross-country shared model boundaries. |
| **C-12** | Vulnerability and patch management | S-1, S-2, S-3, S-4 | OR-9 | business | 15 | Fix weaknesses. Needed to secure components and rotate keys safely. |
| **C-13** | Security monitoring and response | S-1, S-2, S-3, S-4 | OR-1, OR-8 | 24x7 | 40 | Detect misuse. Needed to protect the audit logs and fast response to events. |
| **C-14** | Cost management | S-1, S-2, S-3, S-4 | OR-5 | business | 10 | Track spend. Needed for the monthly cost report. |
| **C-15** | Service level management | S-1, S-2, S-3, S-4 | OR-3, OR-5 | business | 10 | Measure SLAs. Needed for 99.9% tracking and reporting. |
| **C-16** | Platform product management | S-1, S-2, S-3, S-4 | OR-6 | business | 15 | Manage roadmap based on developer friction. Needed to retain engineers. |
| **C-17** | Self-service and golden paths | S-1, S-2, S-3, S-4 | OR-10 | business | 20 | Automate common tasks. Needed for rapid product delivery. |
| **C-18** | Enablement | S-1, S-2, S-3, S-4 | OR-10 | business | 20 | Help teams adopt the platform. Needed for fast flow of value. |
| **C-19** | Delivery and developer experience measurement | S-1, S-2, S-3, S-4 | OR-10 | business | 10 | Measure flow at all layers. Needed to prove fast change delivery. |
| **C-20** | Supplier management | S-1, S-2, S-3, S-4 | OR-6, OR-7 | business | 10 | Hold suppliers to agreements. Needed for the shared model. |
| **C-21** | Regulatory evidence and reporting | S-1, S-2, S-3, S-4 | OR-8 | business | 10 | Retain compliance evidence. Needed to ensure logs remain undeleted for 7 years. |
*Note: The rate card is currently in draft. Any cost figures or staffing structures derived from these estimations will act as placeholders.*
## Assumptions
As this execution is pre-approved, unknown values were accommodated using standard capability assumptions:
- The customer platform team retains network change approvals, and applications running on the platform are out of scope.
- Changes traverse a deployment pipeline utilizing peer review.
- The cloud provider's native operations tooling is employed in lieu of a separate ITSM system.
- Unspecified bounds around headcount limits, monitoring integrations, or customer build components do not currently restrict operational coverage.
## Sources
The capabilities within this model draw on concepts from several recognized industry frameworks. These are cited as referenced by the catalogue parts below.
*Please note: The capability catalogue draws on these frameworks but claims no official certification or compliance against them. All references provided below are currently **unverified** as documented by the standard catalogue register.*
- **ITIL 4**
- Incident management practice
- Monitoring and event management practice
- Problem management practice
- Service request management practice
- Change enablement practice
- Release management and Deployment management practices
- Service configuration management practice
- Service continuity management practice
- Capacity and performance management practice
- Service level management practice
- Supplier management practice
- **Site Reliability Engineering: How Google Runs Production Systems (Google SRE)**
- Managing Incidents
- Monitoring Distributed Systems
- Postmortem Culture: Learning from Failure
- Release Engineering
- Service Level Objectives
- **ISO/IEC 20000-1**
- Incident management
- Service request management
- Change management
- Service continuity management
- Capacity management
- Service level management
- Supplier management
- **Regulation (EU) 2022/2554, the Digital Operational Resilience Act (EU DORA)**
- Article 9, Protection and prevention
- Article 10, Detection
- Article 11, Response and recovery
- Article 12, Backup policies and procedures, restoration and recovery procedures and methods
- Article 17, ICT-related incident management process
- Article 19, Reporting of major ICT-related incidents
- Article 28, General principles on ICT third-party risk
- **NIST Cybersecurity Framework (NIST CSF 2.0)**
- Identify: Asset Management
- Protect: Identity Management, Authentication, and Access Control
- Protect: Platform Security
- Detect: Continuous Monitoring
- Detect: Adverse Event Analysis; Respond: Incident Management
- Recover: Incident Recovery Plan Execution
- **ISO/IEC 27001**
- Access control
- Management of technical vulnerabilities
- Information security incident management
- Compliance with legal and contractual requirements
- **DevOps Research and Assessment (DORA) software delivery metrics**
- Change failure rate
- Deployment frequency and lead time for changes
- Deployment frequency; Lead time for changes; Change failure rate; Time to restore service
- **FinOps Framework**
- Allocation; Budgeting; Forecasting; Anomaly Management
- **CNCF Platforms White Paper (platform as a product)**
- Platform as a product; Measuring platform success
- Platform capabilities; Self-service
- Platform as a product
- **Team Topologies: Organizing Business and Technology Teams for Fast Flow**
- Platform team; Thinnest viable platform
- X-as-a-Service interaction mode
- Enabling team; Facilitating interaction mode
- **The SPACE of Developer Productivity**
- Satisfaction and well-being; Performance; Activity; Communication and collaboration; Efficiency and flow
- **DevEx: What Actually Drives Productivity**
- Feedback loops; Cognitive load; Flow state

View File

@@ -0,0 +1,237 @@
# Operating model guide: Google Cloud landing zone platform foundation
## Summary
This guide sets out the target operating model for the Google Cloud landing zone platform foundation, covering the hub network and interconnect, audit log store, deployment pipeline, and encryption keys. Operational responsibility is shared between the customer and an external service provider across the United Kingdom, Poland, and India. The customer platform team steers platform product direction, developer flow measurement, and retains approval authority over all network changes, while the service provider operations team runs day-to-day operations, maintenance, and incident management. Fault response and platform availability are maintained around the clock (24x7), while change governance, service continuity, and lifecycle management are conducted during business hours.
Readers should look first at the findings and open questions, particularly the catalogue assumptions regarding cloud-native operations tooling, change pipeline procedures, and the exclusion of workload applications, as well as the draft status of the rate card. All scenario walk-throughs and validation checks pass successfully within the allocated operational budget.
### Key figures
- Operated: 4 Items, with 3 Conditions to keep true.
- Faults responded to: 24x7 hours.
- Capabilities: 21.
- People: 11.4. Cost a month: 47,603 GBP, from rate card version `draft-2026-10-13` (placeholder prices: an illustration).
- Scenario walk-throughs: 13 of 13 pass.
- Business outcomes: 3, 3 shown by a Measure.
- Findings for whoever owns the design: 0.
## Business outcomes
**BO-1: New payment products reach customers in weeks rather than months.** Target: A change reaches production within a day of approval..
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Deployment frequency | outcome | dora-metrics | A change reaches production within a day of approval. | Delivery and developer experience measurement | Platform Product Manager |
| Friction and cognitive load | leading | devex-framework | | Delivery and developer experience measurement | Platform Product Manager |
**BO-2: Payments are never unavailable for long.** Target: Restored within 4 hours..
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Time to restore service | outcome | dora-metrics | Restored within 4 hours. | Incident management | Operations Lead |
**BO-3: We keep the platform engineers we hire.**
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Developer satisfaction | guardrail | space-framework | | Delivery and developer experience measurement | Platform Product Manager |
## What is operated
| Item | What it is | Kind | Product | From |
| --- | --- | --- | --- | --- |
| S-1 | Hub network and interconnect | network | Cloud Interconnect | |
| S-2 | Audit log store | storage | Cloud Storage | |
| S-3 | Deployment pipeline | pipeline | Cloud Build | |
| S-4 | Encryption keys | keys | Cloud KMS | |
What must be kept true while it is run:
| Condition | On | What must hold | From |
| --- | --- | --- | --- |
| K-1 | S-1 | The platform is available at least 99.9% of each month. | |
| K-2 | S-2 | Audit logs cannot be deleted for seven years. | |
| K-3 | S-4 | Encryption keys are rotated every 90 days. | |
## Operational requirements
| Requirement | Kind | What must be achieved | From |
| --- | --- | --- | --- |
| OR-1 | service_level | A fault on any Item is acknowledged within 15 minutes, at any hour. | service_levels.priority_1_response_minutes, operations.support_hours |
| OR-2 | service_level | Service is restored within 4 hours of a major failure. | service_levels.recovery_time_hours, BO-2 |
| OR-3 | service_level | The platform is available at least 99.9% of each month. | K-1 |
| OR-4 | process | Every change to the network requires customer platform team approval prior to implementation. | REQ-01 |
| OR-5 | process | A report of service levels and operating costs is provided monthly. | REQ-02 |
| OR-6 | organisation | The platform foundation is operated under a shared service model between the customer and an external service provider. | sourcing.model |
| OR-7 | organisation | Operational delivery is performed exclusively from the United Kingdom, Poland, and India. | sourcing.delivery_countries |
| OR-8 | compliance | Audit logs cannot be deleted for seven years. | K-2 |
| OR-9 | process | Encryption keys are rotated every 90 days. | K-3 |
| OR-10 | service_level | An approved change reaches production within one day of approval. | BO-1 |
## Capabilities
| Capability | What it is | Serves | Covers | Hours | Effort a month |
| --- | --- | --- | --- | --- | --- |
| C-1 | Incident management | OR-1, OR-2 | S-1, S-2, S-3, S-4 | 24x7 | 30 h |
| C-2 | Monitoring and alerting | OR-1, OR-3 | S-1, S-2, S-3, S-4 | 24x7 | 20 h |
| C-3 | Problem management | OR-2 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-4 | Service request fulfilment | OR-6 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-5 | Change enablement | OR-4, OR-10 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-6 | Release and deployment | OR-10 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-7 | Configuration management | OR-8, OR-9 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-8 | Backup and recovery | OR-2, OR-8 | S-2, S-4 | business | 10 h |
| C-9 | Service continuity | OR-2, OR-3 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-10 | Capacity and performance management | OR-3 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-11 | Access management | OR-6, OR-7 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-12 | Vulnerability and patch management | OR-9 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-13 | Security monitoring and response | OR-1, OR-8 | S-1, S-2, S-3, S-4 | 24x7 | 40 h |
| C-14 | Cost management | OR-5 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-15 | Service level management | OR-3, OR-5 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-16 | Platform product management | OR-6 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-17 | Self-service and golden paths | OR-10 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-18 | Enablement | OR-10 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-19 | Delivery and developer experience measurement | OR-10 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-20 | Supplier management | OR-6, OR-7 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-21 | Regulatory evidence and reporting | OR-8 | S-1, S-2, S-3, S-4 | business | 10 h |
## Who does what
| Role | Party | Country | Level | Hours |
| --- | --- | --- | --- | --- |
| Platform Product Manager | Customer (customer) | GB | lead | business |
| Platform Engineer | Customer (customer) | GB | senior | business |
| Operations Engineer | Service Provider (provider) | IN | engineer | 24x7 |
| Operations Lead | Service Provider (provider) | IN | lead | business |
| Security Operations Analyst | Service Provider (provider) | IN | senior | 24x7 |
| Platform Ops Specialist | Service Provider (provider) | PL | senior | business |
The teams, as Team Topologies names their kinds:
| Team | Kind | Party | Roles | Purpose |
| --- | --- | --- | --- | --- |
| Customer Platform Team | platform | Customer | Platform Product Manager, Platform Engineer | Owns the platform roadmap, retains network change approvals, and measures developer flow. |
| Provider Operations Team | platform | Service Provider | Operations Engineer, Operations Lead, Security Operations Analyst, Platform Ops Specialist | Provides 24x7 monitoring, incident response, and day-to-day operations of the platform foundation. |
How the teams work together:
| From | To | Mode | Until | Purpose |
| --- | --- | --- | --- | --- |
| Provider Operations Team | Customer Platform Team | x-as-a-service | | Provider requests network change approvals from the Customer Platform Team. |
| Customer Platform Team | Provider Operations Team | x-as-a-service | | Customer relies on Provider Operations Team for 24x7 incident response and monitoring. |
| Provider Operations Team | Customer Platform Team | collaboration | Month 3 after go-live, shifting to x-as-a-service. | Handover of runbooks and initial operational processes. |
| Capability | Platform Product Manager | Platform Engineer | Operations Engineer | Operations Lead | Security Operations Analyst | Platform Ops Specialist |
| --- | --- | --- | --- | --- | --- | --- |
| Incident management (C-1) | | C | R | A | | |
| Monitoring and alerting (C-2) | | C | R | A | | |
| Problem management (C-3) | | C | | A | | R |
| Service request fulfilment (C-4) | | C | R | A | | |
| Change enablement (C-5) | | A/R | | | | R |
| Release and deployment (C-6) | | A/R | | | | R |
| Configuration management (C-7) | | C | | A | | R |
| Backup and recovery (C-8) | | C | | A | | R |
| Service continuity (C-9) | | C | | A | | R |
| Capacity and performance management (C-10) | | C | | A/R | | |
| Access management (C-11) | | C | | A/R | | |
| Vulnerability and patch management (C-12) | | C | | | A/R | |
| Security monitoring and response (C-13) | | C | | | A/R | |
| Cost management (C-14) | C | | | A/R | | |
| Service level management (C-15) | C | | | A/R | | |
| Platform product management (C-16) | A/R | | | C | | |
| Self-service and golden paths (C-17) | | A/R | | | | R |
| Enablement (C-18) | | A/R | | | | R |
| Delivery and developer experience measurement (C-19) | A/R | | | C | | |
| Supplier management (C-20) | A/R | | | R | | |
| Regulatory evidence and reporting (C-21) | | C | | A | | R |
A accountable, R responsible, C consulted, I informed.
## Staffing and cost
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Platform Product Manager | Customer | GB | lead | business | 30.0 h | 0.2 | not priced |
| Platform Engineer | Customer | GB | senior | business | 35.0 h | 0.3 | not priced |
| Operations Engineer | Service Provider | IN | engineer | 24x7 | 70.0 h | 5.0 | 17,034 GBP |
| Operations Lead | Service Provider | IN | lead | business | 50.0 h | 0.3 | 1,876 GBP |
| Security Operations Analyst | Service Provider | IN | senior | 24x7 | 55.0 h | 5.0 | 24,605 GBP |
| Platform Ops Specialist | Service Provider | PL | senior | business | 90.0 h | 0.6 | 4,088 GBP |
11.4 people in all. Cost a month: 47,603 GBP.
The monthly budget is 60,000 GBP: this is within it.
Worked from rate card `rate-card`, version `draft-2026-10-13`. **Its figures are placeholders: no price has been set, and this cost is an illustration.**
Converted from USD at 0.79, a rate set on 2026-10-13.
The customer's own staff are counted and not priced. A Role that covers hours wider than a working day is never smaller than the team that can cover them.
## Validation
| Check | What must hold | Verdict | Evidence |
| --- | --- | --- | --- |
| OC-1 | A fault on the hub network or any other item is acknowledged within 15 minutes at any hour. | pass | C-1 handles incident management 24x7, with a 24x7 Operations Engineer responsible, enabling acknowledgement of faults within 15 minutes at any hour. The cloud provider's native tooling (via C-2) supports configuring alerts without requiring a separate finding. |
| OC-2 | Service is restored within 4 hours of a major failure on the platform. | pass | C-1 manages incident resolution with a 24x7 Operations Engineer responsible, allowing restoration of service within 4 hours of a major failure regardless of when the failure occurs. |
| OC-3 | The platform availability is tracked to ensure at least 99.9% uptime each month. | pass | C-15 tracks and gathers metrics on availability to ensure the 99.9% target is tracked, with business-hours roles accountable and responsible. |
| OC-4 | Capacity limits for the platform interconnect are managed to support 99.9% availability. | pass | C-10 reviews capacity trends for the interconnect to assure 99.9% availability, managed by the Operations Lead. |
| OC-5 | Every change to the hub network requires explicit approval from the customer platform team. | pass | C-5 coordinates network change approvals with the customer, and a Customer Platform Engineer is accountable and responsible for it, ensuring explicit approval from the customer platform team. |
| OC-6 | A consolidated monthly report includes service levels and operating costs. | pass | C-15 compiles the monthly operational report, pulling in cost data tracked by C-14, both managed by the Operations Lead. |
| OC-7 | The shared service model responsibilities between customer and external service provider are governed. | pass | C-20 coordinates responsibilities across shared delivery borders, with roles from both the customer and provider teams responsible. |
| OC-8a | Role performs operational delivery from India. | pass | R-3 (Operations Engineer) is based in India, satisfying the geographical requirement. |
| OC-8b | Role performs operational delivery from India. | pass | R-4 (Operations Lead) is based in India, satisfying the geographical requirement. |
| OC-8c | Role performs operational delivery from India. | pass | R-5 (Security Operations Analyst) is based in India, satisfying the geographical requirement. |
| OC-8d | Role performs operational delivery from Poland. | pass | R-6 (Platform Ops Specialist) is based in Poland, satisfying the geographical requirement. |
| OC-8e | Role performs operational delivery from the UK. | pass | R-1 (Platform Product Manager) is based in the UK, satisfying the geographical requirement. |
| OC-8f | Role performs operational delivery from the UK. | pass | R-2 (Platform Engineer) is based in the UK, satisfying the geographical requirement. |
| OC-9 | Audit log storage configuration ensures logs cannot be deleted for seven years. | pass | C-7 maintains audit log retention settings, with the Platform Ops Specialist responsible, ensuring logs cannot be deleted for seven years. |
| OC-10 | Retention policies on Cloud Storage for audit logs are verified to prevent deletion for seven years. | pass | C-7 maintains and verifies retention settings on Cloud Storage for audit logs, satisfying the seven-year retention condition. |
| OC-11 | Encryption key configurations are audited to ensure rotation every 90 days. | pass | C-7 audits configuration drift and manages key rotation schedules, ensuring encryption keys are rotated every 90 days. |
| OC-12 | Cloud KMS encryption keys are verified to rotate every 90 days. | pass | C-7 manages key rotation schedules for the Cloud KMS encryption keys, verifying they rotate every 90 days. |
| OC-13 | Deployment pipelines ensure an approved change reaches production within one day. | pass | C-6 oversees deployment pipelines to ensure approved changes reach production within a day, with customer and provider roles responsible. |
| OC-14 | Backups of audit logs and encryption keys are successfully tested for restoration. | pass | C-8 maintains backups of logs and keys and successfully tests restore procedures, managed by the Platform Ops Specialist. |
Each scenario is generated from the operating model and traced through it by code.
| Scenario | Result | Path |
| --- | --- | --- |
| Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Hub network and interconnect (S-1) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Audit log store (S-2) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Audit log store (S-2) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Deployment pipeline (S-3) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Encryption keys (S-4) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Encryption keys (S-4) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. | pass | Check OC-4 on C-10 keeps it true. |
| Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. | pass | Check OC-10 on C-7 keeps it true. |
| Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. | pass | Check OC-12 on C-7 keeps it true. |
| Service Provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
| A month's cost of operating is compared with the budget of 60,000 GBP. | pass | The cost is 47,603 GBP, within the budget. |
## Findings and open questions
No findings: the solution provides what operating it needs.
Assumed for the customer, and open to change when they answer:
- `intent.exclusions`: Workload applications running on the platform foundation, Network change approvals (retained by customer platform team). Assumed from the platform foundation scope: workload applications running on the platform are out of scope, and customer platform team retains network change approvals.
- `operations.change_process`: Changes go through a deployment pipeline with peer review, with network changes requiring customer platform team approval.. Catalogue default adapted to customer requirement REQ-01: changes go through deployment pipelines with peer review, with customer platform team retaining approval over network changes.
- `service_management.tooling`: The Cloud provider's own operations tooling, with no separate system.. Catalogue default: Cloud provider's native operations tooling with no separate system.
## Sources
The Capabilities are from our own capability catalogue, which draws on these frameworks. It cites them and certifies nothing against them.
- ITIL 4: Incident management practice; Monitoring and event management practice; Problem management practice; Service request management practice; Change enablement practice; Release management and Deployment management practices; Service configuration management practice; Service continuity management practice; Capacity and performance management practice; Service level management practice; Supplier management practice
- Site Reliability Engineering: How Google Runs Production Systems: Managing Incidents; Monitoring Distributed Systems; Postmortem Culture: Learning from Failure; Release Engineering; Service Level Objectives
- ISO/IEC 20000-1: Incident management; Service request management; Change management; Service continuity management; Capacity management; Service level management; Supplier management
- Regulation (EU) 2022/2554, the Digital Operational Resilience Act: Article 17, ICT-related incident management process; Article 10, Detection; Article 12, Backup policies and procedures, restoration and recovery procedures and methods; Article 11, Response and recovery; Article 9, Protection and prevention; Article 28, General principles on ICT third-party risk; Article 19, Reporting of major ICT-related incidents
- NIST Cybersecurity Framework: Detect: Continuous Monitoring; Identify: Asset Management; Recover: Incident Recovery Plan Execution; Protect: Identity Management, Authentication, and Access Control; Protect: Platform Security; Detect: Adverse Event Analysis; Respond: Incident Management
- DevOps Research and Assessment (DORA) software delivery metrics: Change failure rate; Deployment frequency and lead time for changes; Deployment frequency; Lead time for changes; Change failure rate; Time to restore service
- ISO/IEC 27001: Access control; Management of technical vulnerabilities; Information security incident management; Compliance with legal and contractual requirements
- FinOps Framework: Allocation; Budgeting; Forecasting; Anomaly Management
- CNCF Platforms White Paper (platform as a product): Platform as a product; Measuring platform success; Platform capabilities; Self-service; Platform as a product
- Team Topologies: Organizing Business and Technology Teams for Fast Flow: Platform team; Thinnest viable platform; X-as-a-Service interaction mode; Enabling team; Facilitating interaction mode
- The SPACE of Developer Productivity: Satisfaction and well-being; Performance; Activity; Communication and collaboration; Efficiency and flow
- DevEx: What Actually Drives Productivity: Feedback loops; Cognitive load; Flow state
**These references have not been checked against the frameworks by a person.** Treat each as a pointer to where to look.

View File

@@ -0,0 +1,39 @@
# Scope statement
This operating scope covers the Google Cloud landing zone platform foundation, comprising the hub network and interconnect, audit log store, deployment pipeline, and encryption keys. The platform is operated under a shared service model jointly by a service provider delivering from the United Kingdom, Poland, and India, and the customer's platform team based in the United Kingdom. Fault response support is provided 24x7, aligning with continuous 24x7 platform availability. All operating costs are stated in GBP. Out of scope for provider operations are workload applications hosted on the platform foundation and final approval authority for network changes, which is retained by the customer platform team.
## Information register
20 stated by the customer, 0 answered in conversation, 3 assumed, 10 unknown, 0 not applicable.
| Field | Value | From |
| --- | --- | --- |
| engagement.kind | platform_foundation | the scope spec |
| intent.statement | We want our landing zone run as a shared service from go-live. A provider should respond to faults at every hour, and our own platform team keeps the final say over changes to the network. | the scope spec |
| intent.requirements | [{"id": "REQ-01", "statement": "Our platform team approves every change to the network."}, {"id": "REQ-02", "statement": "We receive a monthly report of service levels and cost."}] | the scope spec |
| intent.business_outcomes | [{"id": "BO-1", "outcome": "New payment products reach customers in weeks rather than months.", "target": "A change reaches production within a day of approval."}, {"id": "BO-2", "outcome": "Payments | the scope spec |
| solution.cloud_provider | gcp | the scope spec |
| solution.items | [{"id": "S-1", "name": "Hub network and interconnect", "kind": "network", "product": "Cloud Interconnect"}, {"id": "S-2", "name": "Audit log store", "kind": "storage", "product": "Cloud Storage"}, {"i | the scope spec |
| solution.conditions | [{"id": "K-1", "on": ["S-1"], "condition": "The platform is available at least 99.9% of each month."}, {"id": "K-2", "on": ["S-2"], "condition": "Audit logs cannot be deleted for seven years."}, {"id" | the scope spec |
| solution.build.duration_days | 36 | the scope spec |
| operations.support_hours | 24x7 | the scope spec |
| operations.availability_hours | 24x7 | the scope spec |
| sourcing.model | shared | the scope spec |
| sourcing.delivery_countries | ["GB", "PL", "IN"] | the scope spec |
| organisation.existing_teams | [{"name": "Platform team", "party": "customer", "hours": "business", "country": "GB"}] | the scope spec |
| service_levels.priority_1_response_minutes | 15 | the scope spec |
| service_levels.recovery_time_hours | 4 | the scope spec |
| compliance.frameworks | ["DORA"] | the scope spec |
| commercial.currency | GBP | the scope spec |
| commercial.monthly_run_budget | 60000 | the scope spec |
| intent.exclusions | ["Workload applications running on the platform foundation", "Network change approvals (retained by customer platform team)"] | assumed |
| operations.change_process | Changes go through a deployment pipeline with peer review, with network changes requiring customer platform team approval. | assumed |
| service_management.tooling | The Cloud provider's own operations tooling, with no separate system. | assumed |
### Assumptions
| Id | Assumption | If it is wrong |
| --- | --- | --- |
| ASSUMP-01 | Assumed intent.exclusions is ['Workload applications running on the platform foundation', 'Network change approvals (retained by customer platform team)']. Assumed from the platform foundation scope: workload applications running on the platform are out of scope, and customer platform team retains network change approvals. | Changes which Capabilities are designed. |
| ASSUMP-02 | Assumed operations.change_process is Changes go through a deployment pipeline with peer review, with network changes requiring customer platform team approval.. Catalogue default adapted to customer requirement REQ-01: changes go through deployment pipelines with peer review, with customer platform team retaining approval over network changes. | Changes change enablement and release. |
| ASSUMP-03 | Assumed service_management.tooling is The Cloud provider's own operations tooling, with no separate system.. Catalogue default: Cloud provider's native operations tooling with no separate system. | Changes tooling and the processes written for it. |

View File

@@ -0,0 +1,100 @@
# Operational Requirements
This document defines what running the platform foundation solution must achieve. Each operational requirement is traced directly to customer statements, solution conditions, business outcomes, or binding fields settled within the operating specification. Requirements state what must be achieved without prescribing capabilities, roles, or tools.
## Operational requirements
The operational requirements are grouped below by kind: service level, process, organisation, and compliance.
### Service Level Requirements
- **OR-1 (Fault acknowledgement response)**: A fault on any Item is acknowledged within 15 minutes, at any hour.
- *Source*: `service_levels.priority_1_response_minutes`, `operations.support_hours`
- **OR-2 (Service restoration time)**: Service is restored within 4 hours of a major failure.
- *Source*: `service_levels.recovery_time_hours`, `BO-2`
- **OR-3 (Platform availability)**: The platform is available at least 99.9% of each month.
- *Source*: `K-1`
- **OR-10 (Change delivery turnaround)**: An approved change reaches production within one day of approval.
- *Source*: `BO-1`
### Process Requirements
- **OR-4 (Network change governance)**: Every change to the network requires customer platform team approval prior to implementation.
- *Source*: `REQ-01`
- **OR-5 (Monthly operational reporting)**: A report of service levels and operating costs is provided monthly.
- *Source*: `REQ-02`
- **OR-9 (Cryptographic key lifecycle)**: Encryption keys are rotated every 90 days.
- *Source*: `K-3`
### Organisation Requirements
- **OR-6 (Shared operating model)**: The platform foundation is operated under a shared service model between the customer and an external service provider.
- *Source*: `sourcing.model`
- **OR-7 (Delivery geographic boundaries)**: Operational delivery is performed exclusively from the United Kingdom, Poland, and India.
- *Source*: `sourcing.delivery_countries`
### Compliance Requirements
- **OR-8 (Audit log retention)**: Audit logs cannot be deleted for seven years.
- *Source*: `K-2`
### Requirements Traceability Summary
| Requirement ID | Kind | Operational Requirement Statement | Source References |
| --- | --- | --- | --- |
| **OR-1** | `service_level` | A fault on any Item is acknowledged within 15 minutes, at any hour. | `service_levels.priority_1_response_minutes`, `operations.support_hours` |
| **OR-2** | `service_level` | Service is restored within 4 hours of a major failure. | `service_levels.recovery_time_hours`, `BO-2` |
| **OR-3** | `service_level` | The platform is available at least 99.9% of each month. | `K-1` |
| **OR-4** | `process` | Every change to the network requires customer platform team approval prior to implementation. | `REQ-01` |
| **OR-5** | `process` | A report of service levels and operating costs is provided monthly. | `REQ-02` |
| **OR-6** | `organisation` | The platform foundation is operated under a shared service model between the customer and an external service provider. | `sourcing.model` |
| **OR-7** | `organisation` | Operational delivery is performed exclusively from the United Kingdom, Poland, and India. | `sourcing.delivery_countries` |
| **OR-8** | `compliance` | Audit logs cannot be deleted for seven years. | `K-2` |
| **OR-9** | `process` | Encryption keys are rotated every 90 days. | `K-3` |
| **OR-10** | `service_level` | An approved change reaches production within one day of approval. | `BO-1` |
---
## What was not stated
The operating specification leaves several areas assumed or unknown. If answered differently, these would alter the operational requirements.
### Assumptions
Because execution is pre-approved, the following assumptions were recorded from the operating specification and catalogue defaults:
1. **Assumed scope exclusions (`intent.exclusions`)**:
- *Assumption*: Workload applications hosted on the platform foundation are out of scope for provider operations, and network change approvals are retained by the customer platform team.
- *Impact if wrong*: If application workloads were in scope, additional operational requirements for application-layer monitoring, incident triage, deployment coordination, and service-level objectives would be required. If the provider had delegated authority for network modifications, OR-4 would need to be re-scoped.
2. **Assumed change release mechanism (`operations.change_process`)**:
- *Assumption*: Changes proceed through automated deployment pipelines with peer review, with network changes requiring explicit customer platform team approval.
- *Impact if wrong*: If a formal change advisory board (CAB) or manual approval cadence is mandated for non-network components, change lead time requirements (OR-10) would be affected.
3. **Assumed operations tooling (`service_management.tooling`)**:
- *Assumption*: The cloud provider's native operations tooling is utilized without a separate third-party IT service management (ITSM) system.
- *Impact if wrong*: If an external enterprise ITSM platform (e.g., ServiceNow, Jira Service Desk) or dedicated paging tool is mandated, additional requirements for cross-platform integration, ticket synchronization, and external reporting would emerge.
### Unknowns and Open Questions
The operating spec identifies the following unknown fields:
1. **Existing monitoring and alerting (`operations.monitoring`)**:
- *Current status*: Unknown.
- *Impact if answered*: Existing monitoring configurations and alert thresholds could impose specific operational requirements regarding synthetic checks, telemetry ingestion rates, or incident trigger definitions.
2. **Customer-owned build components (`solution.build.customer_owned`)**:
- *Current status*: Unknown.
- *Impact if answered*: If specific infrastructure components or pipelines are managed or maintained by customer internal teams, operational boundaries and fault hand-off requirements would need specification.
3. **Inherited solution risks (`solution.inherited_risks`)**:
- *Current status*: Unknown.
- *Impact if answered*: Known risks in interconnect redundancy or key distribution would require explicit contingency and high-availability operational requirements.
4. **Headcount constraints (`organisation.headcount_limit`)**:
- *Current status*: Unknown.
- *Impact if answered*: A hard headcount cap would constrain how 24x7 coverage is staffed across the three delivery countries (GB, PL, IN).
5. **Operational transition go-live date (`transition.go_live_date`)**:
- *Current status*: Unknown.
- *Impact if answered*: A defined target date would introduce operational readiness milestones and timeline-bound acceptance criteria.

View File

@@ -0,0 +1,87 @@
# Target operating model
## Design rationale
The operating model is designed around a shared responsibility between the customer and an external service provider, maintaining a clear boundary while enabling fast flow and 24x7 operational coverage. The approach maps operational capabilities to defined roles, ensures proper coverage for the declared service levels, and incorporates measurement feedback loops to achieve the stated business outcomes.
### Parties and Teams
Two primary parties are defined in the operating model: the **Customer** and the **Service Provider**.
To align with Team Topologies, we defined two platform-focused teams:
- The **Customer Platform Team** (Customer) focuses on platform evolution, owning the platform roadmap, defining golden paths, and measuring developer flow. This team acts as the platform owner and retains authority over network change approvals.
- The **Provider Operations Team** (Service Provider) is responsible for the day-to-day running of the platform foundation, including 24x7 monitoring, incident response, and executing operational tasks such as backups and patching.
### Roles, Location, and Capability Coverage
Roles are situated in the approved delivery countries (UK, Poland, and India):
- The **Platform Product Manager** (Lead) and **Platform Engineer** (Senior) are situated in the UK, closely collaborating with the customer's business and engineering teams during business hours. They steer the platform, ensure adherence to the 1-day deployment targets, and maintain alignment with business goals.
- The **Operations Engineer** and **Security Operations Analyst** provide 24x7 coverage from India, ensuring rapid response to faults and security events at all hours. They form the backbone of the provider's support roster.
- The **Operations Lead** (India) provides business-hours guidance and accountability for the operational capabilities, ensuring adherence to the 99.9% uptime target.
- The **Platform Ops Specialist** sits in Poland, offering advanced business-hours support, handling problem management, configuration management, and disaster recovery preparations.
For any capabilities where the provider is accountable, a customer role is marked as consulted to ensure there is always a contact point if the provider requires customer guidance. This distribution balances the need for continuous coverage with efficient use of resources across the specified delivery regions.
*(Note: Costs and exact headcounts are derived from the rate card. Because the rate card is currently in draft, any financial and staffing figures resulting from this model will act as placeholders.)*
### Interactions
The Customer Platform Team and Provider Operations Team interact primarily via an **X-as-a-Service** mode. The Provider consumes network change approvals from the Customer, while the Customer relies on the Provider for 24x7 incident response. During the first three months post-go-live, the teams will engage in a **Collaboration** to ensure a smooth handover of runbooks and establish operational processes before shifting entirely to X-as-a-Service.
### Measurement
To ensure the model is serving the business effectively, measurements are tied to the required outcomes. Since the model employs delivery and developer experience measurement (C-19), all three core layers of flow are measured:
- **Outcome** is measured by deployment frequency (using DORA metrics) to ensure changes reach production within a day, and time to restore service.
- **Guardrail** metrics measure developer satisfaction (using the SPACE framework) to ensure retention of platform engineers.
- **Leading signals** track friction and cognitive load (using the DevEx framework) to identify early friction that could impede the target of weeks rather than months for new payment products.
### Assumptions
As this execution is pre-approved, the following assumptions were made:
- Native operational tooling from the cloud provider is sufficient to configure necessary alerts, monitors, and verify restoration of backups or logs without needing separate systems, manual design-arounds, or findings.
- The customer platform team has sufficient capacity to process network change approvals within the timeframes needed to meet deployment targets.
## Responsibility matrix
| Capability | Platform Product Manager | Platform Engineer | Operations Engineer | Operations Lead | Security Operations Analyst | Platform Ops Specialist |
| --- | --- | --- | --- | --- | --- | --- |
| Incident management (C-1) | | C | R | A | | |
| Monitoring and alerting (C-2) | | C | R | A | | |
| Problem management (C-3) | | C | | A | | R |
| Service request fulfilment (C-4) | | C | R | A | | |
| Change enablement (C-5) | | A/R | | | | R |
| Release and deployment (C-6) | | A/R | | | | R |
| Configuration management (C-7) | | C | | A | | R |
| Backup and recovery (C-8) | | C | | A | | R |
| Service continuity (C-9) | | C | | A | | R |
| Capacity and performance management (C-10) | | C | | A/R | | |
| Access management (C-11) | | C | | A/R | | |
| Vulnerability and patch management (C-12) | | C | | | A/R | |
| Security monitoring and response (C-13) | | C | | | A/R | |
| Cost management (C-14) | C | | | A/R | | |
| Service level management (C-15) | C | | | A/R | | |
| Platform product management (C-16) | A/R | | | C | | |
| Self-service and golden paths (C-17) | | A/R | | | | R |
| Enablement (C-18) | | A/R | | | | R |
| Delivery and developer experience measurement (C-19) | A/R | | | C | | |
| Supplier management (C-20) | A/R | | | R | | |
| Regulatory evidence and reporting (C-21) | | C | | A | | R |
A accountable, R responsible, C consulted, I informed.
## Staffing and cost
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Platform Product Manager | Customer | GB | lead | business | 30.0 h | 0.2 | not priced |
| Platform Engineer | Customer | GB | senior | business | 35.0 h | 0.3 | not priced |
| Operations Engineer | Service Provider | IN | engineer | 24x7 | 70.0 h | 5.0 | 17,034 GBP |
| Operations Lead | Service Provider | IN | lead | business | 50.0 h | 0.3 | 1,876 GBP |
| Security Operations Analyst | Service Provider | IN | senior | 24x7 | 55.0 h | 5.0 | 24,605 GBP |
| Platform Ops Specialist | Service Provider | PL | senior | business | 90.0 h | 0.6 | 4,088 GBP |
11.4 people in all. Cost a month: 47,603 GBP.
The monthly budget is 60,000 GBP: this is within it.
Worked from rate card `rate-card`, version `draft-2026-10-13`. **Its figures are placeholders: no price has been set, and this cost is an illustration.**
Converted from USD at 0.79, a rate set on 2026-10-13.
The customer's own staff are counted and not priced. A Role that covers hours wider than a working day is never smaller than the team that can cover them.

View File

@@ -0,0 +1,47 @@
# Validation results
## Check verdicts
The target operating model has been evaluated against the operational requirements, conditions, and business outcomes. Below are the verdicts for each check:
- **OC-1 (pass):** C-1 handles incident management 24x7, with a 24x7 Operations Engineer responsible, enabling acknowledgement of faults within 15 minutes at any hour. The cloud provider's native tooling (via C-2) supports configuring alerts without requiring a separate finding.
- **OC-2 (pass):** C-1 manages incident resolution with a 24x7 Operations Engineer responsible, allowing restoration of service within 4 hours of a major failure regardless of when the failure occurs.
- **OC-3 (pass):** C-15 tracks and gathers metrics on availability to ensure the 99.9% target is tracked, with business-hours roles accountable and responsible.
- **OC-4 (pass):** C-10 reviews capacity trends for the interconnect to assure 99.9% availability, managed by the Operations Lead.
- **OC-5 (pass):** C-5 coordinates network change approvals with the customer, and a Customer Platform Engineer is accountable and responsible for it, ensuring explicit approval from the customer platform team.
- **OC-6 (pass):** C-15 compiles the monthly operational report, pulling in cost data tracked by C-14, both managed by the Operations Lead.
- **OC-7 (pass):** C-20 coordinates responsibilities across shared delivery borders, with roles from both the customer and provider teams responsible.
- **OC-8a (pass):** R-3 (Operations Engineer) is based in India, satisfying the geographical requirement.
- **OC-8b (pass):** R-4 (Operations Lead) is based in India, satisfying the geographical requirement.
- **OC-8c (pass):** R-5 (Security Operations Analyst) is based in India, satisfying the geographical requirement.
- **OC-8d (pass):** R-6 (Platform Ops Specialist) is based in Poland, satisfying the geographical requirement.
- **OC-8e (pass):** R-1 (Platform Product Manager) is based in the UK, satisfying the geographical requirement.
- **OC-8f (pass):** R-2 (Platform Engineer) is based in the UK, satisfying the geographical requirement.
- **OC-9 (pass):** C-7 maintains audit log retention settings, with the Platform Ops Specialist responsible, ensuring logs cannot be deleted for seven years.
- **OC-10 (pass):** C-7 maintains and verifies retention settings on Cloud Storage for audit logs, satisfying the seven-year retention condition.
- **OC-11 (pass):** C-7 audits configuration drift and manages key rotation schedules, ensuring encryption keys are rotated every 90 days.
- **OC-12 (pass):** C-7 manages key rotation schedules for the Cloud KMS encryption keys, verifying they rotate every 90 days.
- **OC-13 (pass):** C-6 oversees deployment pipelines to ensure approved changes reach production within a day, with customer and provider roles responsible.
- **OC-14 (pass):** C-8 maintains backups of logs and keys and successfully tests restore procedures, managed by the Platform Ops Specialist.
**Overall Verdict:** The target operating model **passes** validation. The roles, coverage hours, and capabilities are fully aligned with the operational requirements and the designated shared service sourcing model.
## Scenario walk-throughs
Each scenario is generated from the operating model and traced through it by code.
| Scenario | Result | Path |
| --- | --- | --- |
| Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Hub network and interconnect (S-1) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Audit log store (S-2) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Audit log store (S-2) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Deployment pipeline (S-3) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Encryption keys (S-4) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Encryption keys (S-4) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. | pass | Check OC-4 on C-10 keeps it true. |
| Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. | pass | Check OC-10 on C-7 keeps it true. |
| Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. | pass | Check OC-12 on C-7 keeps it true. |
| Service Provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
| A month's cost of operating is compared with the budget of 60,000 GBP. | pass | The cost is 47,603 GBP, within the budget. |

View File

@@ -0,0 +1,113 @@
{
"customer_case": "bench-landing-zone-shared",
"execution_id": "case-01-landing-zone-shared-r3",
"session_id": "d0d953a6-5254-4646-8d70-7fd6139f1afc",
"intent_version": 3,
"workflow_request": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.",
"baseline": null,
"overlay_skills": {},
"options": {},
"sources": {},
"scope": {
"status": "BASELINE_LOCKED",
"readiness": {
"supplied": 20,
"answered": 0,
"assumed": 3,
"unknown": 10,
"not_applicable": 0
}
},
"status": "completed",
"warnings": [],
"risks": [],
"assessment": null,
"phases": {
"scoping": "approved",
"operational_requirements": "approved",
"operating_model_design": "approved",
"validation": "approved",
"packaging": "approved"
},
"final_document": "operating-model-guide.md",
"changes": null,
"deliverables": {
"operating_scope": {
"document": "deliverables/operating_scope.md",
"attachments": [
"scope.json",
"scope.yaml"
],
"status": "submitted"
},
"operational_requirements": {
"document": "deliverables/operational_requirements.md",
"attachments": [
"operational-requirements.json"
],
"status": "submitted"
},
"capability_model": {
"document": "deliverables/capability_model.md",
"attachments": [
"capabilities.json"
],
"status": "submitted"
},
"target_operating_model": {
"document": "deliverables/target_operating_model.md",
"attachments": [
"findings.json",
"organisation.mmd",
"staffing.json",
"target-operating-model.json"
],
"status": "submitted"
},
"validation_results": {
"document": "deliverables/validation_results.md",
"attachments": [
"scenarios.json",
"verdicts.json"
],
"status": "submitted"
},
"operating_model_guide": {
"document": "deliverables/operating_model_guide.md",
"attachments": [],
"status": "submitted"
}
},
"files": [
"capabilities.json",
"deliverables/capability_model.md",
"deliverables/operating_model_guide.md",
"deliverables/operating_scope.md",
"deliverables/operational_requirements.md",
"deliverables/target_operating_model.md",
"deliverables/validation_results.md",
"findings.json",
"operating-model-guide.md",
"operational-requirements.json",
"organisation.mmd",
"scenarios.json",
"scope.json",
"scope.yaml",
"staffing.json",
"target-operating-model.json",
"verdicts.json"
],
"staffing": {
"people": 11.4,
"cost_per_month": 47603,
"currency": "GBP",
"rate_card": {
"name": "rate-card",
"version": "draft-2026-10-13",
"draft": true
}
},
"findings": [],
"change_request": null,
"capability_sources_verified": false
}

View File

@@ -0,0 +1,237 @@
# Operating model guide: Google Cloud landing zone platform foundation
## Summary
This guide sets out the target operating model for the Google Cloud landing zone platform foundation, covering the hub network and interconnect, audit log store, deployment pipeline, and encryption keys. Operational responsibility is shared between the customer and an external service provider across the United Kingdom, Poland, and India. The customer platform team steers platform product direction, developer flow measurement, and retains approval authority over all network changes, while the service provider operations team runs day-to-day operations, maintenance, and incident management. Fault response and platform availability are maintained around the clock (24x7), while change governance, service continuity, and lifecycle management are conducted during business hours.
Readers should look first at the findings and open questions, particularly the catalogue assumptions regarding cloud-native operations tooling, change pipeline procedures, and the exclusion of workload applications, as well as the draft status of the rate card. All scenario walk-throughs and validation checks pass successfully within the allocated operational budget.
### Key figures
- Operated: 4 Items, with 3 Conditions to keep true.
- Faults responded to: 24x7 hours.
- Capabilities: 21.
- People: 11.4. Cost a month: 47,603 GBP, from rate card version `draft-2026-10-13` (placeholder prices: an illustration).
- Scenario walk-throughs: 13 of 13 pass.
- Business outcomes: 3, 3 shown by a Measure.
- Findings for whoever owns the design: 0.
## Business outcomes
**BO-1: New payment products reach customers in weeks rather than months.** Target: A change reaches production within a day of approval..
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Deployment frequency | outcome | dora-metrics | A change reaches production within a day of approval. | Delivery and developer experience measurement | Platform Product Manager |
| Friction and cognitive load | leading | devex-framework | | Delivery and developer experience measurement | Platform Product Manager |
**BO-2: Payments are never unavailable for long.** Target: Restored within 4 hours..
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Time to restore service | outcome | dora-metrics | Restored within 4 hours. | Incident management | Operations Lead |
**BO-3: We keep the platform engineers we hire.**
| Measure | Layer | Framework | Target | Measured by | Answerable |
| --- | --- | --- | --- | --- | --- |
| Developer satisfaction | guardrail | space-framework | | Delivery and developer experience measurement | Platform Product Manager |
## What is operated
| Item | What it is | Kind | Product | From |
| --- | --- | --- | --- | --- |
| S-1 | Hub network and interconnect | network | Cloud Interconnect | |
| S-2 | Audit log store | storage | Cloud Storage | |
| S-3 | Deployment pipeline | pipeline | Cloud Build | |
| S-4 | Encryption keys | keys | Cloud KMS | |
What must be kept true while it is run:
| Condition | On | What must hold | From |
| --- | --- | --- | --- |
| K-1 | S-1 | The platform is available at least 99.9% of each month. | |
| K-2 | S-2 | Audit logs cannot be deleted for seven years. | |
| K-3 | S-4 | Encryption keys are rotated every 90 days. | |
## Operational requirements
| Requirement | Kind | What must be achieved | From |
| --- | --- | --- | --- |
| OR-1 | service_level | A fault on any Item is acknowledged within 15 minutes, at any hour. | service_levels.priority_1_response_minutes, operations.support_hours |
| OR-2 | service_level | Service is restored within 4 hours of a major failure. | service_levels.recovery_time_hours, BO-2 |
| OR-3 | service_level | The platform is available at least 99.9% of each month. | K-1 |
| OR-4 | process | Every change to the network requires customer platform team approval prior to implementation. | REQ-01 |
| OR-5 | process | A report of service levels and operating costs is provided monthly. | REQ-02 |
| OR-6 | organisation | The platform foundation is operated under a shared service model between the customer and an external service provider. | sourcing.model |
| OR-7 | organisation | Operational delivery is performed exclusively from the United Kingdom, Poland, and India. | sourcing.delivery_countries |
| OR-8 | compliance | Audit logs cannot be deleted for seven years. | K-2 |
| OR-9 | process | Encryption keys are rotated every 90 days. | K-3 |
| OR-10 | service_level | An approved change reaches production within one day of approval. | BO-1 |
## Capabilities
| Capability | What it is | Serves | Covers | Hours | Effort a month |
| --- | --- | --- | --- | --- | --- |
| C-1 | Incident management | OR-1, OR-2 | S-1, S-2, S-3, S-4 | 24x7 | 30 h |
| C-2 | Monitoring and alerting | OR-1, OR-3 | S-1, S-2, S-3, S-4 | 24x7 | 20 h |
| C-3 | Problem management | OR-2 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-4 | Service request fulfilment | OR-6 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-5 | Change enablement | OR-4, OR-10 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-6 | Release and deployment | OR-10 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-7 | Configuration management | OR-8, OR-9 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-8 | Backup and recovery | OR-2, OR-8 | S-2, S-4 | business | 10 h |
| C-9 | Service continuity | OR-2, OR-3 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-10 | Capacity and performance management | OR-3 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-11 | Access management | OR-6, OR-7 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-12 | Vulnerability and patch management | OR-9 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-13 | Security monitoring and response | OR-1, OR-8 | S-1, S-2, S-3, S-4 | 24x7 | 40 h |
| C-14 | Cost management | OR-5 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-15 | Service level management | OR-3, OR-5 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-16 | Platform product management | OR-6 | S-1, S-2, S-3, S-4 | business | 15 h |
| C-17 | Self-service and golden paths | OR-10 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-18 | Enablement | OR-10 | S-1, S-2, S-3, S-4 | business | 20 h |
| C-19 | Delivery and developer experience measurement | OR-10 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-20 | Supplier management | OR-6, OR-7 | S-1, S-2, S-3, S-4 | business | 10 h |
| C-21 | Regulatory evidence and reporting | OR-8 | S-1, S-2, S-3, S-4 | business | 10 h |
## Who does what
| Role | Party | Country | Level | Hours |
| --- | --- | --- | --- | --- |
| Platform Product Manager | Customer (customer) | GB | lead | business |
| Platform Engineer | Customer (customer) | GB | senior | business |
| Operations Engineer | Service Provider (provider) | IN | engineer | 24x7 |
| Operations Lead | Service Provider (provider) | IN | lead | business |
| Security Operations Analyst | Service Provider (provider) | IN | senior | 24x7 |
| Platform Ops Specialist | Service Provider (provider) | PL | senior | business |
The teams, as Team Topologies names their kinds:
| Team | Kind | Party | Roles | Purpose |
| --- | --- | --- | --- | --- |
| Customer Platform Team | platform | Customer | Platform Product Manager, Platform Engineer | Owns the platform roadmap, retains network change approvals, and measures developer flow. |
| Provider Operations Team | platform | Service Provider | Operations Engineer, Operations Lead, Security Operations Analyst, Platform Ops Specialist | Provides 24x7 monitoring, incident response, and day-to-day operations of the platform foundation. |
How the teams work together:
| From | To | Mode | Until | Purpose |
| --- | --- | --- | --- | --- |
| Provider Operations Team | Customer Platform Team | x-as-a-service | | Provider requests network change approvals from the Customer Platform Team. |
| Customer Platform Team | Provider Operations Team | x-as-a-service | | Customer relies on Provider Operations Team for 24x7 incident response and monitoring. |
| Provider Operations Team | Customer Platform Team | collaboration | Month 3 after go-live, shifting to x-as-a-service. | Handover of runbooks and initial operational processes. |
| Capability | Platform Product Manager | Platform Engineer | Operations Engineer | Operations Lead | Security Operations Analyst | Platform Ops Specialist |
| --- | --- | --- | --- | --- | --- | --- |
| Incident management (C-1) | | C | R | A | | |
| Monitoring and alerting (C-2) | | C | R | A | | |
| Problem management (C-3) | | C | | A | | R |
| Service request fulfilment (C-4) | | C | R | A | | |
| Change enablement (C-5) | | A/R | | | | R |
| Release and deployment (C-6) | | A/R | | | | R |
| Configuration management (C-7) | | C | | A | | R |
| Backup and recovery (C-8) | | C | | A | | R |
| Service continuity (C-9) | | C | | A | | R |
| Capacity and performance management (C-10) | | C | | A/R | | |
| Access management (C-11) | | C | | A/R | | |
| Vulnerability and patch management (C-12) | | C | | | A/R | |
| Security monitoring and response (C-13) | | C | | | A/R | |
| Cost management (C-14) | C | | | A/R | | |
| Service level management (C-15) | C | | | A/R | | |
| Platform product management (C-16) | A/R | | | C | | |
| Self-service and golden paths (C-17) | | A/R | | | | R |
| Enablement (C-18) | | A/R | | | | R |
| Delivery and developer experience measurement (C-19) | A/R | | | C | | |
| Supplier management (C-20) | A/R | | | R | | |
| Regulatory evidence and reporting (C-21) | | C | | A | | R |
A accountable, R responsible, C consulted, I informed.
## Staffing and cost
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Platform Product Manager | Customer | GB | lead | business | 30.0 h | 0.2 | not priced |
| Platform Engineer | Customer | GB | senior | business | 35.0 h | 0.3 | not priced |
| Operations Engineer | Service Provider | IN | engineer | 24x7 | 70.0 h | 5.0 | 17,034 GBP |
| Operations Lead | Service Provider | IN | lead | business | 50.0 h | 0.3 | 1,876 GBP |
| Security Operations Analyst | Service Provider | IN | senior | 24x7 | 55.0 h | 5.0 | 24,605 GBP |
| Platform Ops Specialist | Service Provider | PL | senior | business | 90.0 h | 0.6 | 4,088 GBP |
11.4 people in all. Cost a month: 47,603 GBP.
The monthly budget is 60,000 GBP: this is within it.
Worked from rate card `rate-card`, version `draft-2026-10-13`. **Its figures are placeholders: no price has been set, and this cost is an illustration.**
Converted from USD at 0.79, a rate set on 2026-10-13.
The customer's own staff are counted and not priced. A Role that covers hours wider than a working day is never smaller than the team that can cover them.
## Validation
| Check | What must hold | Verdict | Evidence |
| --- | --- | --- | --- |
| OC-1 | A fault on the hub network or any other item is acknowledged within 15 minutes at any hour. | pass | C-1 handles incident management 24x7, with a 24x7 Operations Engineer responsible, enabling acknowledgement of faults within 15 minutes at any hour. The cloud provider's native tooling (via C-2) supports configuring alerts without requiring a separate finding. |
| OC-2 | Service is restored within 4 hours of a major failure on the platform. | pass | C-1 manages incident resolution with a 24x7 Operations Engineer responsible, allowing restoration of service within 4 hours of a major failure regardless of when the failure occurs. |
| OC-3 | The platform availability is tracked to ensure at least 99.9% uptime each month. | pass | C-15 tracks and gathers metrics on availability to ensure the 99.9% target is tracked, with business-hours roles accountable and responsible. |
| OC-4 | Capacity limits for the platform interconnect are managed to support 99.9% availability. | pass | C-10 reviews capacity trends for the interconnect to assure 99.9% availability, managed by the Operations Lead. |
| OC-5 | Every change to the hub network requires explicit approval from the customer platform team. | pass | C-5 coordinates network change approvals with the customer, and a Customer Platform Engineer is accountable and responsible for it, ensuring explicit approval from the customer platform team. |
| OC-6 | A consolidated monthly report includes service levels and operating costs. | pass | C-15 compiles the monthly operational report, pulling in cost data tracked by C-14, both managed by the Operations Lead. |
| OC-7 | The shared service model responsibilities between customer and external service provider are governed. | pass | C-20 coordinates responsibilities across shared delivery borders, with roles from both the customer and provider teams responsible. |
| OC-8a | Role performs operational delivery from India. | pass | R-3 (Operations Engineer) is based in India, satisfying the geographical requirement. |
| OC-8b | Role performs operational delivery from India. | pass | R-4 (Operations Lead) is based in India, satisfying the geographical requirement. |
| OC-8c | Role performs operational delivery from India. | pass | R-5 (Security Operations Analyst) is based in India, satisfying the geographical requirement. |
| OC-8d | Role performs operational delivery from Poland. | pass | R-6 (Platform Ops Specialist) is based in Poland, satisfying the geographical requirement. |
| OC-8e | Role performs operational delivery from the UK. | pass | R-1 (Platform Product Manager) is based in the UK, satisfying the geographical requirement. |
| OC-8f | Role performs operational delivery from the UK. | pass | R-2 (Platform Engineer) is based in the UK, satisfying the geographical requirement. |
| OC-9 | Audit log storage configuration ensures logs cannot be deleted for seven years. | pass | C-7 maintains audit log retention settings, with the Platform Ops Specialist responsible, ensuring logs cannot be deleted for seven years. |
| OC-10 | Retention policies on Cloud Storage for audit logs are verified to prevent deletion for seven years. | pass | C-7 maintains and verifies retention settings on Cloud Storage for audit logs, satisfying the seven-year retention condition. |
| OC-11 | Encryption key configurations are audited to ensure rotation every 90 days. | pass | C-7 audits configuration drift and manages key rotation schedules, ensuring encryption keys are rotated every 90 days. |
| OC-12 | Cloud KMS encryption keys are verified to rotate every 90 days. | pass | C-7 manages key rotation schedules for the Cloud KMS encryption keys, verifying they rotate every 90 days. |
| OC-13 | Deployment pipelines ensure an approved change reaches production within one day. | pass | C-6 oversees deployment pipelines to ensure approved changes reach production within a day, with customer and provider roles responsible. |
| OC-14 | Backups of audit logs and encryption keys are successfully tested for restoration. | pass | C-8 maintains backups of logs and keys and successfully tests restore procedures, managed by the Platform Ops Specialist. |
Each scenario is generated from the operating model and traced through it by code.
| Scenario | Result | Path |
| --- | --- | --- |
| Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Hub network and interconnect (S-1) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Audit log store (S-2) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Audit log store (S-2) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Deployment pipeline (S-3) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Encryption keys (S-4) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
| Encryption keys (S-4) must be changed. | pass | Platform Engineer makes the change under C-5. |
| Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. | pass | Check OC-4 on C-10 keeps it true. |
| Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. | pass | Check OC-10 on C-7 keeps it true. |
| Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. | pass | Check OC-12 on C-7 keeps it true. |
| Service Provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
| A month's cost of operating is compared with the budget of 60,000 GBP. | pass | The cost is 47,603 GBP, within the budget. |
## Findings and open questions
No findings: the solution provides what operating it needs.
Assumed for the customer, and open to change when they answer:
- `intent.exclusions`: Workload applications running on the platform foundation, Network change approvals (retained by customer platform team). Assumed from the platform foundation scope: workload applications running on the platform are out of scope, and customer platform team retains network change approvals.
- `operations.change_process`: Changes go through a deployment pipeline with peer review, with network changes requiring customer platform team approval.. Catalogue default adapted to customer requirement REQ-01: changes go through deployment pipelines with peer review, with customer platform team retaining approval over network changes.
- `service_management.tooling`: The Cloud provider's own operations tooling, with no separate system.. Catalogue default: Cloud provider's native operations tooling with no separate system.
## Sources
The Capabilities are from our own capability catalogue, which draws on these frameworks. It cites them and certifies nothing against them.
- ITIL 4: Incident management practice; Monitoring and event management practice; Problem management practice; Service request management practice; Change enablement practice; Release management and Deployment management practices; Service configuration management practice; Service continuity management practice; Capacity and performance management practice; Service level management practice; Supplier management practice
- Site Reliability Engineering: How Google Runs Production Systems: Managing Incidents; Monitoring Distributed Systems; Postmortem Culture: Learning from Failure; Release Engineering; Service Level Objectives
- ISO/IEC 20000-1: Incident management; Service request management; Change management; Service continuity management; Capacity management; Service level management; Supplier management
- Regulation (EU) 2022/2554, the Digital Operational Resilience Act: Article 17, ICT-related incident management process; Article 10, Detection; Article 12, Backup policies and procedures, restoration and recovery procedures and methods; Article 11, Response and recovery; Article 9, Protection and prevention; Article 28, General principles on ICT third-party risk; Article 19, Reporting of major ICT-related incidents
- NIST Cybersecurity Framework: Detect: Continuous Monitoring; Identify: Asset Management; Recover: Incident Recovery Plan Execution; Protect: Identity Management, Authentication, and Access Control; Protect: Platform Security; Detect: Adverse Event Analysis; Respond: Incident Management
- DevOps Research and Assessment (DORA) software delivery metrics: Change failure rate; Deployment frequency and lead time for changes; Deployment frequency; Lead time for changes; Change failure rate; Time to restore service
- ISO/IEC 27001: Access control; Management of technical vulnerabilities; Information security incident management; Compliance with legal and contractual requirements
- FinOps Framework: Allocation; Budgeting; Forecasting; Anomaly Management
- CNCF Platforms White Paper (platform as a product): Platform as a product; Measuring platform success; Platform capabilities; Self-service; Platform as a product
- Team Topologies: Organizing Business and Technology Teams for Fast Flow: Platform team; Thinnest viable platform; X-as-a-Service interaction mode; Enabling team; Facilitating interaction mode
- The SPACE of Developer Productivity: Satisfaction and well-being; Performance; Activity; Communication and collaboration; Efficiency and flow
- DevEx: What Actually Drives Productivity: Feedback loops; Cognitive load; Flow state
**These references have not been checked against the frameworks by a person.** Treat each as a pointer to where to look.

View File

@@ -0,0 +1,84 @@
[
{
"id": "OR-1",
"kind": "service_level",
"statement": "A fault on any Item is acknowledged within 15 minutes, at any hour.",
"source": [
"service_levels.priority_1_response_minutes",
"operations.support_hours"
]
},
{
"id": "OR-2",
"kind": "service_level",
"statement": "Service is restored within 4 hours of a major failure.",
"source": [
"service_levels.recovery_time_hours",
"BO-2"
]
},
{
"id": "OR-3",
"kind": "service_level",
"statement": "The platform is available at least 99.9% of each month.",
"source": [
"K-1"
]
},
{
"id": "OR-4",
"kind": "process",
"statement": "Every change to the network requires customer platform team approval prior to implementation.",
"source": [
"REQ-01"
]
},
{
"id": "OR-5",
"kind": "process",
"statement": "A report of service levels and operating costs is provided monthly.",
"source": [
"REQ-02"
]
},
{
"id": "OR-6",
"kind": "organisation",
"statement": "The platform foundation is operated under a shared service model between the customer and an external service provider.",
"source": [
"sourcing.model"
]
},
{
"id": "OR-7",
"kind": "organisation",
"statement": "Operational delivery is performed exclusively from the United Kingdom, Poland, and India.",
"source": [
"sourcing.delivery_countries"
]
},
{
"id": "OR-8",
"kind": "compliance",
"statement": "Audit logs cannot be deleted for seven years.",
"source": [
"K-2"
]
},
{
"id": "OR-9",
"kind": "process",
"statement": "Encryption keys are rotated every 90 days.",
"source": [
"K-3"
]
},
{
"id": "OR-10",
"kind": "service_level",
"statement": "An approved change reaches production within one day of approval.",
"source": [
"BO-1"
]
}
]

View File

@@ -0,0 +1,18 @@
flowchart TB
subgraph P_1["Customer (customer)"]
subgraph T_1["Customer Platform Team (platform team)"]
R_1["Platform Product Manager<br/>GB, lead, business"]
R_2["Platform Engineer<br/>GB, senior, business"]
end
end
subgraph P_2["Service Provider (provider)"]
subgraph T_2["Provider Operations Team (platform team)"]
R_3["Operations Engineer<br/>IN, engineer, 24x7"]
R_4["Operations Lead<br/>IN, lead, business"]
R_5["Security Operations Analyst<br/>IN, senior, 24x7"]
R_6["Platform Ops Specialist<br/>PL, senior, business"]
end
end
T_2 -- "x-as-a-service" --> T_1
T_1 -- "x-as-a-service" --> T_2
T_2 -- "collaboration until Month 3 after go-live, shifting to x-as-a-service." --> T_1

View File

@@ -0,0 +1,93 @@
[
{
"id": "SC-fault-S-1",
"scenario": "Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7).",
"about": "S-1",
"passes": true,
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"id": "SC-change-S-1",
"scenario": "Hub network and interconnect (S-1) must be changed.",
"about": "S-1",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-2",
"scenario": "Audit log store (S-2) fails at an hour faults are responded to (24x7).",
"about": "S-2",
"passes": true,
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"id": "SC-change-S-2",
"scenario": "Audit log store (S-2) must be changed.",
"about": "S-2",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-3",
"scenario": "Deployment pipeline (S-3) fails at an hour faults are responded to (24x7).",
"about": "S-3",
"passes": true,
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"id": "SC-change-S-3",
"scenario": "Deployment pipeline (S-3) must be changed.",
"about": "S-3",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-fault-S-4",
"scenario": "Encryption keys (S-4) fails at an hour faults are responded to (24x7).",
"about": "S-4",
"passes": true,
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"id": "SC-change-S-4",
"scenario": "Encryption keys (S-4) must be changed.",
"about": "S-4",
"passes": true,
"path": "Platform Engineer makes the change under C-5."
},
{
"id": "SC-condition-K-1",
"scenario": "Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month.",
"about": "K-1",
"passes": true,
"path": "Check OC-4 on C-10 keeps it true."
},
{
"id": "SC-condition-K-2",
"scenario": "Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years.",
"about": "K-2",
"passes": true,
"path": "Check OC-10 on C-7 keeps it true."
},
{
"id": "SC-condition-K-3",
"scenario": "Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days.",
"about": "K-3",
"passes": true,
"path": "Check OC-12 on C-7 keeps it true."
},
{
"id": "SC-party-P-2",
"scenario": "Service Provider cannot be reached.",
"about": "P-2",
"passes": true,
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
},
{
"id": "SC-budget",
"scenario": "A month's cost of operating is compared with the budget of 60,000 GBP.",
"about": "commercial.monthly_run_budget",
"passes": true,
"path": "The cost is 47,603 GBP, within the budget."
}
]

View File

@@ -0,0 +1,203 @@
{
"kind": "platform_foundation",
"stated": {
"engagement": {
"kind": "platform_foundation"
},
"intent": {
"statement": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.\n",
"requirements": [
{
"id": "REQ-01",
"statement": "Our platform team approves every change to the network."
},
{
"id": "REQ-02",
"statement": "We receive a monthly report of service levels and cost."
}
],
"business_outcomes": [
{
"id": "BO-1",
"outcome": "New payment products reach customers in weeks rather than months.",
"target": "A change reaches production within a day of approval."
},
{
"id": "BO-2",
"outcome": "Payments are never unavailable for long.",
"target": "Restored within 4 hours."
},
{
"id": "BO-3",
"outcome": "We keep the platform engineers we hire."
}
]
},
"solution": {
"cloud_provider": "gcp",
"items": [
{
"id": "S-1",
"name": "Hub network and interconnect",
"kind": "network",
"product": "Cloud Interconnect"
},
{
"id": "S-2",
"name": "Audit log store",
"kind": "storage",
"product": "Cloud Storage"
},
{
"id": "S-3",
"name": "Deployment pipeline",
"kind": "pipeline",
"product": "Cloud Build"
},
{
"id": "S-4",
"name": "Encryption keys",
"kind": "keys",
"product": "Cloud KMS"
}
],
"conditions": [
{
"id": "K-1",
"on": [
"S-1"
],
"condition": "The platform is available at least 99.9% of each month."
},
{
"id": "K-2",
"on": [
"S-2"
],
"condition": "Audit logs cannot be deleted for seven years."
},
{
"id": "K-3",
"on": [
"S-4"
],
"condition": "Encryption keys are rotated every 90 days."
}
],
"build": {
"duration_days": 36
}
},
"operations": {
"support_hours": "24x7",
"availability_hours": "24x7"
},
"sourcing": {
"model": "shared",
"delivery_countries": [
"GB",
"PL",
"IN"
]
},
"organisation": {
"existing_teams": [
{
"name": "Platform team",
"party": "customer",
"hours": "business",
"country": "GB"
}
]
},
"service_levels": {
"priority_1_response_minutes": 15,
"recovery_time_hours": 4
},
"compliance": {
"frameworks": [
"DORA"
]
},
"commercial": {
"currency": "GBP",
"monthly_run_budget": 60000
}
},
"binding": [
"operations.support_hours",
"sourcing.model",
"sourcing.delivery_countries",
"service_levels.priority_1_response_minutes",
"service_levels.recovery_time_hours"
],
"assumed": [
{
"field": "intent.exclusions",
"value": [
"Workload applications running on the platform foundation",
"Network change approvals (retained by customer platform team)"
],
"why": "Assumed from the platform foundation scope: workload applications running on the platform are out of scope, and customer platform team retains network change approvals."
},
{
"field": "operations.change_process",
"value": "Changes go through a deployment pipeline with peer review, with network changes requiring customer platform team approval.",
"why": "Catalogue default adapted to customer requirement REQ-01: changes go through deployment pipelines with peer review, with customer platform team retaining approval over network changes."
},
{
"field": "service_management.tooling",
"value": "The Cloud provider's own operations tooling, with no separate system.",
"why": "Catalogue default: Cloud provider's native operations tooling with no separate system."
}
],
"to_decide": [],
"to_ask": [
{
"field": "metadata.client_name",
"prompt": "What is metadata.client_name?",
"severity": "LOW"
},
{
"field": "metadata.author",
"prompt": "What is metadata.author?",
"severity": "LOW"
},
{
"field": "metadata.revision",
"prompt": "What is metadata.revision?",
"severity": "LOW"
},
{
"field": "metadata.source",
"prompt": "What is metadata.source?",
"severity": "LOW"
},
{
"field": "solution.build.customer_owned",
"prompt": "Which parts of the build does the customer or their supplier own?",
"severity": "LOW"
},
{
"field": "solution.inherited_risks",
"prompt": "What is already known to be unverified or at risk in the solution?",
"severity": "LOW"
},
{
"field": "operations.monitoring",
"prompt": "Which monitoring and alerting is already in place or required?",
"severity": "LOW"
},
{
"field": "organisation.headcount_limit",
"prompt": "Is there a limit on the number of people operating this?",
"severity": "LOW"
},
{
"field": "transition.go_live_date",
"prompt": "When must the solution be in operation?",
"severity": "LOW"
}
],
"not_applicable": []
}

View File

@@ -0,0 +1,201 @@
schema_version: 1
metadata:
customer_case: bench-landing-zone-shared
client_name: ask
author: ask
revision: ask
source: ask
status: BASELINE_LOCKED
engagement:
kind: platform_foundation
intent:
statement: 'We want our landing zone run as a shared service from go-live. A provider
should
respond to faults at every hour, and our own platform team keeps the final say
over changes to the network.
'
requirements:
- id: REQ-01
statement: Our platform team approves every change to the network.
- id: REQ-02
statement: We receive a monthly report of service levels and cost.
business_outcomes:
- id: BO-1
outcome: New payment products reach customers in weeks rather than months.
target: A change reaches production within a day of approval.
- id: BO-2
outcome: Payments are never unavailable for long.
target: Restored within 4 hours.
- id: BO-3
outcome: We keep the platform engineers we hire.
exclusions:
- Workload applications running on the platform foundation
- Network change approvals (retained by customer platform team)
solution:
cloud_provider: gcp
items:
- id: S-1
name: Hub network and interconnect
kind: network
product: Cloud Interconnect
- id: S-2
name: Audit log store
kind: storage
product: Cloud Storage
- id: S-3
name: Deployment pipeline
kind: pipeline
product: Cloud Build
- id: S-4
name: Encryption keys
kind: keys
product: Cloud KMS
conditions:
- id: K-1
'on':
- S-1
condition: The platform is available at least 99.9% of each month.
- id: K-2
'on':
- S-2
condition: Audit logs cannot be deleted for seven years.
- id: K-3
'on':
- S-4
condition: Encryption keys are rotated every 90 days.
build:
duration_days: 36
customer_owned: ask
inherited_risks: ask
operations:
support_hours: 24x7
availability_hours: 24x7
change_process: Changes go through a deployment pipeline with peer review, with
network changes requiring customer platform team approval.
monitoring: ask
sourcing:
model: shared
delivery_countries:
- GB
- PL
- IN
organisation:
existing_teams:
- name: Platform team
party: customer
hours: business
country: GB
headcount_limit: ask
service_management:
tooling: The Cloud provider's own operations tooling, with no separate system.
service_levels:
priority_1_response_minutes: 15
recovery_time_hours: 4
compliance:
frameworks:
- DORA
commercial:
currency: GBP
monthly_run_budget: 60000
transition:
go_live_date: ask
run:
pre_approved: true
overlay_skills: ask
inferred_assumptions:
- id: ASSUMP-01
field: intent.exclusions
statement: 'Assumed intent.exclusions is [''Workload applications running on the
platform foundation'', ''Network change approvals (retained by customer platform
team)'']. Assumed from the platform foundation scope: workload applications running
on the platform are out of scope, and customer platform team retains network change
approvals.'
impact_if_invalid: Changes which Capabilities are designed.
- id: ASSUMP-02
field: operations.change_process
statement: 'Assumed operations.change_process is Changes go through a deployment
pipeline with peer review, with network changes requiring customer platform team
approval.. Catalogue default adapted to customer requirement REQ-01: changes go
through deployment pipelines with peer review, with customer platform team retaining
approval over network changes.'
impact_if_invalid: Changes change enablement and release.
- id: ASSUMP-03
field: service_management.tooling
statement: 'Assumed service_management.tooling is The Cloud provider''s own operations
tooling, with no separate system.. Catalogue default: Cloud provider''s native
operations tooling with no separate system.'
impact_if_invalid: Changes tooling and the processes written for it.
discovery_gaps:
- field: metadata.client_name
prompt: What is metadata.client_name?
severity: LOW
- field: metadata.author
prompt: What is metadata.author?
severity: LOW
- field: metadata.revision
prompt: What is metadata.revision?
severity: LOW
- field: metadata.source
prompt: What is metadata.source?
severity: LOW
- field: solution.build.customer_owned
prompt: Which parts of the build does the customer or their supplier own?
severity: LOW
- field: solution.inherited_risks
prompt: What is already known to be unverified or at risk in the solution?
severity: LOW
- field: operations.monitoring
prompt: Which monitoring and alerting is already in place or required?
severity: LOW
- field: organisation.headcount_limit
prompt: Is there a limit on the number of people operating this?
severity: LOW
- field: transition.go_live_date
prompt: When must the solution be in operation?
severity: LOW
- field: run.overlay_skills
prompt: Which overlay Skills should this Execution load?
severity: LOW
provenance:
commercial.currency: supplied
commercial.monthly_run_budget: supplied
compliance.frameworks: supplied
engagement.kind: supplied
intent.business_outcomes: supplied
intent.exclusions: assumed
intent.requirements: supplied
intent.statement: supplied
metadata.author: unknown
metadata.client_name: unknown
metadata.customer_case: supplied
metadata.revision: unknown
metadata.source: unknown
operations.availability_hours: supplied
operations.change_process: assumed
operations.monitoring: unknown
operations.support_hours: supplied
organisation.existing_teams: supplied
organisation.headcount_limit: unknown
run.overlay_skills: unknown
run.pre_approved: supplied
service_levels.priority_1_response_minutes: supplied
service_levels.recovery_time_hours: supplied
service_management.tooling: assumed
solution.build.customer_owned: unknown
solution.build.duration_days: supplied
solution.cloud_provider: supplied
solution.conditions: supplied
solution.inherited_risks: unknown
solution.items: supplied
sourcing.delivery_countries: supplied
sourcing.model: supplied
transition.go_live_date: unknown
readiness:
supplied: 20
answered: 0
assumed: 3
unknown: 10
not_applicable: 0

View File

@@ -0,0 +1,117 @@
{
"currency": "GBP",
"rate_card": {
"name": "rate-card",
"version": "draft-2026-10-13",
"draft": true
},
"conversion": {
"from": "USD",
"rate": 0.79,
"as_of": "2026-10-13"
},
"roles": [
{
"role": "R-1",
"name": "Platform Product Manager",
"party": "P-1",
"party_name": "Customer",
"country": "GB",
"level": "lead",
"hours": "business",
"effort_hours_per_month": 30.0,
"people": 0.2,
"cost_per_month": null
},
{
"role": "R-2",
"name": "Platform Engineer",
"party": "P-1",
"party_name": "Customer",
"country": "GB",
"level": "senior",
"hours": "business",
"effort_hours_per_month": 35.0,
"people": 0.3,
"cost_per_month": null
},
{
"role": "R-3",
"name": "Operations Engineer",
"party": "P-2",
"party_name": "Service Provider",
"country": "IN",
"level": "engineer",
"hours": "24x7",
"effort_hours_per_month": 70.0,
"people": 5.0,
"cost_per_month": 17034
},
{
"role": "R-4",
"name": "Operations Lead",
"party": "P-2",
"party_name": "Service Provider",
"country": "IN",
"level": "lead",
"hours": "business",
"effort_hours_per_month": 50.0,
"people": 0.3,
"cost_per_month": 1876
},
{
"role": "R-5",
"name": "Security Operations Analyst",
"party": "P-2",
"party_name": "Service Provider",
"country": "IN",
"level": "senior",
"hours": "24x7",
"effort_hours_per_month": 55.0,
"people": 5.0,
"cost_per_month": 24605
},
{
"role": "R-6",
"name": "Platform Ops Specialist",
"party": "P-2",
"party_name": "Service Provider",
"country": "PL",
"level": "senior",
"hours": "business",
"effort_hours_per_month": 90.0,
"people": 0.6,
"cost_per_month": 4088
}
],
"people": 11.4,
"cost_per_month": 47603,
"by_party": {
"P-2": 47603
},
"by_country": {
"IN": 43515,
"PL": 4088
},
"by_capability": {
"C-1": 7300,
"C-2": 4867,
"C-4": 4867,
"C-10": 375,
"C-11": 563,
"C-14": 375,
"C-15": 375,
"C-20": 188,
"C-12": 6711,
"C-13": 17895,
"C-3": 454,
"C-5": 227,
"C-6": 454,
"C-7": 681,
"C-8": 454,
"C-9": 454,
"C-17": 454,
"C-18": 454,
"C-21": 454
}
}

View File

@@ -0,0 +1,642 @@
{
"parties": [
{
"kind": "customer",
"name": "Customer",
"id": "P-1"
},
{
"kind": "provider",
"name": "Service Provider",
"id": "P-2"
}
],
"teams": [
{
"purpose": "Owns the platform roadmap, retains network change approvals, and measures developer flow.",
"id": "T-1",
"party": "P-1",
"type": "platform",
"name": "Customer Platform Team"
},
{
"id": "T-2",
"name": "Provider Operations Team",
"type": "platform",
"party": "P-2",
"purpose": "Provides 24x7 monitoring, incident response, and day-to-day operations of the platform foundation."
}
],
"roles": [
{
"party": "P-1",
"id": "R-1",
"hours": "business",
"team": "T-1",
"name": "Platform Product Manager",
"level": "lead",
"country": "GB"
},
{
"party": "P-1",
"hours": "business",
"team": "T-1",
"level": "senior",
"id": "R-2",
"name": "Platform Engineer",
"country": "GB"
},
{
"level": "engineer",
"hours": "24x7",
"party": "P-2",
"name": "Operations Engineer",
"team": "T-2",
"id": "R-3",
"country": "IN"
},
{
"country": "IN",
"level": "lead",
"id": "R-4",
"name": "Operations Lead",
"hours": "business",
"team": "T-2",
"party": "P-2"
},
{
"level": "senior",
"party": "P-2",
"id": "R-5",
"hours": "24x7",
"name": "Security Operations Analyst",
"country": "IN",
"team": "T-2"
},
{
"id": "R-6",
"name": "Platform Ops Specialist",
"country": "PL",
"level": "senior",
"hours": "business",
"team": "T-2",
"party": "P-2"
}
],
"interactions": [
{
"to": "T-1",
"mode": "x_as_a_service",
"from": "T-2",
"purpose": "Provider requests network change approvals from the Customer Platform Team.",
"id": "I-1"
},
{
"id": "I-2",
"mode": "x_as_a_service",
"to": "T-2",
"purpose": "Customer relies on Provider Operations Team for 24x7 incident response and monitoring.",
"from": "T-1"
},
{
"from": "T-2",
"to": "T-1",
"purpose": "Handover of runbooks and initial operational processes.",
"mode": "collaboration",
"until": "Month 3 after go-live, shifting to x-as-a-service.",
"id": "I-3"
}
],
"measures": [
{
"framework": "dora-metrics",
"name": "Deployment frequency",
"outcome": "BO-1",
"layer": "outcome",
"id": "M-1",
"target": "A change reaches production within a day of approval.",
"measured_by": "C-19"
},
{
"outcome": "BO-3",
"id": "M-2",
"name": "Developer satisfaction",
"layer": "guardrail",
"measured_by": "C-19",
"framework": "space-framework"
},
{
"measured_by": "C-19",
"outcome": "BO-1",
"framework": "devex-framework",
"name": "Friction and cognitive load",
"id": "M-3",
"layer": "leading"
},
{
"layer": "outcome",
"outcome": "BO-2",
"measured_by": "C-1",
"target": "Restored within 4 hours.",
"name": "Time to restore service",
"framework": "dora-metrics",
"id": "M-4"
}
],
"responsibilities": [
{
"id": "RS-1-acc",
"capability": "C-1",
"kind": "accountable",
"role": "R-4"
},
{
"id": "RS-1-res",
"kind": "responsible",
"role": "R-3",
"capability": "C-1"
},
{
"id": "RS-1-con",
"capability": "C-1",
"role": "R-2",
"kind": "consulted"
},
{
"id": "RS-2-acc",
"role": "R-4",
"capability": "C-2",
"kind": "accountable"
},
{
"capability": "C-2",
"id": "RS-2-res",
"kind": "responsible",
"role": "R-3"
},
{
"capability": "C-2",
"role": "R-2",
"kind": "consulted",
"id": "RS-2-con"
},
{
"kind": "accountable",
"role": "R-4",
"capability": "C-3",
"id": "RS-3-acc"
},
{
"role": "R-6",
"kind": "responsible",
"id": "RS-3-res",
"capability": "C-3"
},
{
"capability": "C-3",
"role": "R-2",
"id": "RS-3-con",
"kind": "consulted"
},
{
"role": "R-4",
"kind": "accountable",
"capability": "C-4",
"id": "RS-4-acc"
},
{
"kind": "responsible",
"role": "R-3",
"capability": "C-4",
"id": "RS-4-res"
},
{
"kind": "consulted",
"role": "R-2",
"id": "RS-4-con",
"capability": "C-4"
},
{
"id": "RS-5-acc",
"role": "R-2",
"kind": "accountable",
"capability": "C-5"
},
{
"role": "R-2",
"kind": "responsible",
"capability": "C-5",
"id": "RS-5-res1"
},
{
"kind": "responsible",
"role": "R-6",
"id": "RS-5-res2",
"capability": "C-5"
},
{
"capability": "C-6",
"role": "R-2",
"id": "RS-6-acc",
"kind": "accountable"
},
{
"capability": "C-6",
"id": "RS-6-res1",
"kind": "responsible",
"role": "R-2"
},
{
"role": "R-6",
"id": "RS-6-res2",
"kind": "responsible",
"capability": "C-6"
},
{
"role": "R-4",
"id": "RS-7-acc",
"capability": "C-7",
"kind": "accountable"
},
{
"kind": "responsible",
"capability": "C-7",
"id": "RS-7-res",
"role": "R-6"
},
{
"capability": "C-7",
"role": "R-2",
"id": "RS-7-con",
"kind": "consulted"
},
{
"kind": "accountable",
"role": "R-4",
"id": "RS-8-acc",
"capability": "C-8"
},
{
"role": "R-6",
"capability": "C-8",
"id": "RS-8-res",
"kind": "responsible"
},
{
"role": "R-2",
"capability": "C-8",
"kind": "consulted",
"id": "RS-8-con"
},
{
"role": "R-4",
"id": "RS-9-acc",
"capability": "C-9",
"kind": "accountable"
},
{
"kind": "responsible",
"role": "R-6",
"capability": "C-9",
"id": "RS-9-res"
},
{
"id": "RS-9-con",
"role": "R-2",
"kind": "consulted",
"capability": "C-9"
},
{
"id": "RS-10-acc",
"kind": "accountable",
"capability": "C-10",
"role": "R-4"
},
{
"kind": "responsible",
"id": "RS-10-res",
"capability": "C-10",
"role": "R-4"
},
{
"kind": "consulted",
"id": "RS-10-con",
"role": "R-2",
"capability": "C-10"
},
{
"capability": "C-11",
"role": "R-4",
"id": "RS-11-acc",
"kind": "accountable"
},
{
"capability": "C-11",
"role": "R-4",
"id": "RS-11-res",
"kind": "responsible"
},
{
"kind": "consulted",
"capability": "C-11",
"id": "RS-11-con",
"role": "R-2"
},
{
"kind": "accountable",
"id": "RS-12-acc",
"role": "R-5",
"capability": "C-12"
},
{
"capability": "C-12",
"kind": "responsible",
"id": "RS-12-res",
"role": "R-5"
},
{
"kind": "consulted",
"role": "R-2",
"capability": "C-12",
"id": "RS-12-con"
},
{
"capability": "C-13",
"kind": "accountable",
"role": "R-5",
"id": "RS-13-acc"
},
{
"id": "RS-13-res",
"capability": "C-13",
"kind": "responsible",
"role": "R-5"
},
{
"id": "RS-13-con",
"capability": "C-13",
"role": "R-2",
"kind": "consulted"
},
{
"kind": "accountable",
"role": "R-4",
"capability": "C-14",
"id": "RS-14-acc"
},
{
"id": "RS-14-res",
"capability": "C-14",
"role": "R-4",
"kind": "responsible"
},
{
"kind": "consulted",
"role": "R-1",
"capability": "C-14",
"id": "RS-14-con"
},
{
"capability": "C-15",
"kind": "accountable",
"id": "RS-15-acc",
"role": "R-4"
},
{
"id": "RS-15-res",
"kind": "responsible",
"capability": "C-15",
"role": "R-4"
},
{
"capability": "C-15",
"id": "RS-15-con",
"role": "R-1",
"kind": "consulted"
},
{
"kind": "accountable",
"role": "R-1",
"id": "RS-16-acc",
"capability": "C-16"
},
{
"id": "RS-16-res",
"capability": "C-16",
"role": "R-1",
"kind": "responsible"
},
{
"id": "RS-16-con",
"role": "R-4",
"kind": "consulted",
"capability": "C-16"
},
{
"id": "RS-17-acc",
"role": "R-2",
"kind": "accountable",
"capability": "C-17"
},
{
"kind": "responsible",
"role": "R-2",
"id": "RS-17-res1",
"capability": "C-17"
},
{
"capability": "C-17",
"kind": "responsible",
"role": "R-6",
"id": "RS-17-res2"
},
{
"capability": "C-18",
"role": "R-2",
"id": "RS-18-acc",
"kind": "accountable"
},
{
"kind": "responsible",
"role": "R-2",
"id": "RS-18-res1",
"capability": "C-18"
},
{
"role": "R-6",
"kind": "responsible",
"capability": "C-18",
"id": "RS-18-res2"
},
{
"capability": "C-19",
"kind": "accountable",
"role": "R-1",
"id": "RS-19-acc"
},
{
"role": "R-1",
"capability": "C-19",
"id": "RS-19-res",
"kind": "responsible"
},
{
"id": "RS-19-con",
"role": "R-4",
"kind": "consulted",
"capability": "C-19"
},
{
"role": "R-1",
"id": "RS-20-acc",
"capability": "C-20",
"kind": "accountable"
},
{
"role": "R-1",
"capability": "C-20",
"id": "RS-20-res1",
"kind": "responsible"
},
{
"kind": "responsible",
"capability": "C-20",
"role": "R-4",
"id": "RS-20-res2"
},
{
"kind": "accountable",
"capability": "C-21",
"id": "RS-21-acc",
"role": "R-4"
},
{
"role": "R-6",
"id": "RS-21-res",
"capability": "C-21",
"kind": "responsible"
},
{
"role": "R-2",
"id": "RS-21-con",
"capability": "C-21",
"kind": "consulted"
}
],
"checks": [
{
"source": "OR-1",
"id": "OC-1",
"condition": "A fault on the hub network or any other item is acknowledged within 15 minutes at any hour.",
"on": "C-1"
},
{
"condition": "Service is restored within 4 hours of a major failure on the platform.",
"on": "C-1",
"source": "OR-2",
"id": "OC-2"
},
{
"on": "C-15",
"condition": "The platform availability is tracked to ensure at least 99.9% uptime each month.",
"source": "OR-3",
"id": "OC-3"
},
{
"source": "K-1",
"id": "OC-4",
"condition": "Capacity limits for the platform interconnect are managed to support 99.9% availability.",
"on": "C-10"
},
{
"source": "OR-4",
"condition": "Every change to the hub network requires explicit approval from the customer platform team.",
"id": "OC-5",
"on": "C-5"
},
{
"condition": "A consolidated monthly report includes service levels and operating costs.",
"source": "OR-5",
"on": "C-15",
"id": "OC-6"
},
{
"source": "OR-6",
"id": "OC-7",
"condition": "The shared service model responsibilities between customer and external service provider are governed.",
"on": "C-20"
},
{
"on": "R-3",
"id": "OC-8a",
"source": "OR-7",
"condition": "Role performs operational delivery from India."
},
{
"condition": "Role performs operational delivery from India.",
"id": "OC-8b",
"source": "OR-7",
"on": "R-4"
},
{
"source": "OR-7",
"id": "OC-8c",
"condition": "Role performs operational delivery from India.",
"on": "R-5"
},
{
"condition": "Role performs operational delivery from Poland.",
"id": "OC-8d",
"on": "R-6",
"source": "OR-7"
},
{
"condition": "Role performs operational delivery from the UK.",
"source": "OR-7",
"id": "OC-8e",
"on": "R-1"
},
{
"condition": "Role performs operational delivery from the UK.",
"on": "R-2",
"source": "OR-7",
"id": "OC-8f"
},
{
"on": "C-7",
"source": "OR-8",
"condition": "Audit log storage configuration ensures logs cannot be deleted for seven years.",
"id": "OC-9"
},
{
"condition": "Retention policies on Cloud Storage for audit logs are verified to prevent deletion for seven years.",
"source": "K-2",
"id": "OC-10",
"on": "C-7"
},
{
"condition": "Encryption key configurations are audited to ensure rotation every 90 days.",
"source": "OR-9",
"id": "OC-11",
"on": "C-7"
},
{
"on": "C-7",
"id": "OC-12",
"source": "K-3",
"condition": "Cloud KMS encryption keys are verified to rotate every 90 days."
},
{
"on": "C-6",
"id": "OC-13",
"source": "OR-10",
"condition": "Deployment pipelines ensure an approved change reaches production within one day."
},
{
"condition": "Backups of audit logs and encryption keys are successfully tested for restoration.",
"id": "OC-14",
"source": "OR-2",
"on": "C-8"
}
]
}

View File

@@ -0,0 +1,169 @@
{
"dry_run": {
"verdict": "pass",
"evidence": "13 of 13 scenario walk-throughs pass."
},
"checks": [
{
"check": "OC-1",
"evidence": "C-1 handles incident management 24x7, with a 24x7 Operations Engineer responsible, enabling acknowledgement of faults within 15 minutes at any hour. The cloud provider's native tooling (via C-2) supports configuring alerts without requiring a separate finding.",
"verdict": "pass"
},
{
"evidence": "C-1 manages incident resolution with a 24x7 Operations Engineer responsible, allowing restoration of service within 4 hours of a major failure regardless of when the failure occurs.",
"check": "OC-2",
"verdict": "pass"
},
{
"verdict": "pass",
"evidence": "C-15 tracks and gathers metrics on availability to ensure the 99.9% target is tracked, with business-hours roles accountable and responsible.",
"check": "OC-3"
},
{
"verdict": "pass",
"evidence": "C-10 reviews capacity trends for the interconnect to assure 99.9% availability, managed by the Operations Lead.",
"check": "OC-4"
},
{
"evidence": "C-5 coordinates network change approvals with the customer, and a Customer Platform Engineer is accountable and responsible for it, ensuring explicit approval from the customer platform team.",
"check": "OC-5",
"verdict": "pass"
},
{
"verdict": "pass",
"check": "OC-6",
"evidence": "C-15 compiles the monthly operational report, pulling in cost data tracked by C-14, both managed by the Operations Lead."
},
{
"verdict": "pass",
"check": "OC-7",
"evidence": "C-20 coordinates responsibilities across shared delivery borders, with roles from both the customer and provider teams responsible."
},
{
"check": "OC-8a",
"evidence": "R-3 (Operations Engineer) is based in India, satisfying the geographical requirement.",
"verdict": "pass"
},
{
"evidence": "R-4 (Operations Lead) is based in India, satisfying the geographical requirement.",
"check": "OC-8b",
"verdict": "pass"
},
{
"verdict": "pass",
"check": "OC-8c",
"evidence": "R-5 (Security Operations Analyst) is based in India, satisfying the geographical requirement."
},
{
"check": "OC-8d",
"verdict": "pass",
"evidence": "R-6 (Platform Ops Specialist) is based in Poland, satisfying the geographical requirement."
},
{
"check": "OC-8e",
"evidence": "R-1 (Platform Product Manager) is based in the UK, satisfying the geographical requirement.",
"verdict": "pass"
},
{
"check": "OC-8f",
"verdict": "pass",
"evidence": "R-2 (Platform Engineer) is based in the UK, satisfying the geographical requirement."
},
{
"evidence": "C-7 maintains audit log retention settings, with the Platform Ops Specialist responsible, ensuring logs cannot be deleted for seven years.",
"check": "OC-9",
"verdict": "pass"
},
{
"check": "OC-10",
"verdict": "pass",
"evidence": "C-7 maintains and verifies retention settings on Cloud Storage for audit logs, satisfying the seven-year retention condition."
},
{
"check": "OC-11",
"verdict": "pass",
"evidence": "C-7 audits configuration drift and manages key rotation schedules, ensuring encryption keys are rotated every 90 days."
},
{
"verdict": "pass",
"evidence": "C-7 manages key rotation schedules for the Cloud KMS encryption keys, verifying they rotate every 90 days.",
"check": "OC-12"
},
{
"check": "OC-13",
"verdict": "pass",
"evidence": "C-6 oversees deployment pipelines to ensure approved changes reach production within a day, with customer and provider roles responsible."
},
{
"evidence": "C-8 maintains backups of logs and keys and successfully tests restore procedures, managed by the Platform Ops Specialist.",
"check": "OC-14",
"verdict": "pass"
},
{
"check": "SC-fault-S-1",
"verdict": "pass",
"evidence": "Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"check": "SC-change-S-1",
"verdict": "pass",
"evidence": "Hub network and interconnect (S-1) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-2",
"verdict": "pass",
"evidence": "Audit log store (S-2) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"check": "SC-change-S-2",
"verdict": "pass",
"evidence": "Audit log store (S-2) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-3",
"verdict": "pass",
"evidence": "Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"check": "SC-change-S-3",
"verdict": "pass",
"evidence": "Deployment pipeline (S-3) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-fault-S-4",
"verdict": "pass",
"evidence": "Encryption keys (S-4) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
},
{
"check": "SC-change-S-4",
"verdict": "pass",
"evidence": "Encryption keys (S-4) must be changed. Platform Engineer makes the change under C-5."
},
{
"check": "SC-condition-K-1",
"verdict": "pass",
"evidence": "Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. Check OC-4 on C-10 keeps it true."
},
{
"check": "SC-condition-K-2",
"verdict": "pass",
"evidence": "Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. Check OC-10 on C-7 keeps it true."
},
{
"check": "SC-condition-K-3",
"verdict": "pass",
"evidence": "Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. Check OC-12 on C-7 keeps it true."
},
{
"check": "SC-party-P-2",
"verdict": "pass",
"evidence": "Service Provider cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
},
{
"check": "SC-budget",
"verdict": "pass",
"evidence": "A month's cost of operating is compared with the budget of 60,000 GBP. The cost is 47,603 GBP, within the budget."
}
],
"proposed_additions": []
}

View File

@@ -0,0 +1,10 @@
# Intent 1: bench-landing-zone-shared
- Recorded: 2026-10-21T20:36:25+00:00
- Execution: `case-01-landing-zone-shared-r1`
## What the customer wants
We want our landing zone run as a shared service from go-live. A provider should
respond to faults at every hour, and our own platform team keeps the final say
over changes to the network.

View File

@@ -0,0 +1,198 @@
schema_version: 1
metadata:
customer_case: bench-landing-zone-shared
client_name: ask
author: ask
revision: ask
source: ask
status: BASELINE_LOCKED
engagement:
kind: platform_foundation
intent:
statement: 'We want our landing zone run as a shared service from go-live. A provider
should
respond to faults at every hour, and our own platform team keeps the final say
over changes to the network.
'
requirements:
- id: REQ-01
statement: Our platform team approves every change to the network.
- id: REQ-02
statement: We receive a monthly report of service levels and cost.
business_outcomes:
- id: BO-1
outcome: New payment products reach customers in weeks rather than months.
target: A change reaches production within a day of approval.
- id: BO-2
outcome: Payments are never unavailable for long.
target: Restored within 4 hours.
- id: BO-3
outcome: We keep the platform engineers we hire.
exclusions:
- Application workloads and services hosted on the platform foundation
solution:
cloud_provider: gcp
items:
- id: S-1
name: Hub network and interconnect
kind: network
product: Cloud Interconnect
- id: S-2
name: Audit log store
kind: storage
product: Cloud Storage
- id: S-3
name: Deployment pipeline
kind: pipeline
product: Cloud Build
- id: S-4
name: Encryption keys
kind: keys
product: Cloud KMS
conditions:
- id: K-1
'on':
- S-1
condition: The platform is available at least 99.9% of each month.
- id: K-2
'on':
- S-2
condition: Audit logs cannot be deleted for seven years.
- id: K-3
'on':
- S-4
condition: Encryption keys are rotated every 90 days.
build:
duration_days: 36
customer_owned: ask
inherited_risks: ask
operations:
support_hours: 24x7
availability_hours: 24x7
change_process: Changes go through a deployment pipeline with peer review, with
explicit customer platform team approval required for all network changes.
monitoring: ask
sourcing:
model: shared
delivery_countries:
- GB
- PL
- IN
organisation:
existing_teams:
- name: Platform team
party: customer
hours: business
country: GB
headcount_limit: ask
service_management:
tooling: Google Cloud operations suite and native Cloud provider tooling, with no
separate external ITSM system.
service_levels:
priority_1_response_minutes: 15
recovery_time_hours: 4
compliance:
frameworks:
- DORA
commercial:
currency: GBP
monthly_run_budget: 60000
transition:
go_live_date: ask
run:
pre_approved: true
overlay_skills: ask
inferred_assumptions:
- id: ASSUMP-01
field: intent.exclusions
statement: 'Assumed intent.exclusions is [''Application workloads and services hosted
on the platform foundation'']. Assumed based on platform foundation scope: workloads
hosted on top of the landing zone are out of scope for this operating model.'
impact_if_invalid: Changes which Capabilities are designed.
- id: ASSUMP-02
field: operations.change_process
statement: Assumed operations.change_process is Changes go through a deployment
pipeline with peer review, with explicit customer platform team approval required
for all network changes.. Pipeline-driven changes with peer review, with customer
platform team approval required for network changes per REQ-01.
impact_if_invalid: Changes change enablement and release.
- id: ASSUMP-03
field: service_management.tooling
statement: Assumed service_management.tooling is Google Cloud operations suite and
native Cloud provider tooling, with no separate external ITSM system.. Default
native GCP operations tooling used as no external ITSM was specified.
impact_if_invalid: Changes tooling and the processes written for it.
discovery_gaps:
- field: metadata.client_name
prompt: What is metadata.client_name?
severity: LOW
- field: metadata.author
prompt: What is metadata.author?
severity: LOW
- field: metadata.revision
prompt: What is metadata.revision?
severity: LOW
- field: metadata.source
prompt: What is metadata.source?
severity: LOW
- field: solution.build.customer_owned
prompt: Which parts of the build does the customer or their supplier own?
severity: LOW
- field: solution.inherited_risks
prompt: What is already known to be unverified or at risk in the solution?
severity: LOW
- field: operations.monitoring
prompt: Which monitoring and alerting is already in place or required?
severity: LOW
- field: organisation.headcount_limit
prompt: Is there a limit on the number of people operating this?
severity: LOW
- field: transition.go_live_date
prompt: When must the solution be in operation?
severity: LOW
- field: run.overlay_skills
prompt: Which overlay Skills should this Execution load?
severity: LOW
provenance:
commercial.currency: supplied
commercial.monthly_run_budget: supplied
compliance.frameworks: supplied
engagement.kind: supplied
intent.business_outcomes: supplied
intent.exclusions: assumed
intent.requirements: supplied
intent.statement: supplied
metadata.author: unknown
metadata.client_name: unknown
metadata.customer_case: supplied
metadata.revision: unknown
metadata.source: unknown
operations.availability_hours: supplied
operations.change_process: assumed
operations.monitoring: unknown
operations.support_hours: supplied
organisation.existing_teams: supplied
organisation.headcount_limit: unknown
run.overlay_skills: unknown
run.pre_approved: supplied
service_levels.priority_1_response_minutes: supplied
service_levels.recovery_time_hours: supplied
service_management.tooling: assumed
solution.build.customer_owned: unknown
solution.build.duration_days: supplied
solution.cloud_provider: supplied
solution.conditions: supplied
solution.inherited_risks: unknown
solution.items: supplied
sourcing.delivery_countries: supplied
sourcing.model: supplied
transition.go_live_date: unknown
readiness:
supplied: 20
answered: 0
assumed: 3
unknown: 10
not_applicable: 0

View File

@@ -0,0 +1,53 @@
# A fictional benchmark: a small landing zone run as a shared service. No customer's
# data is in it. Complete enough to run with nobody to ask.
metadata:
customer_case: bench-landing-zone-shared
engagement:
kind: platform_foundation
intent:
statement: |
We want our landing zone run as a shared service from go-live. A provider should
respond to faults at every hour, and our own platform team keeps the final say
over changes to the network.
business_outcomes:
- {id: BO-1, outcome: New payment products reach customers in weeks rather than months., target: "A change reaches production within a day of approval."}
- {id: BO-2, outcome: Payments are never unavailable for long., target: "Restored within 4 hours."}
- {id: BO-3, outcome: We keep the platform engineers we hire.}
requirements:
- {id: REQ-01, statement: Our platform team approves every change to the network.}
- {id: REQ-02, statement: We receive a monthly report of service levels and cost.}
solution:
cloud_provider: gcp
items:
- {id: S-1, name: Hub network and interconnect, kind: network, product: Cloud Interconnect}
- {id: S-2, name: Audit log store, kind: storage, product: Cloud Storage}
- {id: S-3, name: Deployment pipeline, kind: pipeline, product: Cloud Build}
- {id: S-4, name: Encryption keys, kind: keys, product: Cloud KMS}
conditions:
- {id: K-1, "on": [S-1], condition: The platform is available at least 99.9% of each month.}
- {id: K-2, "on": [S-2], condition: Audit logs cannot be deleted for seven years.}
- {id: K-3, "on": [S-4], condition: Encryption keys are rotated every 90 days.}
build:
duration_days: 36
operations:
support_hours: 24x7
availability_hours: 24x7
change_process: decide
sourcing:
model: shared
delivery_countries: [GB, PL, IN]
organisation:
existing_teams:
- {name: Platform team, party: customer, hours: business, country: GB}
service_management:
tooling: decide
service_levels:
priority_1_response_minutes: 15
recovery_time_hours: 4
compliance:
frameworks: [DORA]
commercial:
currency: GBP
monthly_run_budget: 60000
run:
pre_approved: true

View File

@@ -0,0 +1,10 @@
# Intent 2: bench-landing-zone-shared
- Recorded: 2026-10-21T20:54:36+00:00
- Execution: `case-01-landing-zone-shared-r2`
## What the customer wants
We want our landing zone run as a shared service from go-live. A provider should
respond to faults at every hour, and our own platform team keeps the final say
over changes to the network.

View File

@@ -0,0 +1,199 @@
schema_version: 1
metadata:
customer_case: bench-landing-zone-shared
client_name: ask
author: ask
revision: ask
source: ask
status: BASELINE_LOCKED
engagement:
kind: platform_foundation
intent:
statement: 'We want our landing zone run as a shared service from go-live. A provider
should
respond to faults at every hour, and our own platform team keeps the final say
over changes to the network.
'
requirements:
- id: REQ-01
statement: Our platform team approves every change to the network.
- id: REQ-02
statement: We receive a monthly report of service levels and cost.
business_outcomes:
- id: BO-1
outcome: New payment products reach customers in weeks rather than months.
target: A change reaches production within a day of approval.
- id: BO-2
outcome: Payments are never unavailable for long.
target: Restored within 4 hours.
- id: BO-3
outcome: We keep the platform engineers we hire.
exclusions:
- Application workloads deployed onto the platform foundation
solution:
cloud_provider: gcp
items:
- id: S-1
name: Hub network and interconnect
kind: network
product: Cloud Interconnect
- id: S-2
name: Audit log store
kind: storage
product: Cloud Storage
- id: S-3
name: Deployment pipeline
kind: pipeline
product: Cloud Build
- id: S-4
name: Encryption keys
kind: keys
product: Cloud KMS
conditions:
- id: K-1
'on':
- S-1
condition: The platform is available at least 99.9% of each month.
- id: K-2
'on':
- S-2
condition: Audit logs cannot be deleted for seven years.
- id: K-3
'on':
- S-4
condition: Encryption keys are rotated every 90 days.
build:
duration_days: 36
customer_owned: ask
inherited_risks: ask
operations:
support_hours: 24x7
availability_hours: 24x7
change_process: Changes go through automated pipelines with peer review; changes
affecting the hub network require customer platform team approval prior to release.
monitoring: ask
sourcing:
model: shared
delivery_countries:
- GB
- PL
- IN
organisation:
existing_teams:
- name: Platform team
party: customer
hours: business
country: GB
headcount_limit: ask
service_management:
tooling: Google Cloud native operations tooling (Cloud Monitoring and Cloud Logging),
with no separate service management system.
service_levels:
priority_1_response_minutes: 15
recovery_time_hours: 4
compliance:
frameworks:
- DORA
commercial:
currency: GBP
monthly_run_budget: 60000
transition:
go_live_date: ask
run:
pre_approved: true
overlay_skills: ask
inferred_assumptions:
- id: ASSUMP-01
field: intent.exclusions
statement: Assumed intent.exclusions is ['Application workloads deployed onto the
platform foundation']. Workloads deployed onto the platform foundation are excluded;
operations is confined to the landing zone foundation itself.
impact_if_invalid: Changes which Capabilities are designed.
- id: ASSUMP-02
field: operations.change_process
statement: Assumed operations.change_process is Changes go through automated pipelines
with peer review; changes affecting the hub network require customer platform
team approval prior to release.. Changes follow automated deployment pipelines
with peer review, with network changes requiring explicit customer platform team
approval per REQ-01.
impact_if_invalid: Changes change enablement and release.
- id: ASSUMP-03
field: service_management.tooling
statement: Assumed service_management.tooling is Google Cloud native operations
tooling (Cloud Monitoring and Cloud Logging), with no separate service management
system.. Defaulting to GCP native operations tooling with no separate ITSM system.
impact_if_invalid: Changes tooling and the processes written for it.
discovery_gaps:
- field: metadata.client_name
prompt: What is metadata.client_name?
severity: LOW
- field: metadata.author
prompt: What is metadata.author?
severity: LOW
- field: metadata.revision
prompt: What is metadata.revision?
severity: LOW
- field: metadata.source
prompt: What is metadata.source?
severity: LOW
- field: solution.build.customer_owned
prompt: Which parts of the build does the customer or their supplier own?
severity: LOW
- field: solution.inherited_risks
prompt: What is already known to be unverified or at risk in the solution?
severity: LOW
- field: operations.monitoring
prompt: Which monitoring and alerting is already in place or required?
severity: LOW
- field: organisation.headcount_limit
prompt: Is there a limit on the number of people operating this?
severity: LOW
- field: transition.go_live_date
prompt: When must the solution be in operation?
severity: LOW
- field: run.overlay_skills
prompt: Which overlay Skills should this Execution load?
severity: LOW
provenance:
commercial.currency: supplied
commercial.monthly_run_budget: supplied
compliance.frameworks: supplied
engagement.kind: supplied
intent.business_outcomes: supplied
intent.exclusions: assumed
intent.requirements: supplied
intent.statement: supplied
metadata.author: unknown
metadata.client_name: unknown
metadata.customer_case: supplied
metadata.revision: unknown
metadata.source: unknown
operations.availability_hours: supplied
operations.change_process: assumed
operations.monitoring: unknown
operations.support_hours: supplied
organisation.existing_teams: supplied
organisation.headcount_limit: unknown
run.overlay_skills: unknown
run.pre_approved: supplied
service_levels.priority_1_response_minutes: supplied
service_levels.recovery_time_hours: supplied
service_management.tooling: assumed
solution.build.customer_owned: unknown
solution.build.duration_days: supplied
solution.cloud_provider: supplied
solution.conditions: supplied
solution.inherited_risks: unknown
solution.items: supplied
sourcing.delivery_countries: supplied
sourcing.model: supplied
transition.go_live_date: unknown
readiness:
supplied: 20
answered: 0
assumed: 3
unknown: 10
not_applicable: 0

View File

@@ -0,0 +1,53 @@
# A fictional benchmark: a small landing zone run as a shared service. No customer's
# data is in it. Complete enough to run with nobody to ask.
metadata:
customer_case: bench-landing-zone-shared
engagement:
kind: platform_foundation
intent:
statement: |
We want our landing zone run as a shared service from go-live. A provider should
respond to faults at every hour, and our own platform team keeps the final say
over changes to the network.
business_outcomes:
- {id: BO-1, outcome: New payment products reach customers in weeks rather than months., target: "A change reaches production within a day of approval."}
- {id: BO-2, outcome: Payments are never unavailable for long., target: "Restored within 4 hours."}
- {id: BO-3, outcome: We keep the platform engineers we hire.}
requirements:
- {id: REQ-01, statement: Our platform team approves every change to the network.}
- {id: REQ-02, statement: We receive a monthly report of service levels and cost.}
solution:
cloud_provider: gcp
items:
- {id: S-1, name: Hub network and interconnect, kind: network, product: Cloud Interconnect}
- {id: S-2, name: Audit log store, kind: storage, product: Cloud Storage}
- {id: S-3, name: Deployment pipeline, kind: pipeline, product: Cloud Build}
- {id: S-4, name: Encryption keys, kind: keys, product: Cloud KMS}
conditions:
- {id: K-1, "on": [S-1], condition: The platform is available at least 99.9% of each month.}
- {id: K-2, "on": [S-2], condition: Audit logs cannot be deleted for seven years.}
- {id: K-3, "on": [S-4], condition: Encryption keys are rotated every 90 days.}
build:
duration_days: 36
operations:
support_hours: 24x7
availability_hours: 24x7
change_process: decide
sourcing:
model: shared
delivery_countries: [GB, PL, IN]
organisation:
existing_teams:
- {name: Platform team, party: customer, hours: business, country: GB}
service_management:
tooling: decide
service_levels:
priority_1_response_minutes: 15
recovery_time_hours: 4
compliance:
frameworks: [DORA]
commercial:
currency: GBP
monthly_run_budget: 60000
run:
pre_approved: true

View File

@@ -0,0 +1,10 @@
# Intent 3: bench-landing-zone-shared
- Recorded: 2026-10-21T21:11:10+00:00
- Execution: `case-01-landing-zone-shared-r3`
## What the customer wants
We want our landing zone run as a shared service from go-live. A provider should
respond to faults at every hour, and our own platform team keeps the final say
over changes to the network.

View File

@@ -0,0 +1,201 @@
schema_version: 1
metadata:
customer_case: bench-landing-zone-shared
client_name: ask
author: ask
revision: ask
source: ask
status: BASELINE_LOCKED
engagement:
kind: platform_foundation
intent:
statement: 'We want our landing zone run as a shared service from go-live. A provider
should
respond to faults at every hour, and our own platform team keeps the final say
over changes to the network.
'
requirements:
- id: REQ-01
statement: Our platform team approves every change to the network.
- id: REQ-02
statement: We receive a monthly report of service levels and cost.
business_outcomes:
- id: BO-1
outcome: New payment products reach customers in weeks rather than months.
target: A change reaches production within a day of approval.
- id: BO-2
outcome: Payments are never unavailable for long.
target: Restored within 4 hours.
- id: BO-3
outcome: We keep the platform engineers we hire.
exclusions:
- Workload applications running on the platform foundation
- Network change approvals (retained by customer platform team)
solution:
cloud_provider: gcp
items:
- id: S-1
name: Hub network and interconnect
kind: network
product: Cloud Interconnect
- id: S-2
name: Audit log store
kind: storage
product: Cloud Storage
- id: S-3
name: Deployment pipeline
kind: pipeline
product: Cloud Build
- id: S-4
name: Encryption keys
kind: keys
product: Cloud KMS
conditions:
- id: K-1
'on':
- S-1
condition: The platform is available at least 99.9% of each month.
- id: K-2
'on':
- S-2
condition: Audit logs cannot be deleted for seven years.
- id: K-3
'on':
- S-4
condition: Encryption keys are rotated every 90 days.
build:
duration_days: 36
customer_owned: ask
inherited_risks: ask
operations:
support_hours: 24x7
availability_hours: 24x7
change_process: Changes go through a deployment pipeline with peer review, with
network changes requiring customer platform team approval.
monitoring: ask
sourcing:
model: shared
delivery_countries:
- GB
- PL
- IN
organisation:
existing_teams:
- name: Platform team
party: customer
hours: business
country: GB
headcount_limit: ask
service_management:
tooling: The Cloud provider's own operations tooling, with no separate system.
service_levels:
priority_1_response_minutes: 15
recovery_time_hours: 4
compliance:
frameworks:
- DORA
commercial:
currency: GBP
monthly_run_budget: 60000
transition:
go_live_date: ask
run:
pre_approved: true
overlay_skills: ask
inferred_assumptions:
- id: ASSUMP-01
field: intent.exclusions
statement: 'Assumed intent.exclusions is [''Workload applications running on the
platform foundation'', ''Network change approvals (retained by customer platform
team)'']. Assumed from the platform foundation scope: workload applications running
on the platform are out of scope, and customer platform team retains network change
approvals.'
impact_if_invalid: Changes which Capabilities are designed.
- id: ASSUMP-02
field: operations.change_process
statement: 'Assumed operations.change_process is Changes go through a deployment
pipeline with peer review, with network changes requiring customer platform team
approval.. Catalogue default adapted to customer requirement REQ-01: changes go
through deployment pipelines with peer review, with customer platform team retaining
approval over network changes.'
impact_if_invalid: Changes change enablement and release.
- id: ASSUMP-03
field: service_management.tooling
statement: 'Assumed service_management.tooling is The Cloud provider''s own operations
tooling, with no separate system.. Catalogue default: Cloud provider''s native
operations tooling with no separate system.'
impact_if_invalid: Changes tooling and the processes written for it.
discovery_gaps:
- field: metadata.client_name
prompt: What is metadata.client_name?
severity: LOW
- field: metadata.author
prompt: What is metadata.author?
severity: LOW
- field: metadata.revision
prompt: What is metadata.revision?
severity: LOW
- field: metadata.source
prompt: What is metadata.source?
severity: LOW
- field: solution.build.customer_owned
prompt: Which parts of the build does the customer or their supplier own?
severity: LOW
- field: solution.inherited_risks
prompt: What is already known to be unverified or at risk in the solution?
severity: LOW
- field: operations.monitoring
prompt: Which monitoring and alerting is already in place or required?
severity: LOW
- field: organisation.headcount_limit
prompt: Is there a limit on the number of people operating this?
severity: LOW
- field: transition.go_live_date
prompt: When must the solution be in operation?
severity: LOW
- field: run.overlay_skills
prompt: Which overlay Skills should this Execution load?
severity: LOW
provenance:
commercial.currency: supplied
commercial.monthly_run_budget: supplied
compliance.frameworks: supplied
engagement.kind: supplied
intent.business_outcomes: supplied
intent.exclusions: assumed
intent.requirements: supplied
intent.statement: supplied
metadata.author: unknown
metadata.client_name: unknown
metadata.customer_case: supplied
metadata.revision: unknown
metadata.source: unknown
operations.availability_hours: supplied
operations.change_process: assumed
operations.monitoring: unknown
operations.support_hours: supplied
organisation.existing_teams: supplied
organisation.headcount_limit: unknown
run.overlay_skills: unknown
run.pre_approved: supplied
service_levels.priority_1_response_minutes: supplied
service_levels.recovery_time_hours: supplied
service_management.tooling: assumed
solution.build.customer_owned: unknown
solution.build.duration_days: supplied
solution.cloud_provider: supplied
solution.conditions: supplied
solution.inherited_risks: unknown
solution.items: supplied
sourcing.delivery_countries: supplied
sourcing.model: supplied
transition.go_live_date: unknown
readiness:
supplied: 20
answered: 0
assumed: 3
unknown: 10
not_applicable: 0

Some files were not shown because too many files have changed in this diff Show More