DESIGN.md@backend/packages/harness/evoflow/proactiveA
DESIGN.md@backend/packages/harness/evoflow/proactive from evovexai/evoflow is a DESIGN.md file: the design rules coding agents follow in that repo.
mdr add evovexai/evoflow/backend/packages/harness/evoflow/proactive/DESIGN.md@git:20261020.b380398Pins git:20261020.b380398 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- DESIGN.md file
- Repository
- evovexai/evoflow
- Path
backend/packages/harness/evoflow/proactive/DESIGN.md- Versions recorded
- 2
- Latest version
- git:20261020.b380398, committed Oct 20, 2026
- First version recorded
- Sep 12, 2026
- Size
- 16,375 bytes
- Repository stars
- 540
- License
- a license file GitHub does not identify
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 智能体员工（Proactive AI）模块设计文档 ## 1. 核心理念 ### 1.1 从「被动响应」到「主动上岗」 传统 AI 模式：**人 → 发消息 → AI 响应 → 返回结果** 智能体员工模式：**AI 角色 → 自主思考 → 发起行动 → 人仅决策** 每个 AI 不再是被动等待指令的工具，而是一个**真实岗位的负责人**： - 有明确的职责范围（Domain） - 有需要优化的 KPI / 目标 - 定期「醒来」审视自己的领域，主动发现问题、提出改进 - 在授权范围内自主执行，超出范围时请求人类决策 ### 1.2 人类角色：决策者，非执行者 人不再写 prompt、不发指令、不盯进度。人只做一件事：**决策** - 飞书审批卡片 → 点「同意」/「拒绝」 - 桌面窗口通知 → 授权 / 驳回 - 对 AI 的行动结果进行事后评价（反馈循环） --- ## 2. 架构总览 ``` ┌─────────────────────────────────────────────────────────────┐ │ EvoFlow Gateway │ │ │ │ ┌──────────────┐ ┌──────────────────┐ │ │ │ Proactive │───>│ ProactiveEngine │ (LLM 思考引擎) │ │ │ Runner │ │ - 评估领域状态 │ │ │ │ (心跳调度) │ │ - 识别改进机会 │ │ │ │ │ │ - 生成倡议 │ │ │ │ 30s tick │ │ - 规划行动 │ │ │ └──────┬───────┘ └────────┬─────────┘ │ │ │ │ │ │ v v │ …
Read the whole file at its exact version.
How to install
mdr add evovexai/evoflow/backend/packages/harness/evoflow/proactive/DESIGN.md@sha256:04484b4598c90383The line at the top of this page pins the label git:20261020.b380398, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_tqhkcf4yosq52hqd)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 12, 2026 and Oct 20, 2026, about one every 38 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.b380398 latest | 2026-10-20 | b380398 | 16,375 B | A | view · diff |
| git:20260912.6c490fd | 2026-09-12 | 6c490fd | 16,405 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (16375 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
evovexai/evoflow · 540 stars · license a license file GitHub does not identify · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tqhkcf4yosq52hqd GET https://markdownregistry.com/api/v1/resolve?ref=evovexai/evoflow/backend/packages/harness/evoflow/proactive/DESIGN.md GET https://markdownregistry.com/api/v1/blob/04484b4598c90383bd274ad62326b106016fe07edc24869ad91a4c6031b18f82
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: what DESIGN.md is and how agents use it · which agent file does what.