init

Author: Dmi3yy

.gitignore

@@ -0,0 +1 @@
+.idea

ARCHITECTURE_FREEZE_CHECKLIST.md

@@ -0,0 +1,33 @@
+# ARCHITECTURE_FREEZE_CHECKLIST — eMCP
+
+Use this checklist before starting Phase 1 implementation.
+
+## 1. Contract Completeness
+- [ ] `PRD.md`, `SPEC.md`, `TOOLSET.md` are mutually consistent.
+- [ ] Gate A/B/C boundaries are explicit and conflict-free.
+- [ ] Namespace governance and ecosystem extension rules are finalized.
+- [ ] `initialize` metadata contract is mandatory and versioned.
+
+## 2. Security Baseline
+- [ ] `THREAT_MODEL.md` attack trees reviewed and approved.
+- [ ] `SECURITY_CHECKLIST.md` mapped to planned tests.
+- [ ] Model field allowlist policy is complete for all allowlisted models.
+- [ ] Error formatter contract (`401/403/409/413/415` + `trace_id`) is fixed.
+
+## 3. Runtime Governance
+- [ ] Tool uniqueness and handle uniqueness rules are frozen.
+- [ ] Rate-limit identity resolver algorithm is frozen.
+- [ ] Idempotency hash and conflict policy is frozen.
+- [ ] Streaming activation policy (`stream.enabled`) is frozen.
+
+## 4. Release/BC Governance
+- [ ] SemVer and Public Contract Stability sections approved.
+- [ ] Golden fixture governance (version bump + changelog + CI guard) approved.
+- [ ] Deprecation policy for breaking changes approved.
+- [ ] Upstream compatibility policy (`laravel/mcp ^0.5.x`) approved.
+
+## 5. Process Readiness
+- [ ] Formal platform audit (`PLATFORM_AUDIT.md`) approved.
+- [ ] Ownership assigned for platform, security, and release decisions.
+- [ ] Phase 1 backlog items trace to frozen contracts.
+- [ ] Any open architectural question has owner + resolution date.

CONTRIBUTING.md

@@ -0,0 +1,22 @@
+# CONTRIBUTING — eMCP
+
+## Scope
+This repository defines and implements the official MCP platform layer for Evolution CMS.
+
+## Contribution Rules
+- Keep public contract changes aligned across `PRD.md`, `SPEC.md`, and `TOOLSET.md`.
+- Any change that affects public MCP behavior must include tests and changelog entry.
+- Namespace governance is mandatory: third-party additions must use `vendor.domain.*`.
+- Breaking changes require SemVer-major planning and deprecation note.
+
+## Pull Request Requirements
+- Link issue/problem statement.
+- Describe contract impact (none/minor/major).
+- Update docs if runtime behavior changes.
+- Add or update tests/fixtures for changed behavior.
+- Confirm no sensitive fields are exposed by model tools.
+
+## Review Gates
+- Security-sensitive changes require security review.
+- Contract changes require platform maintainer review.
+- Release-significant changes require BC policy review.