📄 docs: Clearly Define expectations for MVP, MVE, MAP

[evolvewithevan]

📚 docs: Clearly Define Expectations for Prototype, MVP, MVE, MAP

Description

We need a clear, internal document that outlines the expectations and definitions for each of the following phases in GitCord's development lifecycle:

• Prototype
• Minimum Viable Product (MVP)
• Minimum Viable Experiment (MVE)
• Minimum Awesome Product (MAP)

This will help align contributors on terminology, reduce ambiguity, and guide future roadmap decisions.

Tasks

• Define what constitutes an MVP for GitCord ✅ P1
• Distinguish MVE from MVP and when to use it ✅ P2
• Describe MAP and how it differs from MVP ✅ P2
• Add all definitions to the project docs or a dedicated glossary ✅ P2
• Link this document from the README or CONTRIBUTING.md ✅ P3
• Update Projects README to reflect these changes

Notes

These definitions should be opinionated enough to guide decisions but flexible enough to evolve as GitCord scales.

---

Priority Legend

• P1: Blocks roadmap or coordination
• P2: Important for medium-term clarity
• P3: Nice-to-have linkage and discoverability