Part of #14496 (maintainer ruling 2026-09-02, 「ok」 to option 2). Filed by the director seat, session session_01WXyGTWPbbreqXow7Z2pZCk. AGENTS.md is a governed surface and the agent-instruction face ⇒ skills lane, draft PR, human merge; Clause ① applies to the dispatch tier per the pm-dispatch skill (agent-instruction file). Clause-②: no.
The rule to land (one paragraph, in the ADR / governed-territory section — today's anchors are the docs/adr/-governed guidance around AGENTS.md line ~275 and the governed-surface definition around line ~291; place it where the ADR-citation reader looks, ⛔ no new section header if an existing one fits)
Verbatim from the ruling on #14496 (translate for the English file, keep the Chinese quote as the provenance line):
决策住在它治理的代码所在的仓。划开闭源边界与商业的决策住 cloud,本仓引用一律 cloud ADR-NNNN(⛔ 永不裸号);凡 cloud 决策的机制半边治理本仓开源代码的,本仓自有 ADR(自有编号 + Provenance 段指回 cloud 记录与日期,商业半边留 cloud),cloud 记录加一行指针;⛔ 不搬文件、不重编号。
English rendering to land: An ADR lives in the repository whose code it governs. Decisions that draw the open/closed or commercial boundary live in objectstack-ai/cloud and are cited from this repo as cloud ADR-NNNN — never as a bare number, which scripts/check-adr-anchors.mjs resolves against this registry (the two registries number independently, so a bare id silently lands on an unrelated local record: 0071 / 0024 / 0081 today). When a cloud decision's mechanism half governs open code in this repo, this repo carries its own ADR — own number, a ## Provenance section naming the cloud record and its date, the commercial half left in cloud — and the cloud record gains a one-line pointer. Files are never moved between registries and numbers are never reassigned.
Why here and not only in the gate
The gate already accepts the qualifier structurally (CROSS_REPO_QUALIFIERS); what it cannot know is which bare number meant the other registry. The rule is what an author reads before writing the citation; the precedent it names (ADR-0079's Provenance section) is what they copy.
Constraints
Refs: #14496 (ruling) · #14361 (the re-pointing pass) · the three mirror-ADR sub-issues of #14496 · ADR-0079.
Part of #14496 (maintainer ruling 2026-09-02, 「ok」 to option 2). Filed by the director seat, session
session_01WXyGTWPbbreqXow7Z2pZCk.AGENTS.mdis a governed surface and the agent-instruction face ⇒ skills lane, draft PR, human merge; Clause ① applies to the dispatch tier per the pm-dispatch skill (agent-instruction file). Clause-②: no.The rule to land (one paragraph, in the ADR / governed-territory section — today's anchors are the
docs/adr/-governed guidance around AGENTS.md line ~275 and the governed-surface definition around line ~291; place it where the ADR-citation reader looks, ⛔ no new section header if an existing one fits)Verbatim from the ruling on #14496 (translate for the English file, keep the Chinese quote as the provenance line):
English rendering to land: An ADR lives in the repository whose code it governs. Decisions that draw the open/closed or commercial boundary live in
objectstack-ai/cloudand are cited from this repo ascloud ADR-NNNN— never as a bare number, whichscripts/check-adr-anchors.mjsresolves against this registry (the two registries number independently, so a bare id silently lands on an unrelated local record: 0071 / 0024 / 0081 today). When a cloud decision's mechanism half governs open code in this repo, this repo carries its own ADR — own number, a## Provenancesection naming the cloud record and its date, the commercial half left in cloud — and the cloud record gains a one-line pointer. Files are never moved between registries and numbers are never reassigned.Why here and not only in the gate
The gate already accepts the qualifier structurally (
CROSS_REPO_QUALIFIERS); what it cannot know is which bare number meant the other registry. The rule is what an author reads before writing the citation; the precedent it names (ADR-0079's Provenance section) is what they copy.Constraints
CLAUDE.mdstays as is).scripts/check-adr-anchors.mjsin this PR (a topic-consistency criterion for the gate was deliberately not ordered on [finding] The SCIM/identity ADR-0071 citation resolves to the dataset semantic-layer record — 39 files point at a decision about multi-hop joins #14361).Refs: #14496 (ruling) · #14361 (the re-pointing pass) · the three mirror-ADR sub-issues of #14496 · ADR-0079.