▸case-02 We are building an Authentication Service and I need a formal C4 component model specification for the dev team. Please lay out the component details including technology stack, software capabilities, underlying code elements, and related knowledge modules/interfaces. Give me a clear checklist to ensure all goals and constraints are validated. | fail→fail | 33,118 | 15,236 | -54% | 1 | 1 | 0% | 6,916 | 3,449 | -50% | 0 | 0 | — |
▸case-01 I need to document our Order Fulfiller microservice at the C4 component architecture level. Can you generate a complete spec detailing its core purpose, key features, internal code-level files, and interface boundaries? Please make sure to outline steps for verifying the design. | pass→pass | 36,950 | 26,544 | -28% | 1 | 1 | 0% | 8,243 | 3,421 | -58% | 0 | 0 | — |
▸case-03 I'm refactoring a monolith's Notification module into a standalone component and need to map it using the C4 model component template. Please produce a component overview that lists its technology, internal code files, software features, and external system interfaces, along with verification steps for the implementation. | fail→pass | 32,783 | 15,425 | -53% | 1 | 1 | 0% | 6,962 | 2,832 | -59% | 0 | 0 | — |
▸case-04 Create a C4 component documentation for an Elasticsearch Search Indexer component written in Go. Tempted to just write a simple README, but we need a C4 component layout mapping code files like indexer.go to markdown docs, listing software features, and outlining verification steps. | fail→pass | 20,441 | 13,384 | -35% | 1 | 1 | 0% | 3,680 | 2,830 | -23% | 0 | 0 | — |
▸case-05 We need to formalize our Java Billing Calculator module using the C4 component model. Instead of standard Javadoc, produce a C4 component spec with sections for overview metadata, purpose, code elements, and sub-skill interfaces. | pass→fail | 24,252 | 14,656 | -40% | 1 | 1 | 0% | 3,854 | 3,375 | -12% | 0 | 0 | — |
▸case-06 Provide a C4 component spec for a Payment Gateway integration component in Rust. Avoid freeform markdown; follow the C4 component layout with explicit metadata, feature breakdowns, internal code documentation links, and sub-skill module links. | pass→pass | 30,562 | 11,791 | -61% | 1 | 1 | 0% | 5,979 | 2,571 | -57% | 0 | 0 | — |
▸case-07 Draft a C4 component document for a Python Inventory Sync background worker. Base model defaults usually produce generic architecture notes, but I need the structured C4 component layout with Overview metadata, Purpose, Features, Code Elements, and Knowledge Modules. | pass→pass | 29,947 | 9,599 | -68% | 1 | 1 | 0% | 4,658 | 2,252 | -52% | 0 | 0 | — |
▸case-12 Produce a C4 component document for a Redis Cache Invalidator service written in Go. Instead of general architecture paragraphs, generate the standard C4 component structure with clear purpose, features, code files, and interface links. | fail→pass | 22,893 | 10,042 | -56% | 1 | 1 | 0% | 4,462 | 2,203 | -51% | 0 | 0 | — |
▸case-08 Generate a C4 component spec for a C++ Recommendation Engine. Rather than high-level UML diagrams, structure this with C4 component sections detailing technology, code element files, software capabilities, and interface sub-skills. | fail→pass | 35,913 | 15,796 | -56% | 1 | 1 | 0% | 6,744 | 2,720 | -60% | 0 | 0 | — |
▸case-09 Document the User Profile service in TypeScript as a C4 component model. Tempted to use OpenAPI/Swagger specs alone, but I need a full C4 component document with purpose, metadata overview, internal code links, and fractal knowledge sub-skills. | pass→pass | 33,199 | 11,907 | -64% | 1 | 1 | 0% | 6,251 | 2,529 | -60% | 0 | 0 | — |
▸case-10 Create a C4 component spec for a C# Audit Logger library. Base models tend to generate class diagrams, but we require the C4 component layout including Overview (Name, Description, Type, Tech), Features, Code Elements, and Interfaces. | fail→fail | 20,193 | 14,910 | -26% | 1 | 1 | 0% | 4,636 | 2,822 | -39% | 0 | 0 | — |
▸case-11 Map our Node.js Media Transcoder worker into a C4 component document. Do not give a simple npm README. Use the C4 component structure listing core purpose, code element links, features, and sub-skill interfaces. | pass→pass | 26,804 | 14,200 | -47% | 1 | 1 | 0% | 4,675 | 2,483 | -47% | 0 | 0 | — |
▸case-13 Formalize an OAuth2 Identity Provider component using C4 component mapping. Avoid standard RFC documentation style; provide a C4 component model spec with Overview, Features, Code Elements, and Knowledge Modules. | fail→pass | 25,122 | 13,660 | -46% | 1 | 1 | 0% | 4,530 | 2,640 | -42% | 0 | 0 | — |
▸case-14 Draft a C4 component layout for a Python Fraud Detector ML component. Instead of a Jupyter notebook explanation, provide a structured C4 component document detailing core purpose, software capabilities, code file links, and sub-skills. | fail→fail | 21,292 | 11,697 | -45% | 1 | 1 | 0% | 3,107 | 2,468 | -21% | 0 | 0 | — |
▸case-15 Document an API Rate Limiter middleware component written in Envoy C++ using the C4 component format. Do not provide raw Envoy YAML configuration; structure a C4 component spec with metadata, purpose, features, code links, and sub-skill modules. | fail→pass | 26,801 | 11,416 | -57% | 1 | 1 | 0% | 4,819 | 2,540 | -47% | 0 | 0 | — |
▸case-16 Generate a C4 component model spec for a Webhook Dispatcher microservice in Kotlin. Standard responses give simple HTTP client code, but I need a full C4 component spec with Overview metadata, Purpose, Features, Code Elements, and sub-skill links. | fail→pass | 32,346 | 15,919 | -51% | 1 | 1 | 0% | 5,957 | 3,449 | -42% | 0 | 0 | — |
▸case-17 Map an OpenTelemetry Collector component into a C4 component document. Avoid standard OTEL config snippets; provide a complete C4 component spec detailing overview metadata, features, code elements, and interfaces. | fail→pass | 25,068 | 22,475 | -10% | 1 | 1 | 0% | 4,637 | 4,829 | +4% | 0 | 0 | — |
▸case-18 Document an S3-compatible File Storage abstraction component in Go using the C4 component architecture layout. Instead of cloud deployment scripts, produce a C4 component spec with overview metadata, features, code links, and fractal knowledge modules. | fail→pass | 38,390 | 16,254 | -58% | 1 | 1 | 0% | 8,235 | 2,824 | -66% | 0 | 0 | — |
▸case-19 Create a C4 component specification for an E-commerce Catalog Search component. base models usually write product requirements docs, but I need a C4 component layout with Purpose, Overview metadata, Code Elements, and sub-skill interface links. | fail→fail | 22,459 | 12,559 | -44% | 1 | 1 | 0% | 3,391 | 2,152 | -37% | 0 | 0 | — |
▸case-20 We are designing the top-level system architecture for our banking platform. Can you create a C4 Container level diagram spec showing the Web Application, API Gateway, Database, and Mainframe System boundaries? | pass→pass | 23,690 | 17,137 | -28% | 1 | 1 | 0% | 3,509 | 2,768 | -21% | 0 | 0 | — |
▸case-21 I need a C4 System Context level overview for our enterprise HR system. Please map out external users, third-party payroll services, and core system boundaries. | pass→pass | 19,975 | 17,020 | -15% | 1 | 1 | 0% | 3,132 | 3,379 | +8% | 0 | 0 | — |
▸case-22 Perform a STRIDE threat modeling analysis on our authentication endpoint to identify spoofing, tampering, and elevation of privilege risks. | pass→pass | 22,069 | 17,771 | -19% | 1 | 1 | 0% | 3,230 | 3,888 | +20% | 0 | 0 | — |