From b5be4f6f1f3fbb42d87edd236d4d74d5d60bae65 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 10 Oct 2026 03:28:01 +0000 Subject: [PATCH] =?UTF-8?q?docs(agents):=20platform=20gaps=20wait=20for=20?= =?UTF-8?q?the=20platform=20=E2=80=94=20no=20app-side=20workaround,=20no?= =?UTF-8?q?=20temporary=20fixture?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Maintainer ruling 2026-10-10: 「平台的问题就等平台」, and the env-gated temporary fixture exception is removed. A platform defect is reported upstream and the card that needs the fix carries Blocked-by: on that issue; the app does not reshape its metadata to dodge it. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_012BtouqNfFazqX5akwoC8Jk --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 85fa26f..326013e 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -132,7 +132,7 @@ docs/backlog/ work cards docs/requirements/ | Governed surface (maintainer merges) | `DESIGN.md` §01–§04 · `AGENTS.md` · `CLAUDE.md` · `LICENSE` · `CHANGELOG.md` · `docs/design/**`. A PR touching any of these is ACCEPTed and left open with a `## 维护者速读` comment. | | Decisions stay with the maintainer | The merge authorization covers **merging**, not deciding. Product semantics, `DESIGN.md` §01–§04 wording, and anything on the escalation ladder still becomes a `needs-user-decision` card. | | Capability expansion | **Tight.** No new runtime dependency, plugin, `requires:` capability or external service unless the card says so. Propose via `needs_decision`. | -| Platform gaps | **Report, never patch.** A platform limitation goes to objectstack-ai/objectstack as an issue (symptom, minimal repro, expected capability, platform version) and is appended to its `docs/PLATFORM_GAPS_FROM_TEMPLATES.md`. The app may carry an env-gated temporary fixture that names the platform issue. | +| Platform gaps | **Report, then wait — never patch, never work around.** A platform limitation goes to objectstack-ai/objectstack as an issue (symptom, minimal repro, expected capability, platform version) and is appended to its `docs/PLATFORM_GAPS_FROM_TEMPLATES.md`. The app does not reshape its own metadata to dodge a platform defect (splitting a screen, moving a gate, duplicating a page or a check), and carries no temporary fixture for one: the card that needs the fix carries `Blocked-by:` the platform issue and waits for it. Maintainer, 2026-10-10, verbatim: 「平台的问题就等平台」. | | Scope | Deliver the card, whole. Out-of-scope findings become new unassigned issues, not riders. | ### PM dispatch