docs: publish the runs of 2026-10-21

The evaluation (both cases three times: report, results, spread, each
run's Deliverables and lesson candidates) and the hand-off through the
Orchestration engine (report, the document of links, both agents' kept
files and records). Benchmark cases only, all fictional; no machine paths,
and the links carry no signatures. Other runs stay ignored.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-22 09:25:03 +01:00
parent 1fed1cb538
commit 628b6ee170
159 changed files with 37817 additions and 2 deletions

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,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,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,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": []
}