This directory is the product and engineering decision source for Evotown.
Evotown is a standalone project. Its specs should not inherit SkillLite-specific implementation constraints by default. SkillLite can be one connected runtime, but Evotown must stay runtime-neutral.
| Spec | Purpose |
|---|---|
| product-positioning.md | What Evotown is, what it is not, and how community / enterprise modes relate. |
| enterprise-control-plane.md | Core enterprise control plane architecture and product modules. |
| engine-ingest-api.md | Runtime-neutral engine ingest and connector contract direction. |
| asset-registry.md | Reusable skill / prompt / workflow / memory asset lifecycle. |
| skills-market-and-connectors.md | Private Skills Market and connector / proxy node architecture. |
| policy-center.md | Enterprise policy pull, violation reporting, and approval boundaries. |
| knowledge-connector.md | Feishu / Yuque / native document sources and search index. |
| database-connector.md | Business database registry, employee ACL, MCP isolation boundary. |
| arena-ux.md | Role of the game page as Arena / visual simulation layer. |
| security-and-privacy.md | Data, secrets, artifacts, employee telemetry, and enterprise privacy boundaries. |
| roadmap.md | Phased implementation plan and acceptance signals. |
- Evotown is the control plane and evaluation layer, not a replacement runtime.
- OpenClaw, Hermes, SkillLite, and custom runners must remain first-class integration targets.
- The game page stays, but enterprise governance features must live in a practical console.
- Personal agent discoveries must pass review before becoming company-wide defaults.
- Private Skills Market owns package distribution; Evotown owns run evidence, review, and evaluation.
- Product docs may summarize specs, but specs are the source of truth for roadmap and architecture direction.