▸case-01 In project 'Titan-DB', lead engineer Marcus initially requested migrating the primary datastore to CockroachDB v23.1, but after load testing, Marcus confirmed staying on PostgreSQL 15.3. Write the markdown history record for this decision. | pass→pass | 9,891 | 5,229 | -47% | 1 | 1 | 0% | 1,639 | 1,122 | -32% | 0 | 0 | — |
▸case-02 During the sprint review for service 'Helios-API', Sarah proposed switching the HTTP framework from Express to Fastify, but the team has not yet tested or approved the switch. Draft the history entry for the decision history file. | pass→fail | 8,774 | 7,863 | -10% | 1 | 1 | 0% | 1,343 | 1,320 | -2% | 0 | 0 | — |
▸case-03 The history log for deployment tool 'KubeDeploy' currently contains the entry: 'Target runtime: Docker v24.0 (decided by Alex on 2024-02-01)'. Alex just confirmed reverting to Containerd v1.7.11 on 2024-02-10 due to daemon memory leaks. Update the history record. | pass→pass | 5,844 | 4,328 | -26% | 1 | 1 | 0% | 1,027 | 902 | -12% | 0 | 0 | — |
▸case-04 For backend service 'PayStream', security patch v2.4.1 was applied to library 'auth-jwt'. Rather than telling future agents to 'see PR #402 or Jira ticket SEC-892 for details', write the single-source-of-truth decision history entry. | fail→pass | 14,993 | 6,601 | -56% | 1 | 1 | 0% | 2,159 | 1,237 | -43% | 0 | 0 | — |
▸case-05 In infrastructure project 'CloudStack-Terraform', engineer Dave is currently running a trial deployment of OpenTofu v1.6 in staging to test compatibility. Dave asks you to write a history log entry declaring OpenTofu v1.6 as the official project standard. How should this history entry be handled? | pass→pass | 11,647 | 130,492 | +1020% | 1 | 1 | 0% | 1,742 | 1,479 | -15% | 0 | 0 | — |
▸case-06 In repo 'Orchestrator-Core', entry in history.md reads: 'Scheduler algorithm: Priority Queue (directed by Elena)'. Elena explicitly updated her direction yesterday to Exponential Backoff Queue. Draft the updated decision history log entry. | pass→pass | 5,912 | 4,596 | -22% | 1 | 1 | 0% | 831 | 990 | +19% | 0 | 0 | — |
▸case-07 The team working on 'SearchService' is leaning toward Elasticsearch v8.12, but benchmarking ends tomorrow. A team member suggests adding a temporary history log entry stating 'For now: Elasticsearch v8.12'. Produce the appropriate history record action. | fail→pass | 6,931 | 5,645 | -19% | 1 | 1 | 0% | 998 | 1,106 | +11% | 0 | 0 | — |
▸case-08 An old history entry in 'PaymentGateway' states 'API version target: v1.0.0'. However, lead architect Maya corrected this decision to target v2.1.0 before release. Update the project history file entry to ensure future reading agents receive accurate guidance. | pass→pass | 7,568 | 3,669 | -52% | 1 | 1 | 0% | 1,015 | 816 | -20% | 0 | 0 | — |
▸case-09 In service 'StreamPipeline', the team flipped the messaging broker from RabbitMQ to Apache Kafka. Write a history entry that provides complete context so a future agent reading cold does not need to inspect Slack archives or team design notes. | pass→pass | 21,395 | 11,478 | -46% | 1 | 1 | 0% | 3,036 | 1,421 | -53% | 0 | 0 | — |
▸case-10 In repository 'AuthServer', history.md records 'Session store: Redis Cluster'. During an incident response, the team migrated permanently to DynamoDB, but nobody updated history.md. Draft the corrected entry for history.md. | pass→pass | 8,435 | 4,699 | -44% | 1 | 1 | 0% | 1,118 | 1,038 | -7% | 0 | 0 | — |
▸case-11 Feature flag 'new_billing_engine' in 'SaaS-Platform' was tested in production for two weeks and fully enabled today by release manager Jordan. Write the history record entry for this decision. | pass→pass | 9,573 | 36,792 | +284% | 1 | 1 | 0% | 1,482 | 1,202 | -19% | 0 | 0 | — |
▸case-12 An RFC in 'DataPipeline' proposed replacing Python with Rust for module 'ingest-core'. After evaluation, the proposal was rejected and Python 3.11 was confirmed. Write the decision history entry for the repository. | pass→pass | 12,606 | 5,568 | -56% | 1 | 1 | 0% | 1,885 | 1,045 | -45% | 0 | 0 | — |
▸case-13 In repository 'ML-Worker', the build environment was changed from Python 3.9 to Python 3.11 after dependency conflict resolution. Write a history entry so a reader cold-booting on this repo knows the exact runtime truth immediately. | pass→pass | 12,874 | 5,125 | -60% | 1 | 1 | 0% | 1,817 | 993 | -45% | 0 | 0 | — |
▸case-14 In 'WebPortal-Frontend', history.md lists 'Framework: Vue 2'. The team completed a migration to Vue 3 last month. Update the history.md file entry. | pass→pass | 6,608 | 6,357 | -4% | 1 | 1 | 0% | 722 | 907 | +26% | 0 | 0 | — |
▸case-15 The team for 'Metrics-Collector' is evaluating Datadog vs Grafana Cloud. Vendor meetings are scheduled for next week. The tech lead asks to record 'Vendor: Datadog' in history.md right now. How should this be handled? | pass→pass | 10,664 | 8,322 | -22% | 1 | 1 | 0% | 1,514 | 1,383 | -9% | 0 | 0 | — |
▸case-16 In project 'Core-Infra', management decided to migrate compute nodes from AWS EKS to GCP GKE. Write a self-contained history entry that explains the final decision and context without referring the reader to external Jira tickets. | pass→pass | 13,841 | 8,755 | -37% | 1 | 1 | 0% | 1,924 | 1,422 | -26% | 0 | 0 | — |
▸case-17 History in 'LogIngest' states 'Storage retention: 30 days (per Sam)'. Sam clarified that 30 days was just an initial draft and the actual compliance policy mandates 90 days, approved by legal. Draft the updated history entry. | pass→pass | 7,213 | 4,068 | -44% | 1 | 1 | 0% | 1,141 | 912 | -20% | 0 | 0 | — |
▸case-18 In 'API-Gateway', a history entry stated 'v1 REST endpoints deprecated, sunset on 2024-06-01'. The team canceled the sunset and decided to support v1 REST indefinitely due to key client contracts. Write the revised history entry. | pass→pass | 7,374 | 3,604 | -51% | 1 | 1 | 0% | 1,027 | 888 | -14% | 0 | 0 | — |
▸case-19 Database engineer Liam is halfway through running a multi-step zero-downtime migration to rename table 'users' to 'accounts' in service 'UserSvc'. Liam asks to write a history entry stating 'Table users successfully renamed to accounts'. Draft the response/entry. | pass→pass | 9,984 | 7,489 | -25% | 1 | 1 | 0% | 1,532 | 1,416 | -8% | 0 | 0 | — |
▸case-20 Draft a git commit message following Conventional Commits format for refactoring the auth token refresh handler in project 'Aegis'. | pass→pass | 8,347 | 13,765 | +65% | 1 | 1 | 0% | 1,305 | 1,108 | -15% | 0 | 0 | — |
▸case-21 Design a markdown template for Architecture Decision Records (ADRs) to be used in the 'DataMesh' project repository, specifying standard sections like Status, Context, Decision, and Consequences. | pass→pass | 15,168 | 13,055 | -14% | 1 | 1 | 0% | 2,214 | 2,135 | -4% | 0 | 0 | — |
▸case-22 Draft an in-flight status update message for the #incident-outage Slack channel while database engineers are currently investigating elevated latency on PostgreSQL node 2. | pass→pass | 8,521 | 5,658 | -34% | 1 | 1 | 0% | 1,238 | 1,066 | -14% | 0 | 0 | — |