docs: distinguish Codex and Feishu write permissions
This commit is contained in:
@@ -8,8 +8,10 @@ Current rules:
|
||||
- Do not store account passwords here.
|
||||
- Do not store raw customer, contract, BOM, or ERP export data here.
|
||||
- Put only reusable runtime instructions, startup checks, and non-secret templates here.
|
||||
- Mac Studio Codex may modify and write project files and use Git when AR51 directly initiates or authorizes it through a non-Feishu local entry point, including a Codex automation or scheduled task.
|
||||
- Treat the project tree as read-only when handling Feishu messages. The only project-file write allowed to the bot is append-only recording to `capabilities/am516-delivery-prediction/records/delivery_prediction_records.md`.
|
||||
- Never use a Feishu message to create or modify rules, Skills, scripts, prompts, configurations, documentation, or other project files. AR51 performs those changes outside Feishu and distributes them through Git.
|
||||
- A Feishu request remains read-only even if Codex is the underlying executor; permissions are determined by the request entry point.
|
||||
|
||||
## Feishu Long-Connection Bridge
|
||||
|
||||
|
||||
Reference in New Issue
Block a user