feat: the solution architecture agent on the shared Execution engine
The reference agent's subject, cloud solution architecture, as an agent in the operating model agent's pattern: the Execution engine (from orchestration_engine) and one Workflow in app/solution_architecture, built for the settings and provider bundle by assembly.workflow_for. Copied from gcp_solution_architecture_agent at 8b397cd without its own engine: its role files, Skills, provider bundle, ADRs, vocabulary, scripts and evaluation datasets. The image takes the engine from a named build context and installs Terraform. It is called through the Orchestration engine, and its files are what the operating model agent digests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
20
eval/datasets/judge/calibration.json
Normal file
20
eval/datasets/judge/calibration.json
Normal file
@@ -0,0 +1,20 @@
|
||||
{
|
||||
"runs": 3,
|
||||
"questions": 32,
|
||||
"labelled": 0,
|
||||
"judges": {
|
||||
"jev": {
|
||||
"answered": 32,
|
||||
"stability": 1.0,
|
||||
"agreement_with_labels": null,
|
||||
"mean_answer": 0.37
|
||||
},
|
||||
"gemini": {
|
||||
"answered": 32,
|
||||
"stability": 0.92,
|
||||
"agreement_with_labels": null,
|
||||
"mean_answer": 0.32
|
||||
}
|
||||
},
|
||||
"between_judges": 0.91
|
||||
}
|
||||
44
eval/datasets/judge/case-02-design-recommendations.md
Normal file
44
eval/datasets/judge/case-02-design-recommendations.md
Normal file
@@ -0,0 +1,44 @@
|
||||
# Design Recommendations
|
||||
|
||||
This document outlines the architectural configurations and best practices applied to the components of the high-scale data ingestion pipeline. These recommendations integrate the functional and non-functional requirements (NFRs) with guidance from the Google Cloud Well-Architected Framework pillar advisors to ensure a secure, reliable, cost-optimized, and high-performing system.
|
||||
|
||||
## Security, privacy, and compliance
|
||||
|
||||
To protect the ingestion endpoint from volumetric DDoS attacks and Layer 7 exploits, a Global External Application Load Balancer with Google Cloud Armor is deployed. This fulfills the requirement for strict perimeter isolation while serving the 10,000 RPS traffic over TLS 1.2+ (**DR-1**).
|
||||
|
||||
The architecture implements a zero-trust model where all internal pipeline components (Cloud Run, Pub/Sub, Cloud Storage, BigQuery) communicate privately via VPC Service Controls and direct VPC egress (**DR-3**). All processes run under dedicated, least-privilege IAM service accounts, tightly binding permissions to only the required resources (**DR-4**). To meet regulatory data protection mandates and ensure cryptographic sovereignty, all persistent data across the Pub/Sub staging buffer, Cloud Storage sink, and BigQuery quarantine store is encrypted with Customer-Managed Encryption Keys (CMEK) (**DR-2**).
|
||||
|
||||
## Reliability
|
||||
|
||||
Reliability is anchored on minimizing data loss (RPO 0) and avoiding systemic failures under heavy load. The ingestion endpoint mitigates the risk of cold-start latency spikes by maintaining a minimum instance baseline, allowing it to sustainably absorb traffic bursts without violating the 200ms p95 latency target (**DR-5**).
|
||||
|
||||
Within the asynchronous pipeline, downstream processing degradation is isolated from ingestion. The Pub/Sub validation subscription utilizes a dead-letter policy with bounded delivery attempts (5 retries) to redirect unparseable poison-pill messages to BigQuery, preventing queue head-of-line blocking (**DR-6**). Additionally, the valid record storage sink leverages multi-region replication and object versioning to guarantee data durability even during a regional outage or accidental deletion event (**DR-7**). Finally, the Cloud Run services utilize explicit startup and liveness probes to ensure traffic is only routed to healthy, fully-initialized containers (**DR-8**).
|
||||
|
||||
## Operational excellence
|
||||
|
||||
A foundational principle of operational excellence is reproducible, reviewable, and automated changes. Every pipeline component—from IAM bindings to Pub/Sub schemas and serverless runtimes—is defined declaratively as Infrastructure as Code (Terraform) (**DR-9**). This declarative approach acts as the primary recovery mechanism to satisfy the RTO < 60 minutes disaster recovery objective.
|
||||
|
||||
## Cost optimization
|
||||
|
||||
Cost optimizations prioritize scaling tightly with business demand. Both the Ingestion and Validation Cloud Run services are configured to allocate CPU only during request processing, meaning they incur zero compute costs when idle, perfectly matching the strict scale-to-zero requirement (**DR-10**).
|
||||
|
||||
Storage costs are minimized through aggressive lifecycle management. The Pub/Sub buffer retains messages only for a shortened 48-hour window, as RPO=0 durability is fulfilled by the downstream sinks (**DR-11**). The Cloud Storage bucket transitions older validated batches to Nearline storage after 30 days (**DR-12**), and the BigQuery dead-letter quarantine datasets enforce a 30-day automated partition expiration to prevent unbound storage accumulation of malformed payloads (**DR-13**).
|
||||
|
||||
## Performance efficiency
|
||||
|
||||
To sustain the 10,000 RPS throughput requirement with sub-second latencies, the pipeline leverages advanced serverless execution features. Both Cloud Run services use Execution Environment Gen 2 and Startup CPU Boost to optimize network packet processing and eliminate initialization drag (**DR-14**). The Ingestion service's concurrency is explicitly tuned to handle high parallel request volumes (e.g., 80 concurrent requests per instance), preventing excessive container scale-out thrashing (**DR-15**).
|
||||
|
||||
Between the buffer and the processing tier, the Validation Engine relies on a Pub/Sub push subscription to immediately invoke the validation containers, minimizing pull polling overhead and reducing end-to-end event latency (**DR-16**).
|
||||
|
||||
## Sustainability
|
||||
|
||||
To minimize the workload's carbon footprint, all services are provisioned together within a Google Cloud region boasting a high Carbon-Free Energy (CFE) score (e.g., `europe-west1` or `us-central1`) (**DR-17**).
|
||||
|
||||
Energy waste is further curtailed by enforcing schema compliance at the initial Pub/Sub buffer boundary, dropping malformed payloads early and preventing wasted validation compute cycles (**DR-19**). Lastly, the Quarantine Replay Processor is architected as an on-demand Cloud Run Job rather than an always-on polling consumer, aligning energy expenditure directly to actual remediation activity (**DR-18**).
|
||||
|
||||
## Assumptions
|
||||
|
||||
As this design was produced in pre-approved mode, the following assumptions were made:
|
||||
- **Cloud Region Selection**: We assume the selection of a specific region (like `europe-west1` or `us-central1`) will balance the multi-zone availability requirements with the high CFE targets for sustainability.
|
||||
- **Micro-batching**: We assume the Validation Engine service includes internal micro-batching logic to aggregate records before writing to Cloud Storage, avoiding excessive single-object API calls that could degrade performance.
|
||||
- **Trace Sampling & Logging**: Observability costs will be governed by sampling Cloud Trace ingestion and filtering out routine Cloud Run health check (`/healthz`) logs out-of-band via standard project sinks.
|
||||
56
eval/datasets/judge/case-03-design-recommendations.md
Normal file
56
eval/datasets/judge/case-03-design-recommendations.md
Normal file
@@ -0,0 +1,56 @@
|
||||
# Design Recommendations
|
||||
|
||||
## Assumptions
|
||||
|
||||
Since `pre_approved` is `true`, the following assumptions govern these design recommendations:
|
||||
- The workload is deployed regionally in a low-carbon region (a region with CFE% >= 75%) to meet sustainability goals.
|
||||
- Cloud SQL for PostgreSQL is configured in a high-availability (multi-zone) topology to meet the 99.9% uptime requirement, avoiding cross-region replication.
|
||||
- Cloud Run handles the compute scaling, scaling down to 0 instances outside of business hours to optimize costs.
|
||||
- The Corporate Identity Provider integrates with Identity-Aware Proxy (IAP) to authenticate users at the load balancer.
|
||||
- All application and operational logs are stored in a centralized Google Cloud Storage bucket locked for 365 days.
|
||||
|
||||
## Security, privacy, and compliance
|
||||
|
||||
To enforce a zero-trust model and meet security, privacy, and compliance requirements, the architecture implements several layers of defense:
|
||||
|
||||
- **Identity-Aware Proxy (IAP)**: Protects the Cloud Run service by authenticating corporate users at the external load balancer before traffic reaches the application (DR-2).
|
||||
- **Network Security**: The Load Balancer enforces a custom SSL policy restricting traffic to TLS 1.2+ (DR-1). The Cloud Run service itself restricts ingress to `internal-and-cloud-load-balancing` so it cannot be accessed directly via the public internet (DR-3). Outbound traffic from Cloud Run is routed strictly through the VPC using Direct VPC Egress (DR-4).
|
||||
- **Least Privilege and Secrets**: Cloud Run operates using a dedicated, user-managed service account (DR-5) with permissions limited to accessing necessary secrets from Secret Manager (DR-8) and connecting to the database. These secrets are injected dynamically into the runtime environment (DR-9).
|
||||
- **Database Security**: Cloud SQL is isolated from the public internet by disabling public IPv4 and connecting via Private Service Connect/VPC peering (DR-6). It enforces IAM authentication and SSL/TLS connections (DR-7).
|
||||
- **Compliance Logging**: To meet the 365-day immutable audit log requirement, a Cloud Logging sink routes all audit events to a dedicated Cloud Storage bucket configured with a 365-day retention policy (DR-10).
|
||||
|
||||
## Reliability
|
||||
|
||||
High availability and disaster recovery are essential to meeting the 99.9% uptime and RTO/RPO requirements:
|
||||
|
||||
- **High Availability**: Cloud SQL for PostgreSQL is configured for regional high availability, maintaining a synchronous standby replica in a secondary zone to allow automatic failover during a disruption (DR-11).
|
||||
- **Disaster Recovery**: Automated daily backups are retained for at least 7 days, and Point-in-Time Recovery (PITR) is enabled via Write-Ahead Logging (WAL) to guarantee an RPO of 1 hour or less (DR-12).
|
||||
- **Health Checking**: The load balancer utilizes backend health checks to continuously monitor the health of the Cloud Run instances, routing traffic away from degraded containers (DR-13).
|
||||
|
||||
## Operational excellence
|
||||
|
||||
Operations are streamlined through comprehensive observability and automated alerting:
|
||||
|
||||
- **Monitoring and Alerting**: Cloud Monitoring captures metrics across all components. Alert policies are specifically configured to trigger when Cloud Run HTTP 5xx error rates exceed 1% over a 5-minute window, and when Cloud SQL CPU or storage utilization exceeds 80% (DR-16).
|
||||
- **Centralized Logs**: All system metrics, application logs, and traces are centralized within Google Cloud's operations suite for rapid incident response.
|
||||
|
||||
## Cost optimization
|
||||
|
||||
The architecture leverages serverless characteristics to align cloud spend with active business usage:
|
||||
|
||||
- **Scale to Zero**: Cloud Run is configured with a minimum instance count of 0, ensuring that compute resources scale down entirely during off-hours, weekends, and periods of inactivity, drastically reducing idle costs (DR-14).
|
||||
- **Right-sized Database**: While high availability is required, autoscaling storage ensures that database disk space is only paid for when consumed.
|
||||
|
||||
## Performance efficiency
|
||||
|
||||
Sub-second page loads and transactional consistency are maintained through optimized storage and networking:
|
||||
|
||||
- **Database Performance**: Cloud SQL is provisioned with high-throughput SSD storage and automatic storage expansion to maintain low-latency read/write operations for booking transactions without hitting IOPS ceilings (DR-15).
|
||||
- **Connection Optimization**: By using VPC-native private connections and keeping all traffic within the same region, network latency between Cloud Run and Cloud SQL is minimized.
|
||||
|
||||
## Sustainability
|
||||
|
||||
Environmental impact is mitigated by selecting the right region and eliminating idle resource waste:
|
||||
|
||||
- **Low-Carbon Region**: All resources are deployed in a region with a Carbon-Free Energy (CFE) score of 75% or higher, directly lowering the gross carbon emissions of the workload (DR-17).
|
||||
- **Dynamic Scaling**: Utilizing Cloud Run's scale-to-zero capabilities (DR-14) ensures that the application does not consume power for idle compute instances outside of business hours.
|
||||
226
eval/datasets/judge/labels.json
Normal file
226
eval/datasets/judge/labels.json
Normal file
@@ -0,0 +1,226 @@
|
||||
[
|
||||
{
|
||||
"id": "case-02-design-recommendations.security.0",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this security checklist item, either by recommending it or by explaining why it does not apply? Shift-left security: Are automated security scans integrated into the CI/CD pipeline?",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.security.1",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this security checklist item, either by recommending it or by explaining why it does not apply? Zero trust: Is Cloud Identity used as a centralized identity provider for managing user lifecycles and federation?",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.reliability.2",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this reliability checklist item, either by recommending it or by explaining why it does not apply? Game days or chaos engineering practices are regularly held to validate failure recovery.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.reliability.3",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this reliability checklist item, either by recommending it or by explaining why it does not apply? The system architecture incorporates patterns like circuit breakers, retries with exponential backoff, and rate limiting to support graceful degradation.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.operational-excellence.4",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this operational-excellence checklist item, either by recommending it or by explaining why it does not apply? Operational readiness: A formal framework or set of criteria exists to assess operational readiness before production deployment.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.operational-excellence.5",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this operational-excellence checklist item, either by recommending it or by explaining why it does not apply? Culture of improvement: A documented strategy is in place for regularly reviewing and adapting cloud operations to industry advancements.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.cost-optimization.6",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this cost-optimization checklist item, either by recommending it or by explaining why it does not apply? Network Egress: Data transfer is minimized by keeping traffic regional, using **Cloud CDN**, and leveraging **Standard Network Tier** where appropriate. High-volume on-premises traffic uses **Direct Peering** or **Cloud Interconnect** (always verify if hybrid connectivity is involved).",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.cost-optimization.7",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this cost-optimization checklist item, either by recommending it or by explaining why it does not apply? Granular Visibility: BigQuery billing export is enabled and used for regular cost reviews.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.performance-optimization.8",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this performance-optimization checklist item, either by recommending it or by explaining why it does not apply? Monitoring and continuous improvement: Automated dashboards and alerts are configured for key performance indicators (KPIs).",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.performance-optimization.9",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this performance-optimization checklist item, either by recommending it or by explaining why it does not apply? Elasticity: The architecture leverages serverless or managed services to dynamically match capacity to load.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.sustainability.10",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this sustainability checklist item, either by recommending it or by explaining why it does not apply? Cloud sustainability: AI is used as a catalyst for profitability and resilience to streamline operations, or sustainability is integrated into the design process to create positive feedback loops.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.sustainability.11",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this sustainability checklist item, either by recommending it or by explaining why it does not apply? Continuously measure and improve: Applications are instrumented to measure the specific carbon intensity of software features, or automated exports of Carbon Footprint data to BigQuery are configured for deep analysis.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.quality.specific",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "graded",
|
||||
"text": "Are the recommendations specific to this workload and its stated requirements, as opposed to generic best practice that would fit any workload?",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.quality.actionable",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "graded",
|
||||
"text": "Does each recommendation name the concrete setting, feature or configuration to apply, so an engineer could act on it without more research?",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.quality.trade_offs",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "graded",
|
||||
"text": "Where pillars pull in different directions (for example cost against reliability), is the trade-off named and a resolution recommended?",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-02-design-recommendations.quality.traceable",
|
||||
"document": "case-02-design-recommendations.md",
|
||||
"kind": "graded",
|
||||
"text": "Can each recommendation be traced to a requirement or constraint of the workload?",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.security.16",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this security checklist item, either by recommending it or by explaining why it does not apply? Zero trust: Are private connectivity methods (Cloud Interconnect, VPN) used for internal traffic?",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.security.17",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this security checklist item, either by recommending it or by explaining why it does not apply? Security by design: Is defense-in-depth implemented at the network, host, and application layers?",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.reliability.18",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this reliability checklist item, either by recommending it or by explaining why it does not apply? The architecture avoids single points of failure through cross-zone or cross-region redundancy.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.reliability.19",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this reliability checklist item, either by recommending it or by explaining why it does not apply? Application and infrastructure health checks are configured to trigger automated failovers.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.operational-excellence.20",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this operational-excellence checklist item, either by recommending it or by explaining why it does not apply? Resource optimization: Resource utilization is regularly reviewed using recommendations from Active Assist or performance data.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.operational-excellence.21",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this operational-excellence checklist item, either by recommending it or by explaining why it does not apply? Operational readiness: A formal framework or set of criteria exists to assess operational readiness before production deployment.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.cost-optimization.22",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this cost-optimization checklist item, either by recommending it or by explaining why it does not apply? Rightsizing: Resources are regularly adjusted based on rightsizing suggestions provided by Active Assist Recommender.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.cost-optimization.23",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this cost-optimization checklist item, either by recommending it or by explaining why it does not apply? Granular Visibility: BigQuery billing export is enabled and used for regular cost reviews.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.performance-optimization.24",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this performance-optimization checklist item, either by recommending it or by explaining why it does not apply? Elasticity: Auto-scaling rules are configured and validated to handle variable demand.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.performance-optimization.25",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this performance-optimization checklist item, either by recommending it or by explaining why it does not apply? Monitoring and continuous improvement: Distributed tracing and profiling tools are used to identify code-level bottlenecks.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.sustainability.26",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this sustainability checklist item, either by recommending it or by explaining why it does not apply? Cloud sustainability: AI is used as a catalyst for profitability and resilience to streamline operations, or sustainability is integrated into the design process to create positive feedback loops.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.sustainability.27",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "yes_no",
|
||||
"text": "Do the recommendations address this sustainability checklist item, either by recommending it or by explaining why it does not apply? Promote a culture of sustainability: Abstract carbon metrics are transformed into tangible progress indicators in annual reports, or sustainability is treated as a first-class technical requirement (NFR) tied to KPIs and performance reviews.",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.quality.specific",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "graded",
|
||||
"text": "Are the recommendations specific to this workload and its stated requirements, as opposed to generic best practice that would fit any workload?",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.quality.actionable",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "graded",
|
||||
"text": "Does each recommendation name the concrete setting, feature or configuration to apply, so an engineer could act on it without more research?",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.quality.trade_offs",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "graded",
|
||||
"text": "Where pillars pull in different directions (for example cost against reliability), is the trade-off named and a resolution recommended?",
|
||||
"label": null
|
||||
},
|
||||
{
|
||||
"id": "case-03-design-recommendations.quality.traceable",
|
||||
"document": "case-03-design-recommendations.md",
|
||||
"kind": "graded",
|
||||
"text": "Can each recommendation be traced to a requirement or constraint of the workload?",
|
||||
"label": null
|
||||
}
|
||||
]
|
||||
Reference in New Issue
Block a user