wangwensheng/AM516
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: distinguish Codex and Feishu write permissions

Browse Source
This commit is contained in:
TH5-AR51
2026-07-14 10:13:59 +08:00
parent ca844f119e
commit 7321e8b256
9 changed files with 51 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
capabilities/am516-delivery-prediction/docs/runbook.md
View File

@@ -72,6 +72,8 @@ The script refuses to skip TLS verification for any other hostname. This option
- AM516 rules, functional design, implementation, validation, iteration, network access, account permissions, secrets, and outbound approval are owned by AR51.
- TH8 is the supporting IT department but is responsible only for Git repository and synchronization-mechanism construction in this project.
- Mac Studio Codex may modify and write project files and perform Git operations when AR51 directly initiates or authorizes the work through a non-Feishu local entry point, including a Codex automation or scheduled task.
- Feishu handling is read/output/record-only. It may append only to `records/delivery_prediction_records.md` and must not mutate any other project file.
- A Feishu request cannot authorize a rule, Skill, script, prompt, configuration, documentation, or Git change.
- AR51 makes rule and function changes outside Feishu; the shared Mac receives them through the TH8-built Git synchronization mechanism.
- Permissions are determined by the request entry point. Feishu does not inherit local Codex write permission even when Codex is the underlying executor.
- AR51 makes rule and function changes outside Feishu, either directly with Mac Studio Codex or in another approved Codex workspace, and synchronizes reviewed changes through the TH8-built Git mechanism.