[objectstack-fleet]

Requested by Sales · project thread

Fixes #25107

Clause-②: no (narrowing) — on a walled posture, the security service's admission probes, field projections, access explanation and narrowing diagnostic answer the operation prologue's refusal for an on-behalf-of context whose live active organization the delegator's membership does not back, where they used to answer an admission.
Metadata-protocol: none

Claim of record: 6348946648 on the card (card thread, domain:services seat 1). Branch claude/project-thread-a7kyo3 is the harness-pinned branch for this session; it names no issue, so the Duplicate Fix Guard's branch-name hint will not match, and the claim is the identity record. ⛔ Disclosure (#9387 ruling 5323310017): this body states the rule and an abstract reach only.

The rule

Under isolated or group, the delegated-principal prologue (resolveOperationPrincipals) refuses every operation of an on-behalf-of context whose live active organization the delegator's own membership does not back (ADR-0090 D10, landed with #25063), and the raw-SQL read scope answers that refusal (#25106, PR #25150). Every other reader in plugin-security that resolves a delegator on its own skipped the check, so for such a context it answered an admission the operation refuses. The card names them; this PR makes each one ask.

One ask. delegatedOrganizationRefusal (explain-engine.ts, beside resolveDelegatorContext) asks vetOrganizationClaim once with the prologue's inputs: the live organization (context.tenantId), the delegator's own memberships (accessible_org_ids, never inherited), the posture. It answers the refused organization or undefined. The prologue and computeDelegatedReadFilter now ask it instead of spelling the inputs themselves (byte-identical behaviour: their 42 existing cells stay green unchanged), and every other site asks it at the prologue's point, after a resolved delegator and before the delegator's sets resolve:

site	answer for a refused context (was)
canReadObject	false (could be true)
canWriteObject (insert and update)	false (could be true)
canExport	false (could be true)
resolveProjectionFieldMask, behind getReadableFields, getMetadataReadableFields, getWritableFields, getQueryableFields	[], as for a dangling delegator (the intersected list)
the explain engine's delegated path (explainOnce)	allowed: false; the principal and object_crud layers denies, naming the organization (the D10 intersection)
describeDelegationNarrowing	{ narrowed: false }, as for a dangling delegator (a narrowing)
delegatedWriteContexts (the explanation's per-record write gate and authored-row probe)	null: the gate refuses without asking the sharing service (asked as agent and delegator)

resolveDelegatorContext's docblock no longer says the agent and its delegator are "by construction, in the same org": that is the precondition the helper vets, and the docblock points at it.

ExplainEngineDeps gains a required tenancyPosture, which the security plugin wires from its own posture. Required for the reason the module gives for getPartialMaskRules: an engine wired without it would explain such a context as admitted, the misreport this card closes, and a required member makes the omission a compile error. The seven test files that build the deps by hand pass 'single'. The changeset names this with runtime-interface-only (the interface has no metadata surface; the compiler is the channel that reaches an embedder).

Reach, abstractly

In process only, as the card says: the one producer of an on-behalf-of context (the /mcp door) never builds the shape, and none of these readers serves rows (their consumers run the operation through the engine, which refuses).

Boundary, before and after

• Before: under isolated or group, for such a context the three probes could answer true, the projections the intersected fields, the explanation allowed: true, the diagnostic a narrowing, and the per-record write gate asked the sharing service.
• After: each answers the refusal, as tabled above.
• Unchanged: the single posture; an on-behalf-of context with no active organization; an on-behalf-of context in an organization the delegator belongs to; a context without onBehalfOf; a dangling delegator; system contexts.

Docs

• content/docs/permissions/system-context.mdx, row 6b: the list of arms canWriteObject runs gains, in its fail-closed group, the walled-posture D10 delegator who is not a member of the organization the request runs in (commit 981b7c2f, one line, flagged by the docs drift check).

Pins

All in packages/plugins/plugin-security/src/delegated-organization-membership.test.ts, the rule's file (real ObjectQL from source, real SqlDriver, real SecurityPlugin; the delegator rebuilt from stored rows). 24 new cases; the file goes from 42 to 66. The fixture gains allowExport on its three grants (so the export probe's admitted cells are admitted by a grant) and one object only the narrowing cells read, with a delegator grant and an agent ceiling for it.

• Refusal (10): per walled posture × the three objects (public, private, organization-less): canReadObject, canWriteObject insert and update and canExport are false, the four projections [], the explanation allowed: false with both layers denying and naming the organization; per walled posture, the narrowing diagnostic answers { narrowed: false }, and the explanation's per-record write gate never calls the sharing service's canEdit.
• Preservation (11): per walled posture, a delegated context in a member organization and the undelegated caller are admitted by every probe on every object; a delegated context with no active organization keeps its read answers; the diagnostic still reports a narrowing in a member organization; the write gate still asks canEdit as the agent, then as the delegator; and the single posture admits every probe and reports the narrowing.
• Parity (2): per walled posture, over three contexts × three objects: canReadObject, canExport and the explanation's allowed equal whether the engine's find runs, and canWriteObject insert equals whether the engine's insert runs. The table asserts its refused set, so neither side is vacuous.
• Enumeration (1): per source file in this package, the calls of delegatedOrganizationRefusal equal the calls of resolveDelegatorContext (definitions excluded), and the two files that resolve a delegator are both counted: a tenth reader that resolves one without asking goes red.

One existing pin moves, because this change makes its fixture the refused shape: explain-dependency-fault.test.ts's control "a delegator that resolves leaves the principal layer neutral" runs on a walled stack (org scoping, so isolated) whose delegator had no membership in the organization its agent runs in, so with the fix its principal layer read denies (the package suite caught it). Its fixture seeds that membership, so the cell measures what it names; its sibling (the delegator's grants unreadable, explain fails closed) is untouched.

One-time proofs (not left as tests), each in scripts/ablation-replace.mjs WRAP mode (anchor must hit once, blob must move, restore proven: blob equal to HEAD and git diff HEAD empty). The subject is imported from source (./security-plugin.js), so there is no dist/ leg.

leg	what is undone (tree only)	file reading	red cells
0, red first	both source files at the base (cc8d886d), the new tests kept	13 failed, 53 passed	the 6 refusal cells, the 2 narrowing-refusal cells, the 2 write-gate cells, the 2 parity cells, the enumeration cell; the 42 existing cells green
1	describeDelegationNarrowing's ask	3 failed	narrowing refusal × 2, enumeration
2	delegatedWriteContexts' ask	3 failed	write gate × 2, enumeration
3	resolveProjectionFieldMask's ask	7 failed	refusal × 6, enumeration
4	canReadObject's ask	9 failed	refusal × 6, parity × 2, enumeration
5	canWriteObject's ask	9 failed	refusal × 6, parity × 2, enumeration
6	canExport's ask	9 failed	refusal × 6, parity × 2, enumeration
7	explainOnce's ask	11 failed	refusal × 6, write gate × 2, parity × 2, enumeration
8	the helper itself answers undefined (call counts kept)	36 failed, 30 passed	every refusal cell of the file, the prologue's and the read scope's 24 included; the enumeration cell stays green, as it should (it counts asks)

Every leg restored: blob equal to HEAD (security-plugin.ts 4e9f0dc892a5, explain-engine.ts aee792270aa0) and git diff HEAD empty.

Tests and gates

Read on head 8bb2d5e0, branched from cc8d886d. Every test run went through scripts/pm/os-verify-lock.sh; each exit code was captured before any pipe.

• Dependency closure: pnpm exec turbo run build --filter='@objectstack/dogfood^...' --concurrency=3: VERDICT command-exit 0. The eight packages outside it that check:dual-build-cjs-loads reads were built too (exit 0).
• The package: pnpm --filter @objectstack/plugin-security exec vitest run --maxWorkers=2: Test Files 209 passed (209), Tests 4320 passed | 45 skipped (4365). pnpm --filter @objectstack/plugin-security run typecheck: exit 0.
• The suites outside the package that build an on-behalf-of context through the real SecurityPlugin: objectql engine-readable-ids-nested-composition (12/12), service-storage attachment-read-leaf.integration + attachment-access-hooks (152/152), plugin-sharing authored-row-write-deferral (20/20), plugin-audit comment-access-hooks + parent-record-read-leaf.integration (83/83), runtime http-dispatcher (248/248): each exit 0.
• The derived gate families: node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derived 70 commands; all 70 exit 0 (check:type-check-debt re-run under the lock after its first call timed out queueing behind the battery, which is a prerequisite reading, not a verdict). --ran: 70 derived, 70 run, 0 NOT-MEASURED, 0 UNRUN, exit 0. The three roster gates whose roster sits under a directory this diff touches (check-changeset-fixed, check:error-code-casing, check:filter-alias-parity) were run as well: exit 0.
• Full dogfood battery (the title carries !): pnpm --filter @objectstack/dogfood test, no shard, no path: VERDICT command-exit 0, Test Files 289 passed | 3 skipped (292), Tests 2481 passed | 18 skipped (2499).
• Not run locally, declared to CI: the type-check lanes and the path-scheduled CI jobs dispatch-gates names.

Serial. #25256 (#25095) landed on main after this branch was cut and edits security-plugin.ts in hunks disjoint from these (a test merge is clean); CI's run on this PR reads the merge with it.

Acceptance notes

• The helper lives in explain-engine.ts beside resolveDelegatorContext because the explain engine (a module function, no plugin instance) asks it too; it adds no rule text: vetOrganizationClaim stays the one spelling of "a membership backs this organization".
• The probes answer silently (no log), as each already answers a dangling delegator silently; the prologue and the read scope keep their warn.
• A review at CONTRACT_REVIEW_TIER is owed before the queue (a narrowing).

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/plugin-security, touching 12 documentable anchor(s).

5 hand-written doc(s) NAME something this change touched and may need an implementation-accuracy re-verification:

• content/docs/permissions/field-level-security.mdx (via SecurityPlugin (symbol, a top-level class))
• content/docs/permissions/index.mdx (via SecurityPlugin (symbol, a top-level class))
• content/docs/permissions/system-context.mdx (via canExport (symbol, a method of class SecurityPlugin), canReadObject (symbol, a method of class SecurityPlugin), canWriteObject (symbol, a method of class SecurityPlugin), explainAccessForCaller (symbol, a method of class SecurityPlugin))
• content/docs/plugins/packages.mdx (via SecurityPlugin (symbol, a top-level class))
• content/docs/ui/forms.mdx (via SecurityPlugin (symbol, a top-level class))

⛔ 4 release-owned page(s) also name something this change touched. These are read-only:

• content/docs/releases/implementation-status.mdx (via SecurityPlugin (symbol, a top-level class))
• content/docs/releases/v17/17-5.mdx (via canReadObject (symbol, a method of class SecurityPlugin), canWriteObject (symbol, a method of class SecurityPlugin))
• content/docs/releases/v17/17-6.mdx (via canExport (symbol, a method of class SecurityPlugin), canReadObject (symbol, a method of class SecurityPlugin))
• content/docs/releases/v18/18-0.mdx (via SecurityPlugin (symbol, a top-level class))

content/docs/releases/ is RELEASE-OWNED (AGENTS.md "Documentation Guardrails"): release
notes are written centrally at release time, and a code PR that edits them is the exact PR
that guardrail exists to stop. They are still audited — read-only. If one of them is actually
wrong, file an issue or open a dedicated docs-only PR; do not edit it here.

What this run could not see

• 1 name(s) were too generic to anchor anything (single lowercase words)
• the SDK route bridge reached 54 of 206 client-bound route-ledger rows — the other 152 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 152: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 97 are undecided (no in-repo declaration, on a ledger that has other in-repo registrars — absence and an unreadable spelling are not distinguishable here). The rows themselves: node scripts/docs-audit/affected-docs.mjs --bridge-coverage
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 16 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json c9be979dd1580f2a92db62a0a5104bf2abae1129 → packageMentionDocs.

Which tree this was computed on

This run read content/docs from 1329cb5f6b01ba56dd83313a9ed6687b2d022d0e — the merge of head 981b7c2f04124ccf1308aa6403647f36e69354a9 into base c9be979dd1580f2a92db62a0a5104bf2abae1129, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin 1329cb5f6b01ba56dd83313a9ed6687b2d022d0e && git checkout 1329cb5f6b01ba56dd83313a9ed6687b2d022d0e
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin c9be979dd1580f2a92db62a0a5104bf2abae1129 981b7c2f04124ccf1308aa6403647f36e69354a9 && git checkout -B drift-repro c9be979dd1580f2a92db62a0a5104bf2abae1129 && git merge --no-ff 981b7c2f04124ccf1308aa6403647f36e69354a9

node scripts/docs-audit/affected-docs.mjs --json c9be979dd1580f2a92db62a0a5104bf2abae1129

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

Advisory only, and a precision-first one (#9192): a page is listed because it names a
symbol, wire route or SDK method this diff touched — not because it mentions a changed
package. Each row says which anchor put it there, so a wrong row is reportable rather than
merely annoying. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs c9be979dd1580f2a92db62a0a5104bf2abae1129 → pass the list as
args.docs, on the commit named under Which tree this was computed on.

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 8bb2d5e0d9e4fd57fb9bbc6739e3972c3ff5a347
Local-runs: none
Scope: .changeset/25107-delegation-probes-organization-membership.md, packages/plugins/plugin-security/src/explain-engine.ts, packages/plugins/plugin-security/src/security-plugin.ts, packages/plugins/plugin-security/src/delegated-organization-membership.test.ts, packages/plugins/plugin-security/src/explain-asker-gate.test.ts, packages/plugins/plugin-security/src/explain-controlled-by-parent-write.test.ts, packages/plugins/plugin-security/src/explain-dependency-fault.test.ts, packages/plugins/plugin-security/src/explain-engine.test.ts, packages/plugins/plugin-security/src/explain-positions-name-authority.test.ts, packages/plugins/plugin-security/src/explain-read-absent-record-story.test.ts, packages/plugins/plugin-security/src/metadata-unresolvable-posture.test.ts, packages/plugins/plugin-security/src/unpublished-object-deny-message.test.ts + packages/core/src/security/resolve-authz-context.ts (vetOrganizationClaim), packages/spec/src/security/tenancy-posture.ts (postureEnforcesWall), packages/plugins/plugin-security/src/index.ts (the public export of ExplainEngineDeps), docs/adr/0090-permission-model-v2-concept-convergence.md (D10), docs/adr/0087-metadata-protocol-upgrade-contract.md, .github/workflows/pr-automation.yml (Check Changeset), scripts/check-adr-0087-registration.mjs, scripts/check-changeset-no-major.mjs, AGENTS.md (Post-Task Checklist step 3)

Inputs: card #25107 (body, claim 6348946648, os-dev-report 6350577797), PR #25288 (body, 12-file list, net diff against main), the head's check-runs. Read only; nothing built, run or ablated here. Face: fix(plugin-security)! with Clause-②: no (narrowing) on the body and the changeset, no governed path, no published schema. Disclosure ruling (#9387, 5323310017) observed: this record states the rule, the sites and the classes of answer; no probe, context shape, request, posture value set or payload.

① Derived judgments

The one helper — right. delegatedOrganizationRefusal (explain-engine.ts, beside resolveDelegatorContext, exported) asks vetOrganizationClaim once with exactly the prologue's three inputs: the live organization read off the operation's own context (the same null-and-empty guard the prologue spelled, then stringified the same way), the delegator's OWN membership set read off the resolved delegator context (the set resolveDelegatorContext deliberately does not inherit, ADR-0105 D2; the same empty default), and the plugin's posture. It answers the live organization where the claim is dropped and nothing otherwise. Read in core: vetOrganizationClaim returns the claim unchanged when no wall is enforced (postureEnforcesWall is "not the non-walled posture") and otherwise answers it only when the membership set contains it, so the helper refuses nothing under the non-walled posture, nothing for a context with no active organization, nothing for a member organization. No second spelling of the membership rule was introduced; vetOrganizationClaim stays the one, and its remaining import in security-plugin.ts is live (the explain caller's own organization vetting, untouched).

The prologue (resolveOperationPrincipals) — byte-identical in behaviour. Before: compute the live organization, refuse when the claim is dropped, name that organization in the refusal. After: the helper's answer IS that organization, bound to the same local, so the warn, the PermissionDeniedError text and its prescription are produced from the same value at the same point (after the dangling-delegator missing throw, before the delegator's sets resolve, inside the same permissionSets non-empty AND on-behalf-of guard). The guest refusal, the principal-less refusal and the fail-closed set-resolution catch ahead of it are untouched.

computeDelegatedReadFilter (#25106's arm) — byte-identical in behaviour. Same point (after the no-set deny sentinel and the dangling-delegator deny sentinel, before the delegator's sets resolve), same warn, same deny sentinel; only the inline spelling was replaced by the helper. The dev's helper-ablation leg (the helper answering nothing, call sites kept) is reported as reddening the prologue's and the read scope's 24 pre-existing cells, which is the reading that proves the re-pointing carries the rule rather than duplicating it.

Every site the card names asks at the prologue's point — right, nothing left out, none wider than the prologue. Read at the head, each ask sits immediately after a resolved delegator and before any read of the delegator's sets, and each answers the same value the site already answers for a dangling delegator:

• canReadObject: after the system bypass, the principal-less refusal and the no-set deny, inside the on-behalf-of branch after missing — answers false.
• canWriteObject: after the caller-class gates, the principal-less refusal, the no-set deny and the unresolved-posture deny, inside the on-behalf-of branch after missing — answers false; the branch is shared by every write verb the probe serves, not only insert and update, and the organization-wall arm downstream still receives the delegator's sets only when the ask admits.
• canExport: after the no-set deny, the unresolved-posture deny and the caller's own export check, inside the on-behalf-of branch after missing — answers false.
• resolveProjectionFieldMask: inside the same permissionSets non-empty AND on-behalf-of guard the prologue uses, after missing's empty answer — answers the empty projection; the four public readers (getReadableFields, getMetadataReadableFields, getWritableFields, getQueryableFields) all route through it at the head, so all four narrow together.
• explainOnce (the delegated path): after a resolved settle, before resolveSets on the delegator; a refused context leaves the delegator's context and sets unset exactly as missing does, a single delegatorRefused fold (missing, unresolved, outside-organization) drives the principal layer's denies, crudAllowed and thence allowed (allowed is derived from crudAllowed, read at the head), and the two layer details name the D10 fail-closed cause instead of the intersection. The agent-only allowed: true is unreachable for that shape.
• describeDelegationNarrowing: after the system and no-link early returns and after resolved — answers the no-narrowing value, as for a dangling delegator (a diagnostic that reports no narrowing for a read the operation refuses is the correct non-answer; it decides nothing).
• delegatedWriteContexts: after resolved — answers null, which both consumers already treat as the refusal (the per-record write gate returns false without asking the sharing service; the authored-row probe abstains). Both consumers read at the head.

No site answers wider than the prologue: each ask takes the same context the operation would carry and the same resolved delegator, and sits behind guards at least as strict as the prologue's. No reader resolving a delegator is left out: repo-wide on current main, resolveDelegatorContext is called from exactly the two files the diff touches (eight call sites in security-plugin.ts, one in explain-engine.ts), the head carries an ask beside every one of the nine, and no other plugin-security source file reads the delegation link at all. The remaining on-behalf-of readers in security-plugin.ts that do not resolve a delegator (the sharing write-scope defaults, the authored-row abstain, the master-detail floor exclusion) answer fail-closed constants or sit behind the prologue (checkControlledByParentWrite calls it), so none can serve an admission the operation refuses.

What stays unchanged — right. The non-walled posture (the claim stands in core); a context with no active organization (the helper answers nothing before asking core, ADR-0123 D2 keeps those answers); a member organization; a context without the delegation link (every ask is inside an on-behalf-of branch); a dangling delegator (the missing arms precede every ask and are untouched); system contexts (the three probes and the narrowing diagnostic return before any delegator is resolved, unchanged; the explanation had no system short-circuit before this change and gains none, a narrowing-only difference for a shape ADR-0090 D10 rule 2 forbids an agent principal to carry). The docblock edits on resolveDelegatorContext and the prologue replace the "same organization by construction" assumption with a pointer at the precondition; the inheritance of the live organization into the delegator context is unchanged in code.

ExplainEngineDeps.tenancyPosture (required) — right and wired everywhere. The one real constructor is the plugin's explainAccessForCaller, which passes its own posture (the field every enforcement path reads, set once at init from the tenancy service, else from the org-scoping probe, else the non-walled default); the deps literal is built per call, so it reads the live value. Repo-wide on current main, no other package constructs or imports ExplainEngineDeps and no package outside plugin-security calls the explain entry points; the seven hand-built test bags each carry the member at their base builder, and the derived bags (readOnlyRls, recDeps, recOf, the Partial override) spread a base that has it. The type is exported from the package index, so an embedder is reached by the compiler, as the changeset says. Making it required rather than defaulted is the module's own documented rule for a dep whose omission would misreport (getPartialMaskRules); a default would have reintroduced the misreport silently.

Pins — real negative pins, ablation reported per site. The 24 new cells in the rule's file run the real engine, driver and plugin with the delegator rebuilt from stored rows. Refusal cells assert the refused value per probe, per walled posture, per object class, and assert the explanation's two layer verdicts and the cause they name; the write-gate cells assert the sharing service's edit gate is never called; the preservation cells assert every admitted class keeps every admission (member organization, undelegated caller, no active organization, the non-walled posture, the narrowing still reported, the gate still asked twice in order); the parity cells equate each probe with the engine operation it describes over a context-by-object table and assert the refused set is exactly the one row class, so neither side is vacuous; the enumeration cell counts asks against resolutions per source file and pins that both files are counted. The fixture's export grant on every set is what keeps the export refusal attributable to this rule alone, as the card's D10-intersection caution requires. Red-first at the base with the new tests (13 red, exactly the non-preservation cells) and one WRAP-mode ablation leg per site (7 legs, each reddening its own cells plus the enumeration cell, plus the helper leg reddening every refusal cell including the pre-existing 24) are reported with restore proofs. Read-only here: I accept those readings as the dev's and note the check-runs on this head as the gate verdicts.

The moved control — not a relaxation. explain-dependency-fault.test.ts's "a delegator that resolves leaves the principal layer neutral" runs on a walled stack whose fixture delegator held no membership in the agent's organization; with the rule that is the refused shape, so the control would have measured this rule instead of what it names. The fixture gains the membership row; the assertion is unchanged and its fail-closed sibling is untouched.

Lane floor. Every accept-set change in this diff is allow-to-deny, aligned with the operation prologue; no permission or security boundary is relaxed anywhere in the diff or the cited code.

② Semver level

Changeset .changeset/25107-delegation-probes-organization-membership.md: @objectstack/plugin-security at patch, BREAKING banner, Clause-②: no (narrowing), Metadata-protocol: none, exactly one ADR-0087 marker not-required (runtime-interface-only packages/plugins/plugin-security/src/explain-engine.ts#ExplainEngineDeps) …, FROM/TO/Unchanged/fix blocks present. The PR body carries the same two declaration lines.

Right, on the house rules. AGENTS.md Post-Task step 3: the level follows the metadata-protocol kind alone; none takes patch; a non-protocol change, widening or breaking, ships patch and keeps its BREAKING banner and ADR-0087 disposition. check-changeset-no-major.mjs ruling A grades no (narrowing) beside none as none-clean and refuses minor for it; major is forbidden in the launch window. The diff publishes two things, both non-protocol: an accept-set narrowing of runtime answers (no spec key, authorable spelling or stored shape moves) and a required member on a published TS-only runtime interface, which is the category runtime-interface-only exists for; the marker names the symbol by path#Symbol as the gate's grammar requires, and the Check Changeset job (which runs check-adr-0087-registration.mjs against the merge base and the Clause-② reader) concluded success on this head, verifying the symbol is a non-Zod type declaration with no metadata surface. The migration text names the remedy for an in-process producer and for an embedder. Clause-②: no (narrowing) is the correct arm: nothing widens.

③ Boundary flags

• Dev report 6350577797: open_questions: [], out_of_scope_findings: [], premise_still_valid: true. Nothing to answer; nothing escalated.
• Dev note, serial with fix(plugin-security)!: under a controlled_by_parent declaration whose one master reference is readonly or system, every write that sets it is refused (ADR-0055 §1) #25256 (landed on main after the branch point, same file, disjoint hunks): the API reports the PR mergeable against current main, and CI read the merge ref — answered.
• Dev note, "a CONTRACT_REVIEW_TIER review of record is owed before the queue": this record is it.
• Reviewer flag, the enumeration pin is a source-text count (asks per file equal resolutions per file; both files named). It pins presence, not position; position is pinned by the behavioural cells and was proven per site by the ablation legs. Adequate as a tripwire for a tenth reader; noted, not escalated.
• Reviewer flag, the explanation path has no system short-circuit before or after (the probes do). Narrowing-only for a shape D10 forbids; the card's "system contexts unchanged" holds for every path that had a system exit. Noted, not escalated.
• Reviewer flag, the card's file surface said "⛔ Not packages/core, packages/spec, plugin-sharing or any other plugin": held; the 12 files are all under packages/plugins/plugin-security/src/ plus the changeset.
• Disclosure: the PR body, the changeset and this record state the rule, the sites and the roles of the inputs; the changeset's remedy names what a producer sets, a prescription and not a shape. Within the ruling.
• Check-runs on 8bb2d5e0: at review time 27 concluded success and 7 skipped (path-scheduled lanes), none red: Check Changeset, Governed Surface Queue Guard, Lint · ESLint, Lint · PM dispatch-gates, Lint · docs & code guards, Lint · CI, release & engine gates, Lint · repo & tooling gates, both Lint · scoped lanes and the query-options erasure lane, Type Check · workspace, Type Check · source gates, Type Check · consumer gates, Type Check · debt ledger, Build Core, Dogfood Regression Gate, the claim and single-writer guards, Check PR Size, Check Documentation Links. Still running when this record was written: Test Core shards 1/6 to 6/6. Their conclusions are the gate verdicts for the test family; this PASS is conditional on those six concluding success, and the queue's required set holds that condition mechanically.

Implemented-by: claude/project-thread-a7kyo3
Reviewed-by: session_016g7nYP9wdNx1GDa5XDr7Uy

VERDICT: PASS

[objectstack-fleet]

席位核对 · ACCEPT · 2026-10-22T21:20Z

domain:services seat 1 (seat post #6021) · os-sales · session_016g7nYP9wdNx1GDa5XDr7Uy · card #25107 (claim 6348946648; card session branch claude/project-thread-a7kyo3) · reviewed head 981b7c2f04124ccf1308aa6403647f36e69354a9 (code head 8bb2d5e0d9)

⛔ Disclosure (#9387): abstract. The PR body, the report 6350577797 and the contract review were read for probes, context shapes or payloads first; none carries one.

• Shape: one helper, delegatedOrganizationRefusal, asks vetOrganizationClaim once with the operation prologue's inputs. The prologue and the raw-SQL read scope (plugin-security: the raw-SQL read-scope provider (getReadFilter) does not apply the delegated organization-membership rule PR #25101 enforces at the operation prologue; measure reach first (detail withheld) #25106) are re-pointed to it with unchanged behaviour, and the seven sites the card names now ask it at the prologue's point and answer their existing dangling-delegator value. ExplainEngineDeps gains a required tenancyPosture, wired by its one real constructor. 13 files, +420 / −50 (with the docs line).
• Head delta: 8bb2d5e0d9...981b7c2f04 is one commit and one line in content/docs/permissions/system-context.mdx (row 6b names the new fail-closed arm of canWriteObject), read by the seat and true to the code. The contract review, the dogfood battery and the pins were taken on 8bb2d5e0d9, whose code this head carries unchanged; the derived gates were re-run on this head (100 / 100). The seat added a Docs line to the body.
• Contract review: CONTRACT_REVIEW_TIER, isolated, record 6350743954 on the code head 8bb2d5e0d9 — PASS, Local-runs: none. Every accept-set change is allow-to-deny; no boundary is relaxed (lane floor checked).
• Declarations: fix(plugin-security)!, Clause-②: no (narrowing), Metadata-protocol: none, patch with the BREAKING banner, ADR-0087 not-required (runtime-interface-only …#ExplainEngineDeps); Check Changeset green.
• Pins and ablation: 24 new real-engine cases (42 → 66 in the rule's file), 13 red at base; each of the 8 sites ablated red and restored.
• Dogfood battery: full, on the code head 8bb2d5e0d9 (289 files / 2481 tests pass, VERDICT 0).
• Gates: dispatch-gates --ran 70 / 70 on the code head and 100 / 100 on this head; plugin-security 209 files / 4320 pass; the delegation cases in 5 packages green; every check-run on this head success or an expected skip.
• Serial: fix(plugin-security)!: under a controlled_by_parent declaration whose one master reference is readonly or system, every write that sets it is refused (ADR-0055 §1) #25256 landed first on the same file; the hunks do not meet and CI reads the merge ref.
• Landing: not governed (check-governed-merges --pr 25288: 470 lines). Ready + auto-merge through the relay.

---

Generated by Claude Code