▸case-15 Our product team is embarking on a strategic DDD initiative for a global supply chain logistics engine. We need to know the mandatory strategic artifacts that must be produced during this initial phase before starting code implementation. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 We are evaluating an algorithmic clearinghouse system with fast-changing regulatory rules, 5 separate development teams conflicting over domain entities, unstable partner REST endpoints, and strict auditability mandates. Perform a formal viability check and structure the required response sections. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 An energy grid monitoring platform processes 10,000 sensor telemetry writes per second while power dispatchers query complex aggregated dashboards in real time. Assess if read/write separation is recommended and provide the specialized skill handle. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-23 A medical claim processing workflow involves claim validation, coverage lookup, co-pay calculation, and payout authorization across multiple microservices. Failures during payout require rolling back prior holds. Evaluate DDD fit, workflow routing, and rollback design. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 We need sample templates and deliverable structures to guide our strategic design workshop deliverables for an enterprise asset management platform. Where should the team look for deliverable templates? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 Our core healthcare claim processing engine needs architectural refactoring due to strict compliance requirements and unstable partner integration endpoints. Assess if we should implement DDD here and guide our next moves. Provide a breakdown including underlying assumptions and scope, our current phase, the primary design artifacts produced, and a summary of open risks alongside recommended next steps. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 We are restructuring our enterprise logistics platform where multi-carrier fulfillment rules are constantly shifting and development teams keep conflicting over shared database models. Please evaluate whether adopting domain-driven design is appropriate for this system. Format your response to cover the framing assumptions, the active design stage, all concrete deliverables generated, and any highlighted risks with immediate follow-up actions. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 We have a bug in our existing payment service where a null check fails on an optional field in an API payload. Evaluate whether to initiate a domain-driven design modeling process to resolve this issue. Provide scope, current stage, deliverables, and next steps. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 We are building an order fulfillment pipeline spanning payment, inventory reservation, and shipping dispatch that takes hours to complete and requires compensating transactions on failure. Team members suggest implementing this as nested database triggers. Evaluate DDD viability, workflow handling pattern, and provide relevant skill routing. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 We are tasked with building an automated options trading algorithm platform, but our team has zero access to domain experts or product proxies who understand options trading mechanics. Should we proceed with full domain-driven design modeling? Provide scope, stage, artifacts, and risk analysis. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 Our internal notification microservice has one unstable integration contract with a third-party SMS provider, but its business rules are static, it is maintained by a single developer, and auditability is not required. Assess whether full DDD should be adopted according to viability standards. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 We have established our bounded contexts and subdomains for an insurance claim management domain, and now our developers need guidance on implementing aggregates, entities, and value objects in domain code. Determine the next design stage and provide skill routing. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 We are building a single-team internal task checklist web app that performs simple CRUD operations on tasks with no complex business rules or external integrations. Evaluate whether we should implement full DDD architecture for this application. Provide scope, current stage, deliverables, and risks. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 We are designing a multi-tenant B2B billing and subscription platform that handles high-volume invoice generation and audit tracking. Help us determine if full domain modeling is justified versus keeping a simple pattern. Make sure the output details the project scope and baseline assumptions, the current modeling stage, specific artifacts produced, and key architectural risks with advice on what step to take next. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 Our warehouse management system requires complete audit trails of stock adjustments and re-allocations across multiple fulfillment centers. Engineers want to record every state change as an append-only event stream. Evaluate DDD viability and route event store design. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 We are breaking a monolithic B2B SaaS CRM into microservices. Teams are arguing over whether Customer should be a single shared model or split across Sales, Support, and Billing. Evaluate DDD viability and provide skill handle routing for strategic design. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 Our e-commerce platform suffers from database contention because heavy reporting queries run against the same tables handling checkout transactions. Engineers suggest using raw SQL database views on the live transactional database. Assess if DDD applies and how to separate reads from writes, including artifacts and specialized skill references. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 We are evaluating a peer-to-peer lending engine where risk models update daily, loan origination involves complex multi-party state transitions, and audit logs are legally enforced. Evaluate DDD viability, identify the initial active design stage, and route tactical pattern design. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 We are designing an immutable banking ledger where all balance changes must be retained as an accurate historical sequence of events. Developers want to store only current balances in a traditional SQL table instead of capturing full historical events. Evaluate whether full DDD applies and how to structure event history as the source of truth, including required artifacts and skill routing. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 In a freight management system, the Dispatch context must consume carrier status updates from an external legacy EDI system whose data format changes frequently without warning. Assess DDD applicability and route context mapping. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 We need to synchronize customer profile data between an inventory context and a loyalty context while building optimized read models for customer dashboards. Some engineers suggest creating direct cross-database joins between context databases. Evaluate DDD viability, proper context integration, read model design, and relevant skill tags. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 A telehealth platform connects patients, clinicians, and insurance payors. Patient records have strict privacy invariants, compliance auditing is mandatory, and 3 distinct engineering teams keep breaking each other's database models. Assess DDD viability and route for strategic boundary definition. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 Our architectural review board requires that all boundary decisions and strategic model choices made during our microservice refactoring be formally documented and tracked over time. Evaluate DDD suitability and show how architectural decisions should be logged. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |