User Hackathon: Module 1 Mastery Challenge (The Question Paper)

[!CAUTION] This is a Hands-Off challenge. Do not manually write code. Your role is as a Commander. You will orchestrate AI agents to build, verify, and document a production-ready system.

---

1. Challenge Overview

Objective: Build a functional system that demonstrates your evolution from a typist to an AI Orchestrator using at least 3 of the Nine Pillars of AIDD.

Time Limit: 4-8 hours Tooling: Use any LLM-powered IDE (Cursor, VS Code + Agentic Extensions, etc.)

---

2. Choose Your Mission

Choose ONE of the following scenarios to implement.

Option A: Intelligent API Gateway

Build a rate-limiting API gateway with:

• Requirement 1: Dynamic request routing and load balancing using worker pods.
• Requirement 2: Real-time analytics dashboard showing latency and request volume.
• Requirement 3: Automated threat detection (blocking SQL injections or excessive requests via AI analysis).
• Pillars to Show: Specs First, Verification, Observability.

Option B: Multi-Agent Code Review System

Develop a system where code commits trigger a multi-agent review:

• Requirement 1: A Security Agent scans for vulnerabilities (e.g., OWASP Top 10).
• Requirement 2: A Performance Agent suggests algorithmic optimizations.
• Requirement 3: A Quality Agent ensures adherence to a strict style guide.
• Requirement 4: Generates a consolidated report in a unified Markdown format.
• Pillars to Show: Security Guards, Governance, Verification.

---

3. Strict Rules & Constraints

1. Commander Mode ONLY: If you manually write more than 5 lines of code, you have failed the challenge.
2. Specifications First: You must produce a system_specification.md before generating implementation files.
3. Verification Circles: Every feature must have a corresponding automated test. If the tests don't pass, the feature doesn't exist.
4. Observability Integration: Your system must have a "Heartbeat" or "Health Check" endpoint that reflects its internal state.

---

4. Evaluation Rubric

---

5. Submission Requirements

To pass this hackathon, you must provide:

1. The Specification: Your initial system_specification.md document.
2. The Architecture: A Mermaid diagram showing how your components interact.
3. The Evidence: Screenshots or terminal logs showing passing test suites.
4. A Reflection: A brief write-up on how your role shifted from "Coder" to "Orchestrator" during this build.

[!IMPORTANT] Good luck, Commander. The future is orchestrated, not written.