updated manifesto

README.md

@@ -1,5 +1,7 @@
 # The MCP Manifesto
 **The Constitution of the Move Compete Play League.**
+*A Builder's Community by [Ekarna Interactive](hhttps://ekarnainteractive.com/).*
+*"Our mission is to forge the next generation of AI-Augmented Architects."*
 
 ---
 
@@ -13,52 +15,49 @@ 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 assistants (Cursor, v0, Midjourney) to generate code and assets so we can focus on the Architecture.
-* **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.
+* **Rapid Prototyping.** We move from "Brainstorm" to "Blueprint" to "Build" in days, not weeks.
 
 #### 🔴 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.
+* **The Season Pass.** We operate in **Seasons**. Every cohort has a start date, a finish line, and a mission. You are either in the arena, or you are watching from the stands.
-* **Meritocracy.** Your rank is determined by what you ship, not who you know.
+* **Skin in the Game.** We believe commitment requires cost—whether it's time, reputation, or a nominal fee. Free advice is rarely valued; earned skills last forever.
 
 #### 🔵 PLAY (Creativity)
 * **Code is Art.** We respect the craft.
-* **Weird is Good.** We encourage experimental UI, game dev, and "useless" fun projects.
+* **Protocol First.** We don't just build apps; we build Agents. We explore the bleeding edge of **MCP (Model Context Protocol)**, **A2A (Agent-to-Agent)**, and **UCP**.
 * **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"
+### 3. The Methodology: "Studio Mode"
-Software is a team sport. In the real world, you never build alone.
+This is not a bootcamp. This is a simulation of a high-performance Product Studio.
-* **The Squad:** Builders are grouped into squads of 4-6 members.
+* **The Squad:** Builders are grouped into squads to simulate a real startup environment.
-* **The Mission:** Every Season has a clear objective (e.g., "Build an MCP Agent").
+* **The Stack:** We standardize on the **Ekarna Stack**—tools chosen for speed and scale.
-* **The Stack:** We standardize on modern, open protocols.
+* **The Workflow:** We teach the full lifecycle: Brainstorming $\rightarrow$ Blueprints $\rightarrow$ AI Gen $\rightarrow$ PaaS Deployment.
 
-### 4. Software Philosophy
+### 4. Software Philosophy: "Pragmatic Sovereignty"
-We are builders, not just consumers. The tools we use to run this community are chosen based on three principles:
+We are builders, not zealots. We choose tools that give us **Leverage**.
 
-**I. Sovereign & Self-Hosted**
+**I. Own the Code (Gitea)**
-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.
+We host our own Git server because code is our most valuable asset. We welcome you to clone our repos to GitHub, but the "Source of Truth" lives here, on our soil.
 
-**II. The "Powered By" Protocol**
+**II. Rent the Scale (PaaS)**
-We are proud of our stack. We do not white-label or hide the open-source tools that power our community.
+We do not waste time managing servers when we should be building features.
-* **Co-Branding:** We display the Gitea, Matrix, and Linux logos alongside our own.
+* We use **Supabase** for Backend-as-a-Service to cut dev time by 50%.
-* **Respect:** We stand on the shoulders of giants. We acknowledge the creators who built the engines we use.
+* We use **Netlify/Vercel** for instant global deployment.
-* **Contribution:** If we find a bug, we fix it and push it upstream.
+* We use **AI Agents** to automate our Ops.
 
-**III. Modular by Design (The Unix Way)**
+**III. The "Powered By" Protocol**
-We reject "All-in-One" bloatware. We choose tools that do *one thing perfectly*.
+We are proud of our open-source roots. We contribute back to the tools we use (Gitea, Matrix, Linux) and we never hide the engine that powers our league.
-* **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.
+* **No Gatekeeping.** Code is just one part of the stack. Whether you are a Designer, Product Manager, or Engineer—if you ship, you are a Builder.
 * **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.
+* **Respect the Squad.** If you commit to a Season, you deliver. Your squad depends on you.
 
 ---
 
-*Infrastructure sponsored by **Ekarna Interactive**.*
+*Operated by **Ekarna Interactive**.*