commit 16995cd1308786a703b5d0c755d5a2c6f07ddae4 Author: Gokul G Date: Sun Feb 8 10:58:17 2026 +0000 added readme file diff --git a/README.md b/README.md new file mode 100644 index 0000000..1d10748 --- /dev/null +++ b/README.md @@ -0,0 +1,64 @@ +# The MCP Manifesto +**The Constitution of the Move Compete Play League.** + +--- + +### 1. The Great Filter +We are entering the age of Infinite Intelligence. The barrier to entry for coding has collapsed. This is not the end of the developer; it is the beginning of the **Architect**. + +The "Tutorial Loop" is dead. Watching someone else code does not make you a builder. In the MCP League, we do not consume content. We ship products. + +### 2. The Trinity +Our philosophy is built on three pillars that balance chaos and order. + +#### 🟢 MOVE (Velocity) +* **Ship or Die.** A rough prototype today is worth more than a perfect idea tomorrow. +* **Bias for Action.** We don't spend weeks debating stacks. We pick tools, we build, we deploy. +* **The AI Acceleration.** We do not fear AI; we ride it. We use AI code assistants (Cursor, Windsurf), rapid prototyping tools (v0, Lovable), and LLMs to skip the boilerplate and focus on the logic. + +#### 🔴 COMPETE (Excellence) +* **Iron Sharpens Iron.** Competition is not toxic; it is necessary for growth. +* **The Leaderboard.** We track shipping streaks, bounty clears, and code quality. +* **Meritocracy.** Your rank is determined by what you ship, not who you know. + +#### 🔵 PLAY (Creativity) +* **Code is Art.** We respect the craft. +* **Weird is Good.** We encourage experimental UI, game dev, and "useless" fun projects. +* **Joy of Building.** The best way to learn is to build something ridiculous just to see if you can. If you aren't having fun, you're doing it wrong. + +--- + +### 3. The Methodology: "Squad Mode" +Software is a team sport. In the real world, you never build alone. +* **The Squad:** Builders are grouped into squads of 4-6 members. +* **The Mission:** Every Season has a clear objective (e.g., "Build an MCP Agent"). +* **The Stack:** We standardize on modern, open protocols. + +### 4. Software Philosophy +We are builders, not just consumers. The tools we use to run this community are chosen based on three principles: + +**I. Sovereign & Self-Hosted** +We own our data. Whenever possible, we choose software we can host ourselves (Gitea, Matrix, Flarum) over walled gardens. This ensures that the MCP League cannot be de-platformed or monetized against our will. + +**II. The "Powered By" Protocol** +We are proud of our stack. We do not white-label or hide the open-source tools that power our community. +* **Co-Branding:** We display the Gitea, Matrix, and Linux logos alongside our own. +* **Respect:** We stand on the shoulders of giants. We acknowledge the creators who built the engines we use. +* **Contribution:** If we find a bug, we fix it and push it upstream. + +**III. Modular by Design (The Unix Way)** +We reject "All-in-One" bloatware. We choose tools that do *one thing perfectly*. +* **The API Requirement:** Every tool we use must have a robust API. +* **The MCP Layer:** We don't just connect tools manually. We build **MCP Servers** on top of these APIs, allowing our AI Agents to interact with our infrastructure seamlessly. +* **Example:** Gitea manages code. Matrix manages chat. An MCP Agent bridges them to update your team when you ship. + +--- + +### 5. Code of Conduct +* **No Gatekeeping.** Whether you are a student, Junior or a Principal Engineer, you are here to build. +* **Open Source Default.** Unless it involves sensitive business logic, we build in public. +* **Respect the Squad.** If you commit to a Sprint, you deliver. Your squad depends on you. + +--- + +*Infrastructure sponsored by **Ekarna Interactive**.* \ No newline at end of file