Files
tom_analysis_agent/eval/results/20261021T203623Z-handoff/solution_architecture/requirements.json
Jonathan Boniface 628b6ee170 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>
2026-10-22 09:25:03 +01:00

304 lines
13 KiB
JSON

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