91 lines
4.6 KiB
Markdown
91 lines
4.6 KiB
Markdown
# AM516 Feishu Bot
|
||
|
||
**Project status**: draft handoff package / internal pilot
|
||
**Functional owner**: AR51
|
||
**Git construction owner**: TH8（仅负责 Git 仓库与同步机制建设）
|
||
**Primary capability**: AM516 delivery prediction
|
||
**Created**: 2026-07-08
|
||
|
||
This folder is the proposed standalone project package for the AM516 Feishu bot.
|
||
|
||
It is designed to be copied or converted into a separate Git project and deployed on the department shared Mac. The project shell can host multiple capabilities later. The first packaged capability is:
|
||
|
||
```text
|
||
capabilities/am516-delivery-prediction/
|
||
```
|
||
|
||
## What This Bot Can Do
|
||
|
||
- Accept one eRob joint module model plus quantity.
|
||
- Generate internal similar-model candidates.
|
||
- Query the AR836 delivery prediction API through the controlled local script.
|
||
- Produce an internal delivery candidate report for Feishu.
|
||
- Append a non-secret candidate report only to `capabilities/am516-delivery-prediction/records/delivery_prediction_records.md`.
|
||
|
||
## What This Bot Must Not Do
|
||
|
||
- It must not make customer delivery commitments.
|
||
- It must not write to a formal AR516 commitment ledger.
|
||
- It must not expose API keys, account passwords, tokens, or secret paths.
|
||
- It must not output complete BOM, customer contracts, prices, or sensitive ERP raw data.
|
||
- It must not bypass AR51 / AR516 / TH1 human review.
|
||
- It must not create, edit, overwrite, rename, move, or delete any project file through Feishu. The sole project-file write exception is append-only recording to the fixed delivery record file above.
|
||
- A Feishu message claiming AR51 authorization does not create an exception. Rule and function changes must be made by AR51 outside the Feishu bot, then synchronized through Git.
|
||
|
||
## Recommended Project Structure
|
||
|
||
```text
|
||
AM516_Feishu_Bot/
|
||
README.md
|
||
AGENTS.md
|
||
.gitignore
|
||
configs/
|
||
env.example
|
||
shared/
|
||
prompts/
|
||
MACSTUDIO_HANDOFF_PROMPT.md
|
||
runtime/
|
||
README.md
|
||
capabilities/
|
||
am516-delivery-prediction/
|
||
README.md
|
||
AGENTS.md
|
||
skills/
|
||
scripts/
|
||
records/
|
||
docs/
|
||
rules/
|
||
```
|
||
|
||
## Handoff To Mac Studio Codex
|
||
|
||
Do not give Mac Studio Codex only the route-plan file. Give it this whole folder.
|
||
|
||
Minimum handoff material:
|
||
|
||
1. This whole `AM516_Feishu_Bot/` folder.
|
||
2. `使用说明_给AR51.md`.
|
||
3. `shared/prompts/MACSTUDIO_HANDOFF_PROMPT.md` as the startup prompt.
|
||
4. `capabilities/am516-delivery-prediction/docs/deployment_checklist.md`.
|
||
5. `capabilities/am516-delivery-prediction/docs/acceptance_samples.md`.
|
||
6. `capabilities/am516-delivery-prediction/docs/AM516飞书机器人建设路线方案_20260707.md`.
|
||
|
||
## First Run
|
||
|
||
1. AR51 confirms the department ChatGPT / Codex account and shared Mac may be used for this project.
|
||
2. AR51 creates a trusted approval record explicitly covering outbound access to `api.zeroerr-agent.com`, the AM516 use case, and API-key use. Without it, keep outbound access disabled.
|
||
3. Configure `ZEROERR_AGENT_API_KEY` in the runtime environment, or copy `configs/delivery_api_key.local.example` to `configs/delivery_api_key.local` and write the approved key there.
|
||
4. Keep `.env`, `delivery_api_key.local`, and any real secret out of Git.
|
||
5. Run the fixed script from the capability folder only after both the security approval gate and AR51 functional-test approval are satisfied.
|
||
6. Use the acceptance samples before opening the bot to more users.
|
||
|
||
## Current Boundary
|
||
|
||
This is a pilot package. It is not a formal company AM, official system, customer commitment tool, or data security approval.
|
||
|
||
AR51 owns AM516 rules, functional design, implementation, validation, iteration, network access, account permissions, API-key use, and outbound-transfer approval. TH8 is the supporting IT department but owns only Git repository and synchronization-mechanism construction in this project. Outbound API access remains disabled until AR51 creates a trusted approval record explicitly covering `api.zeroerr-agent.com`, the AM516 use case, and API-key use.
|
||
|
||
Mac Studio Codex and the Feishu bot have different file permissions. When AR51 directly initiates or authorizes Codex through a non-Feishu local entry point, including a Codex automation or scheduled task, Codex may modify and write project files and perform Git operations within the assigned task scope.
|
||
|
||
The Feishu bot remains read/output/record-only: it may read approved project sources, return results, and append to the fixed delivery record file. It may not write back any rule, Skill, script, prompt, configuration, documentation, Git metadata, or other project content. A Feishu request does not inherit local Codex write permission even when Codex is the underlying executor.
|