cft0808/edict: README-based editorial guide

cft0808/edict describes itself in the README as "🏛️ 三省六部制 · OpenClaw Multi-Agent Orchestration System , 9 specialized AI agents with real-time dashboard, model config, and full audit trails". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "🎬 Demo", the README says: > 🐳 没有 OpenClaw？ 跑一行 docker run -p 7891:7891 cft0808/edict 即可体验完整看板 Demo（预置模拟数据）。. That establishes the project's stated boundary, not a production test.

The README's "安装" section gives a useful starting point for deciding whether the project fits: ✅ 设置 Agent 间通信可见性（sessions.visibility all，解决消息不可达问题）. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: ✅ 符号链接统一数据（各 Workspace 的 data/scripts → 项目目录，确保数据一致）. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "🤔 为什么是三省六部？". The source evidence includes: CrewAI 和 AutoGen 的 Agent 协作模式是 "做完就交",,没有人检查产出质量。就像一个公司没有 QA 部门，工程师写完代码直接上线。. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: docker run -p 7891:7891 cft0808/sansheng-demo When the README contains no runnable command, this article does not invent one. Open its "🤔 为什么是三省六部？" section and confirm system dependencies, default ports, and first-run initialization before using a public server.