docs(objectql): point the sibling-seam prose at the recorded ruling

[os-musk]

Fixes#14693

Three passages in packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts still said the readonlyWhen sibling seam was "WITHHELD pending a maintainer ruling" and headed "to the decision inbox, never resolved here". It was ruled — #14259, maintainer ruling B: that seam keeps value equality, a self-assigning hook does not unlock a readonlyWhen state lock, and the asymmetry with the static face is deliberate. #14690 then landed the corrected isCallerSuppliedValue docblock plus a measurement pin on each face, and a cross-reference into this file — so a PR whose purpose is to document the ruling now routes readers straight into the sentence that contradicts it.

Comment-only. Every assertion, test name and fixture is untouched: git diff -U0 on the changed file, with the comment lines filtered out, returns nothing. The stale prose is replaced with a pointer to where the argument now lives rather than a fourth copy of it.

What changed

Two comment blocks, carrying the three stale lines triage measured at :23, :30 and :352 (all three re-measured unmoved on this branch's base 7a17f3bf1):

1. The file header's "THE SIBLING SEAM IS DELIBERATELY NOT HERE" block — lines 21-30, holding the :23 and :30 lines. It now records that the seam was ruled and names where the argument lives. The measurement narrative it used to carry (threading the record turns LOCK 3b red, closed_note committing the forgery) is deliberately not repeated: it lives in the docblock and in LOCK 3b itself.
2. The closing sentence of the MEASURED: a lone self-assigning hook leaves the CALLER value on the key block — the :352 line. "#14259's fork clause sends that one to the decision inbox; nothing here resolves it." becomes a statement that the fork was ruled, plus the pointer.

Where the pointer aims, and why that target is stable

isCallerSuppliedValue's docblock in packages/objectql/src/validation/rule-validator.ts, plus the two face pins named by test name:

• static face — MEASURED: a lone self-assigning hook leaves the CALLER value on the key, in this suite (insert side) and engine-readonly-strip-caller-values.test.ts (update side);
• lock face — LOCK 3b in engine-readonly-when-derived-writes.test.ts.

All three are symbol and test names, never line numbers — a line number is the thing that rots and produces the next card exactly like this one. It is also the idiom #14690 already established: both landed pins close with "isCallerSuppliedValue's docblock carries the argument", so this file now reads the same way as its two siblings instead of contradicting them.

Deliberately left alone: the conditional at lines 359-362 ("A ruling that self-assignment must NOT count would move this pin and #14088's seam together; that is a deliberate follow-up, not silent drift"). It is a hypothetical future reversal, framed exactly as #14690's landed pins frame it ("A future ruling that reverses this INVERTS both pins together; it never deletes either") — it does not assert the question is open.

Verification (all at ad84d2315, the head of this branch)

Behaviour cannot move on a comment-only diff, and it is cheap to show that either side:

• before (base 7a17f3bf1, after building the dependency closure pnpm --filter '@objectstack/objectql^...' build): engine-hook-provenance-sibling-seams.test.ts — Test Files 1 passed (1) · Tests 13 passed (13).
• after (ad84d2315), this file plus both face pins the new prose points at: Test Files 3 passed (3) · Tests 60 passed (60).

Both runs went through scripts/pm/os-verify-lock.sh (VERDICT command-exit 0).

Gate family re-derived on the final tree with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts at ad84d2315 — 28 commands. 24 green, plus check:nul-bytes green. Three exited 3, which each gate defines as its own PREREQUISITE-NOT-MET branch — recorded as NOT MEASURED, in the gates' own words, and not as a pass:

• check-test-completeness: "PREREQUISITE NOT MET — this gate grades a saved turbo run test log, and no log was named. … running the family locally, record this gate as NOT MEASURED."
• check:type-check-debt: "PREREQUISITE NOT MET … --re-measure cannot run: 41 workspace dependenc(ies) of the ledgered packages have no built type entry point on disk". Its self-test and the coverage half passed (check:type-check-coverage exit 0).
• check:dual-build-cjs-loads: "PREREQUISITE NOT MET — this gate reads built output, and some package has no dist/." Its 93-case self-test passed.

All three need a whole-repo build, which is CI's run, not this PR's.

Changeset

skip-changeset: the diff is one test file, comment-only. Nothing is published from any package and no behaviour moves. The label is applied on this PR.

---

🤖 Generated with Claude Code

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 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.

Coarse fallback — 0 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 7a17f3bf1e48e1e88f8e833a794e37bd40230f17 → packageMentionDocs.

[os-musk]

Landing provenance — domain:engine execution seat

Enqueued at ad84d2315.

1. The ruling's ⛔ verified by content, not by the PR's word. Triage ruled "Comment-only. Every assertion in the file stays untouched." The diff is one file, +13/−12, and every changed line is a // comment — no assertion, test name or fixture moved. The dev's own mechanical check (git diff -U0 with comment lines filtered → empty) agrees with reading the patch.

2. Clause ② — no. No new exported symbol and no new key on an already-published payload, so the mechanical floor (#14696) is not hit, and no conformance-class judgement arises: a comment inside a test file reaches no consumer. In-seat review therefore permitted; no needs:contract-review. skip-changeset is the landed precedent for a comment-and-test-only diff.

3. Governed-surface predicate, re-run on the FINAL file list — ⛔ not recalled:

node scripts/pm/check-governed-merges.mjs --test \
packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts
→ 0 of 1 path(s) hit the register (5 surfaces) — NOT governed; ordinary queue landing applies.

4. Every check run green or skipped — 40 check runs read at perPage: 50, each by its own completed + conclusion, ⛔ never by an aggregate. Test Core (1/6) again the long shard (23:56:29Z → 00:16:34Z, ~20 min) and Lint & Repo Gates ~16½ min; both green.

5. Flipped draft: false, read back draft: false, then armed auto-merge SQUASH.⚠️ The API echo reads method: MERGE regardless of what is requested — a known platform artifact; the merge-queue build ref is the authoritative reading.

⚠️The flip and the arm were delayed ~25 minutes by a GitHub rate limit, and the shape is worth recording: the GraphQL pool was exhausted while REST was not. pull_request_read (REST) answered normally throughout, so CI could be read and the PR judged; update_pull_request and search_issues (GraphQL) refused. ⛔ The seat stopped retrying rather than burning quota, and the git read channel — fetch, ls-remote, grep — was unaffected the whole time. Prior sessions recorded this class of outage as "account-wide"; it is not, and the distinction decides what work can continue during one.

⭐ One correction the seat owes this card

The dispatch told the dev that isCallerSuppliedValue was not in rule-validator.ts or engine.ts — "I grepped and got nothing, so it is somewhere else." That was wrong: it is in packages/objectql/src/**validation**/rule-validator.ts, 9 hits, definition at :623, corrected docblock at :578-621. The seat's grep used a path missing the validation/ segment and ran no control, so a path typo and a real absence were indistinguishable — the exact failure the standing zero-hit rule exists to prevent, violated by the seat that wrote the rule down.

⭐ It cost nothing because the dispatch handed the claim over as a Zone 2 item to measure rather than as fact, and told the dev its pointer would be worthless if it named the wrong file. The dev found the real location and said so. That is the third time this shift a labelled-as-assumption has caught a seat error before it reached a PR.

---

Generated by Claude Code

[os-musk]

Fixes#14693

Three passages in packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts still said the readonlyWhen sibling seam was "WITHHELD pending a maintainer ruling" and headed "to the decision inbox, never resolved here". It was ruled — #14259, maintainer ruling B: that seam keeps value equality, a self-assigning hook does not unlock a readonlyWhen state lock, and the asymmetry with the static face is deliberate. #14690 then landed the corrected isCallerSuppliedValue docblock plus a measurement pin on each face, and a cross-reference into this file — so a PR whose purpose is to document the ruling now routes readers straight into the sentence that contradicts it.

Comment-only. Every assertion, test name and fixture is untouched: git diff -U0 on the changed file, with the comment lines filtered out, returns nothing. The stale prose is replaced with a pointer to where the argument now lives rather than a fourth copy of it.

What changed

Two comment blocks, carrying the three stale lines triage measured at :23, :30 and :352 (all three re-measured unmoved on this branch's base 7a17f3bf1):

1. The file header's "THE SIBLING SEAM IS DELIBERATELY NOT HERE" block — lines 21-30, holding the :23 and :30 lines. It now records that the seam was ruled and names where the argument lives. The measurement narrative it used to carry (threading the record turns LOCK 3b red, closed_note committing the forgery) is deliberately not repeated: it lives in the docblock and in LOCK 3b itself.
2. The closing sentence of the MEASURED: a lone self-assigning hook leaves the CALLER value on the key block — the :352 line. "#14259's fork clause sends that one to the decision inbox; nothing here resolves it." becomes a statement that the fork was ruled, plus the pointer.

Where the pointer aims, and why that target is stable

isCallerSuppliedValue's docblock in packages/objectql/src/validation/rule-validator.ts, plus the two face pins named by test name:

• static face — MEASURED: a lone self-assigning hook leaves the CALLER value on the key, in this suite (insert side) and engine-readonly-strip-caller-values.test.ts (update side);
• lock face — LOCK 3b in engine-readonly-when-derived-writes.test.ts.

All three are symbol and test names, never line numbers — a line number is the thing that rots and produces the next card exactly like this one. It is also the idiom #14690 already established: both landed pins close with "isCallerSuppliedValue's docblock carries the argument", so this file now reads the same way as its two siblings instead of contradicting them.

Deliberately left alone: the conditional at lines 359-362 ("A ruling that self-assignment must NOT count would move this pin and #14088's seam together; that is a deliberate follow-up, not silent drift"). It is a hypothetical future reversal, framed exactly as #14690's landed pins frame it ("A future ruling that reverses this INVERTS both pins together; it never deletes either") — it does not assert the question is open.

Verification (all at ad84d2315, the head of this branch)

Behaviour cannot move on a comment-only diff, and it is cheap to show that either side:

• before (base 7a17f3bf1, after building the dependency closure pnpm --filter '@objectstack/objectql^...' build): engine-hook-provenance-sibling-seams.test.ts — Test Files 1 passed (1) · Tests 13 passed (13).
• after (ad84d2315), this file plus both face pins the new prose points at: Test Files 3 passed (3) · Tests 60 passed (60).

Both runs went through scripts/pm/os-verify-lock.sh (VERDICT command-exit 0).

Gate family re-derived on the final tree with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts at ad84d2315 — 28 commands. 24 green, plus check:nul-bytes green. Three exited 3, which each gate defines as its own PREREQUISITE-NOT-MET branch — recorded as NOT MEASURED, in the gates' own words, and not as a pass:

• check-test-completeness: "PREREQUISITE NOT MET — this gate grades a saved turbo run test log, and no log was named. … running the family locally, record this gate as NOT MEASURED."
• check:type-check-debt: "PREREQUISITE NOT MET … --re-measure cannot run: 41 workspace dependenc(ies) of the ledgered packages have no built type entry point on disk". Its self-test and the coverage half passed (check:type-check-coverage exit 0).
• check:dual-build-cjs-loads: "PREREQUISITE NOT MET — this gate reads built output, and some package has no dist/." Its 93-case self-test passed.

All three need a whole-repo build, which is CI's run, not this PR's.

Changeset

skip-changeset: the diff is one test file, comment-only. Nothing is published from any package and no behaviour moves. The label is applied on this PR.

---

🤖 Generated with Claude Code

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 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.

Coarse fallback — 0 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 7a17f3bf1e48e1e88f8e833a794e37bd40230f17 → packageMentionDocs.

[os-musk]

Landing provenance — domain:engine execution seat

Enqueued at ad84d2315.

1. The ruling's ⛔ verified by content, not by the PR's word. Triage ruled "Comment-only. Every assertion in the file stays untouched." The diff is one file, +13/−12, and every changed line is a // comment — no assertion, test name or fixture moved. The dev's own mechanical check (git diff -U0 with comment lines filtered → empty) agrees with reading the patch.

2. Clause ② — no. No new exported symbol and no new key on an already-published payload, so the mechanical floor (#14696) is not hit, and no conformance-class judgement arises: a comment inside a test file reaches no consumer. In-seat review therefore permitted; no needs:contract-review. skip-changeset is the landed precedent for a comment-and-test-only diff.

3. Governed-surface predicate, re-run on the FINAL file list — ⛔ not recalled:

node scripts/pm/check-governed-merges.mjs --test \
packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts
→ 0 of 1 path(s) hit the register (5 surfaces) — NOT governed; ordinary queue landing applies.

4. Every check run green or skipped — 40 check runs read at perPage: 50, each by its own completed + conclusion, ⛔ never by an aggregate. Test Core (1/6) again the long shard (23:56:29Z → 00:16:34Z, ~20 min) and Lint & Repo Gates ~16½ min; both green.

5. Flipped draft: false, read back draft: false, then armed auto-merge SQUASH.⚠️ The API echo reads method: MERGE regardless of what is requested — a known platform artifact; the merge-queue build ref is the authoritative reading.

⚠️The flip and the arm were delayed ~25 minutes by a GitHub rate limit, and the shape is worth recording: the GraphQL pool was exhausted while REST was not. pull_request_read (REST) answered normally throughout, so CI could be read and the PR judged; update_pull_request and search_issues (GraphQL) refused. ⛔ The seat stopped retrying rather than burning quota, and the git read channel — fetch, ls-remote, grep — was unaffected the whole time. Prior sessions recorded this class of outage as "account-wide"; it is not, and the distinction decides what work can continue during one.

⭐ One correction the seat owes this card

The dispatch told the dev that isCallerSuppliedValue was not in rule-validator.ts or engine.ts — "I grepped and got nothing, so it is somewhere else." That was wrong: it is in packages/objectql/src/**validation**/rule-validator.ts, 9 hits, definition at :623, corrected docblock at :578-621. The seat's grep used a path missing the validation/ segment and ran no control, so a path typo and a real absence were indistinguishable — the exact failure the standing zero-hit rule exists to prevent, violated by the seat that wrote the rule down.

⭐ It cost nothing because the dispatch handed the claim over as a Zone 2 item to measure rather than as fact, and told the dev its pointer would be worthless if it named the wrong file. The dev found the real location and said so. That is the third time this shift a labelled-as-assumption has caught a seat error before it reached a PR.

---

Generated by Claude Code

[os-musk]

Fixes#14693

Three passages in packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts still said the readonlyWhen sibling seam was "WITHHELD pending a maintainer ruling" and headed "to the decision inbox, never resolved here". It was ruled — #14259, maintainer ruling B: that seam keeps value equality, a self-assigning hook does not unlock a readonlyWhen state lock, and the asymmetry with the static face is deliberate. #14690 then landed the corrected isCallerSuppliedValue docblock plus a measurement pin on each face, and a cross-reference into this file — so a PR whose purpose is to document the ruling now routes readers straight into the sentence that contradicts it.

Comment-only. Every assertion, test name and fixture is untouched: git diff -U0 on the changed file, with the comment lines filtered out, returns nothing. The stale prose is replaced with a pointer to where the argument now lives rather than a fourth copy of it.

What changed

Two comment blocks, carrying the three stale lines triage measured at :23, :30 and :352 (all three re-measured unmoved on this branch's base 7a17f3bf1):

1. The file header's "THE SIBLING SEAM IS DELIBERATELY NOT HERE" block — lines 21-30, holding the :23 and :30 lines. It now records that the seam was ruled and names where the argument lives. The measurement narrative it used to carry (threading the record turns LOCK 3b red, closed_note committing the forgery) is deliberately not repeated: it lives in the docblock and in LOCK 3b itself.
2. The closing sentence of the MEASURED: a lone self-assigning hook leaves the CALLER value on the key block — the :352 line. "#14259's fork clause sends that one to the decision inbox; nothing here resolves it." becomes a statement that the fork was ruled, plus the pointer.

Where the pointer aims, and why that target is stable

isCallerSuppliedValue's docblock in packages/objectql/src/validation/rule-validator.ts, plus the two face pins named by test name:

• static face — MEASURED: a lone self-assigning hook leaves the CALLER value on the key, in this suite (insert side) and engine-readonly-strip-caller-values.test.ts (update side);
• lock face — LOCK 3b in engine-readonly-when-derived-writes.test.ts.

All three are symbol and test names, never line numbers — a line number is the thing that rots and produces the next card exactly like this one. It is also the idiom #14690 already established: both landed pins close with "isCallerSuppliedValue's docblock carries the argument", so this file now reads the same way as its two siblings instead of contradicting them.

Deliberately left alone: the conditional at lines 359-362 ("A ruling that self-assignment must NOT count would move this pin and #14088's seam together; that is a deliberate follow-up, not silent drift"). It is a hypothetical future reversal, framed exactly as #14690's landed pins frame it ("A future ruling that reverses this INVERTS both pins together; it never deletes either") — it does not assert the question is open.

Verification (all at ad84d2315, the head of this branch)

Behaviour cannot move on a comment-only diff, and it is cheap to show that either side:

• before (base 7a17f3bf1, after building the dependency closure pnpm --filter '@objectstack/objectql^...' build): engine-hook-provenance-sibling-seams.test.ts — Test Files 1 passed (1) · Tests 13 passed (13).
• after (ad84d2315), this file plus both face pins the new prose points at: Test Files 3 passed (3) · Tests 60 passed (60).

Both runs went through scripts/pm/os-verify-lock.sh (VERDICT command-exit 0).

Gate family re-derived on the final tree with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts at ad84d2315 — 28 commands. 24 green, plus check:nul-bytes green. Three exited 3, which each gate defines as its own PREREQUISITE-NOT-MET branch — recorded as NOT MEASURED, in the gates' own words, and not as a pass:

• check-test-completeness: "PREREQUISITE NOT MET — this gate grades a saved turbo run test log, and no log was named. … running the family locally, record this gate as NOT MEASURED."
• check:type-check-debt: "PREREQUISITE NOT MET … --re-measure cannot run: 41 workspace dependenc(ies) of the ledgered packages have no built type entry point on disk". Its self-test and the coverage half passed (check:type-check-coverage exit 0).
• check:dual-build-cjs-loads: "PREREQUISITE NOT MET — this gate reads built output, and some package has no dist/." Its 93-case self-test passed.

All three need a whole-repo build, which is CI's run, not this PR's.

Changeset

skip-changeset: the diff is one test file, comment-only. Nothing is published from any package and no behaviour moves. The label is applied on this PR.

---

🤖 Generated with Claude Code

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 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.

Coarse fallback — 0 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 7a17f3bf1e48e1e88f8e833a794e37bd40230f17 → packageMentionDocs.

[os-musk]

Landing provenance — domain:engine execution seat

Enqueued at ad84d2315.

1. The ruling's ⛔ verified by content, not by the PR's word. Triage ruled "Comment-only. Every assertion in the file stays untouched." The diff is one file, +13/−12, and every changed line is a // comment — no assertion, test name or fixture moved. The dev's own mechanical check (git diff -U0 with comment lines filtered → empty) agrees with reading the patch.

2. Clause ② — no. No new exported symbol and no new key on an already-published payload, so the mechanical floor (#14696) is not hit, and no conformance-class judgement arises: a comment inside a test file reaches no consumer. In-seat review therefore permitted; no needs:contract-review. skip-changeset is the landed precedent for a comment-and-test-only diff.

3. Governed-surface predicate, re-run on the FINAL file list — ⛔ not recalled:

node scripts/pm/check-governed-merges.mjs --test \
packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts
→ 0 of 1 path(s) hit the register (5 surfaces) — NOT governed; ordinary queue landing applies.

4. Every check run green or skipped — 40 check runs read at perPage: 50, each by its own completed + conclusion, ⛔ never by an aggregate. Test Core (1/6) again the long shard (23:56:29Z → 00:16:34Z, ~20 min) and Lint & Repo Gates ~16½ min; both green.

5. Flipped draft: false, read back draft: false, then armed auto-merge SQUASH.⚠️ The API echo reads method: MERGE regardless of what is requested — a known platform artifact; the merge-queue build ref is the authoritative reading.

⚠️The flip and the arm were delayed ~25 minutes by a GitHub rate limit, and the shape is worth recording: the GraphQL pool was exhausted while REST was not. pull_request_read (REST) answered normally throughout, so CI could be read and the PR judged; update_pull_request and search_issues (GraphQL) refused. ⛔ The seat stopped retrying rather than burning quota, and the git read channel — fetch, ls-remote, grep — was unaffected the whole time. Prior sessions recorded this class of outage as "account-wide"; it is not, and the distinction decides what work can continue during one.

⭐ One correction the seat owes this card

The dispatch told the dev that isCallerSuppliedValue was not in rule-validator.ts or engine.ts — "I grepped and got nothing, so it is somewhere else." That was wrong: it is in packages/objectql/src/**validation**/rule-validator.ts, 9 hits, definition at :623, corrected docblock at :578-621. The seat's grep used a path missing the validation/ segment and ran no control, so a path typo and a real absence were indistinguishable — the exact failure the standing zero-hit rule exists to prevent, violated by the seat that wrote the rule down.

⭐ It cost nothing because the dispatch handed the claim over as a Zone 2 item to measure rather than as fact, and told the dev its pointer would be worthless if it named the wrong file. The dev found the real location and said so. That is the third time this shift a labelled-as-assumption has caught a seat error before it reached a PR.

---

Generated by Claude Code

[os-musk]

Fixes#14693

Three passages in packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts still said the readonlyWhen sibling seam was "WITHHELD pending a maintainer ruling" and headed "to the decision inbox, never resolved here". It was ruled — #14259, maintainer ruling B: that seam keeps value equality, a self-assigning hook does not unlock a readonlyWhen state lock, and the asymmetry with the static face is deliberate. #14690 then landed the corrected isCallerSuppliedValue docblock plus a measurement pin on each face, and a cross-reference into this file — so a PR whose purpose is to document the ruling now routes readers straight into the sentence that contradicts it.

Comment-only. Every assertion, test name and fixture is untouched: git diff -U0 on the changed file, with the comment lines filtered out, returns nothing. The stale prose is replaced with a pointer to where the argument now lives rather than a fourth copy of it.

What changed

Two comment blocks, carrying the three stale lines triage measured at :23, :30 and :352 (all three re-measured unmoved on this branch's base 7a17f3bf1):

1. The file header's "THE SIBLING SEAM IS DELIBERATELY NOT HERE" block — lines 21-30, holding the :23 and :30 lines. It now records that the seam was ruled and names where the argument lives. The measurement narrative it used to carry (threading the record turns LOCK 3b red, closed_note committing the forgery) is deliberately not repeated: it lives in the docblock and in LOCK 3b itself.
2. The closing sentence of the MEASURED: a lone self-assigning hook leaves the CALLER value on the key block — the :352 line. "#14259's fork clause sends that one to the decision inbox; nothing here resolves it." becomes a statement that the fork was ruled, plus the pointer.

Where the pointer aims, and why that target is stable

isCallerSuppliedValue's docblock in packages/objectql/src/validation/rule-validator.ts, plus the two face pins named by test name:

• static face — MEASURED: a lone self-assigning hook leaves the CALLER value on the key, in this suite (insert side) and engine-readonly-strip-caller-values.test.ts (update side);
• lock face — LOCK 3b in engine-readonly-when-derived-writes.test.ts.

All three are symbol and test names, never line numbers — a line number is the thing that rots and produces the next card exactly like this one. It is also the idiom #14690 already established: both landed pins close with "isCallerSuppliedValue's docblock carries the argument", so this file now reads the same way as its two siblings instead of contradicting them.

Deliberately left alone: the conditional at lines 359-362 ("A ruling that self-assignment must NOT count would move this pin and #14088's seam together; that is a deliberate follow-up, not silent drift"). It is a hypothetical future reversal, framed exactly as #14690's landed pins frame it ("A future ruling that reverses this INVERTS both pins together; it never deletes either") — it does not assert the question is open.

Verification (all at ad84d2315, the head of this branch)

Behaviour cannot move on a comment-only diff, and it is cheap to show that either side:

• before (base 7a17f3bf1, after building the dependency closure pnpm --filter '@objectstack/objectql^...' build): engine-hook-provenance-sibling-seams.test.ts — Test Files 1 passed (1) · Tests 13 passed (13).
• after (ad84d2315), this file plus both face pins the new prose points at: Test Files 3 passed (3) · Tests 60 passed (60).

Both runs went through scripts/pm/os-verify-lock.sh (VERDICT command-exit 0).

Gate family re-derived on the final tree with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts at ad84d2315 — 28 commands. 24 green, plus check:nul-bytes green. Three exited 3, which each gate defines as its own PREREQUISITE-NOT-MET branch — recorded as NOT MEASURED, in the gates' own words, and not as a pass:

• check-test-completeness: "PREREQUISITE NOT MET — this gate grades a saved turbo run test log, and no log was named. … running the family locally, record this gate as NOT MEASURED."
• check:type-check-debt: "PREREQUISITE NOT MET … --re-measure cannot run: 41 workspace dependenc(ies) of the ledgered packages have no built type entry point on disk". Its self-test and the coverage half passed (check:type-check-coverage exit 0).
• check:dual-build-cjs-loads: "PREREQUISITE NOT MET — this gate reads built output, and some package has no dist/." Its 93-case self-test passed.

All three need a whole-repo build, which is CI's run, not this PR's.

Changeset

skip-changeset: the diff is one test file, comment-only. Nothing is published from any package and no behaviour moves. The label is applied on this PR.

---

🤖 Generated with Claude Code

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 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.

Coarse fallback — 0 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 7a17f3bf1e48e1e88f8e833a794e37bd40230f17 → packageMentionDocs.

[os-musk]

Landing provenance — domain:engine execution seat

Enqueued at ad84d2315.

1. The ruling's ⛔ verified by content, not by the PR's word. Triage ruled "Comment-only. Every assertion in the file stays untouched." The diff is one file, +13/−12, and every changed line is a // comment — no assertion, test name or fixture moved. The dev's own mechanical check (git diff -U0 with comment lines filtered → empty) agrees with reading the patch.

2. Clause ② — no. No new exported symbol and no new key on an already-published payload, so the mechanical floor (#14696) is not hit, and no conformance-class judgement arises: a comment inside a test file reaches no consumer. In-seat review therefore permitted; no needs:contract-review. skip-changeset is the landed precedent for a comment-and-test-only diff.

3. Governed-surface predicate, re-run on the FINAL file list — ⛔ not recalled:

node scripts/pm/check-governed-merges.mjs --test \
packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts
→ 0 of 1 path(s) hit the register (5 surfaces) — NOT governed; ordinary queue landing applies.

4. Every check run green or skipped — 40 check runs read at perPage: 50, each by its own completed + conclusion, ⛔ never by an aggregate. Test Core (1/6) again the long shard (23:56:29Z → 00:16:34Z, ~20 min) and Lint & Repo Gates ~16½ min; both green.

5. Flipped draft: false, read back draft: false, then armed auto-merge SQUASH.⚠️ The API echo reads method: MERGE regardless of what is requested — a known platform artifact; the merge-queue build ref is the authoritative reading.

⚠️The flip and the arm were delayed ~25 minutes by a GitHub rate limit, and the shape is worth recording: the GraphQL pool was exhausted while REST was not. pull_request_read (REST) answered normally throughout, so CI could be read and the PR judged; update_pull_request and search_issues (GraphQL) refused. ⛔ The seat stopped retrying rather than burning quota, and the git read channel — fetch, ls-remote, grep — was unaffected the whole time. Prior sessions recorded this class of outage as "account-wide"; it is not, and the distinction decides what work can continue during one.

⭐ One correction the seat owes this card

The dispatch told the dev that isCallerSuppliedValue was not in rule-validator.ts or engine.ts — "I grepped and got nothing, so it is somewhere else." That was wrong: it is in packages/objectql/src/**validation**/rule-validator.ts, 9 hits, definition at :623, corrected docblock at :578-621. The seat's grep used a path missing the validation/ segment and ran no control, so a path typo and a real absence were indistinguishable — the exact failure the standing zero-hit rule exists to prevent, violated by the seat that wrote the rule down.

⭐ It cost nothing because the dispatch handed the claim over as a Zone 2 item to measure rather than as fact, and told the dev its pointer would be worthless if it named the wrong file. The dev found the real location and said so. That is the third time this shift a labelled-as-assumption has caught a seat error before it reached a PR.

---

Generated by Claude Code

[os-musk]

Fixes#14693

Three passages in packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts still said the readonlyWhen sibling seam was "WITHHELD pending a maintainer ruling" and headed "to the decision inbox, never resolved here". It was ruled — #14259, maintainer ruling B: that seam keeps value equality, a self-assigning hook does not unlock a readonlyWhen state lock, and the asymmetry with the static face is deliberate. #14690 then landed the corrected isCallerSuppliedValue docblock plus a measurement pin on each face, and a cross-reference into this file — so a PR whose purpose is to document the ruling now routes readers straight into the sentence that contradicts it.

Comment-only. Every assertion, test name and fixture is untouched: git diff -U0 on the changed file, with the comment lines filtered out, returns nothing. The stale prose is replaced with a pointer to where the argument now lives rather than a fourth copy of it.

What changed

Two comment blocks, carrying the three stale lines triage measured at :23, :30 and :352 (all three re-measured unmoved on this branch's base 7a17f3bf1):

1. The file header's "THE SIBLING SEAM IS DELIBERATELY NOT HERE" block — lines 21-30, holding the :23 and :30 lines. It now records that the seam was ruled and names where the argument lives. The measurement narrative it used to carry (threading the record turns LOCK 3b red, closed_note committing the forgery) is deliberately not repeated: it lives in the docblock and in LOCK 3b itself.
2. The closing sentence of the MEASURED: a lone self-assigning hook leaves the CALLER value on the key block — the :352 line. "#14259's fork clause sends that one to the decision inbox; nothing here resolves it." becomes a statement that the fork was ruled, plus the pointer.

Where the pointer aims, and why that target is stable

isCallerSuppliedValue's docblock in packages/objectql/src/validation/rule-validator.ts, plus the two face pins named by test name:

• static face — MEASURED: a lone self-assigning hook leaves the CALLER value on the key, in this suite (insert side) and engine-readonly-strip-caller-values.test.ts (update side);
• lock face — LOCK 3b in engine-readonly-when-derived-writes.test.ts.

All three are symbol and test names, never line numbers — a line number is the thing that rots and produces the next card exactly like this one. It is also the idiom #14690 already established: both landed pins close with "isCallerSuppliedValue's docblock carries the argument", so this file now reads the same way as its two siblings instead of contradicting them.

Deliberately left alone: the conditional at lines 359-362 ("A ruling that self-assignment must NOT count would move this pin and #14088's seam together; that is a deliberate follow-up, not silent drift"). It is a hypothetical future reversal, framed exactly as #14690's landed pins frame it ("A future ruling that reverses this INVERTS both pins together; it never deletes either") — it does not assert the question is open.

Verification (all at ad84d2315, the head of this branch)

Behaviour cannot move on a comment-only diff, and it is cheap to show that either side:

• before (base 7a17f3bf1, after building the dependency closure pnpm --filter '@objectstack/objectql^...' build): engine-hook-provenance-sibling-seams.test.ts — Test Files 1 passed (1) · Tests 13 passed (13).
• after (ad84d2315), this file plus both face pins the new prose points at: Test Files 3 passed (3) · Tests 60 passed (60).

Both runs went through scripts/pm/os-verify-lock.sh (VERDICT command-exit 0).

Gate family re-derived on the final tree with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts at ad84d2315 — 28 commands. 24 green, plus check:nul-bytes green. Three exited 3, which each gate defines as its own PREREQUISITE-NOT-MET branch — recorded as NOT MEASURED, in the gates' own words, and not as a pass:

• check-test-completeness: "PREREQUISITE NOT MET — this gate grades a saved turbo run test log, and no log was named. … running the family locally, record this gate as NOT MEASURED."
• check:type-check-debt: "PREREQUISITE NOT MET … --re-measure cannot run: 41 workspace dependenc(ies) of the ledgered packages have no built type entry point on disk". Its self-test and the coverage half passed (check:type-check-coverage exit 0).
• check:dual-build-cjs-loads: "PREREQUISITE NOT MET — this gate reads built output, and some package has no dist/." Its 93-case self-test passed.

All three need a whole-repo build, which is CI's run, not this PR's.

Changeset

skip-changeset: the diff is one test file, comment-only. Nothing is published from any package and no behaviour moves. The label is applied on this PR.

---

🤖 Generated with Claude Code

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 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.

Coarse fallback — 0 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 7a17f3bf1e48e1e88f8e833a794e37bd40230f17 → packageMentionDocs.

[os-musk]

Landing provenance — domain:engine execution seat

Enqueued at ad84d2315.

1. The ruling's ⛔ verified by content, not by the PR's word. Triage ruled "Comment-only. Every assertion in the file stays untouched." The diff is one file, +13/−12, and every changed line is a // comment — no assertion, test name or fixture moved. The dev's own mechanical check (git diff -U0 with comment lines filtered → empty) agrees with reading the patch.

2. Clause ② — no. No new exported symbol and no new key on an already-published payload, so the mechanical floor (#14696) is not hit, and no conformance-class judgement arises: a comment inside a test file reaches no consumer. In-seat review therefore permitted; no needs:contract-review. skip-changeset is the landed precedent for a comment-and-test-only diff.

3. Governed-surface predicate, re-run on the FINAL file list — ⛔ not recalled:

node scripts/pm/check-governed-merges.mjs --test \
packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts
→ 0 of 1 path(s) hit the register (5 surfaces) — NOT governed; ordinary queue landing applies.

4. Every check run green or skipped — 40 check runs read at perPage: 50, each by its own completed + conclusion, ⛔ never by an aggregate. Test Core (1/6) again the long shard (23:56:29Z → 00:16:34Z, ~20 min) and Lint & Repo Gates ~16½ min; both green.

5. Flipped draft: false, read back draft: false, then armed auto-merge SQUASH.⚠️ The API echo reads method: MERGE regardless of what is requested — a known platform artifact; the merge-queue build ref is the authoritative reading.

⚠️The flip and the arm were delayed ~25 minutes by a GitHub rate limit, and the shape is worth recording: the GraphQL pool was exhausted while REST was not. pull_request_read (REST) answered normally throughout, so CI could be read and the PR judged; update_pull_request and search_issues (GraphQL) refused. ⛔ The seat stopped retrying rather than burning quota, and the git read channel — fetch, ls-remote, grep — was unaffected the whole time. Prior sessions recorded this class of outage as "account-wide"; it is not, and the distinction decides what work can continue during one.

⭐ One correction the seat owes this card

The dispatch told the dev that isCallerSuppliedValue was not in rule-validator.ts or engine.ts — "I grepped and got nothing, so it is somewhere else." That was wrong: it is in packages/objectql/src/**validation**/rule-validator.ts, 9 hits, definition at :623, corrected docblock at :578-621. The seat's grep used a path missing the validation/ segment and ran no control, so a path typo and a real absence were indistinguishable — the exact failure the standing zero-hit rule exists to prevent, violated by the seat that wrote the rule down.

⭐ It cost nothing because the dispatch handed the claim over as a Zone 2 item to measure rather than as fact, and told the dev its pointer would be worthless if it named the wrong file. The dev found the real location and said so. That is the third time this shift a labelled-as-assumption has caught a seat error before it reached a PR.

---

Generated by Claude Code

[os-musk]

Fixes#14693

Three passages in packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts still said the readonlyWhen sibling seam was "WITHHELD pending a maintainer ruling" and headed "to the decision inbox, never resolved here". It was ruled — #14259, maintainer ruling B: that seam keeps value equality, a self-assigning hook does not unlock a readonlyWhen state lock, and the asymmetry with the static face is deliberate. #14690 then landed the corrected isCallerSuppliedValue docblock plus a measurement pin on each face, and a cross-reference into this file — so a PR whose purpose is to document the ruling now routes readers straight into the sentence that contradicts it.

Comment-only. Every assertion, test name and fixture is untouched: git diff -U0 on the changed file, with the comment lines filtered out, returns nothing. The stale prose is replaced with a pointer to where the argument now lives rather than a fourth copy of it.

What changed

Two comment blocks, carrying the three stale lines triage measured at :23, :30 and :352 (all three re-measured unmoved on this branch's base 7a17f3bf1):

1. The file header's "THE SIBLING SEAM IS DELIBERATELY NOT HERE" block — lines 21-30, holding the :23 and :30 lines. It now records that the seam was ruled and names where the argument lives. The measurement narrative it used to carry (threading the record turns LOCK 3b red, closed_note committing the forgery) is deliberately not repeated: it lives in the docblock and in LOCK 3b itself.
2. The closing sentence of the MEASURED: a lone self-assigning hook leaves the CALLER value on the key block — the :352 line. "#14259's fork clause sends that one to the decision inbox; nothing here resolves it." becomes a statement that the fork was ruled, plus the pointer.

Where the pointer aims, and why that target is stable

isCallerSuppliedValue's docblock in packages/objectql/src/validation/rule-validator.ts, plus the two face pins named by test name:

• static face — MEASURED: a lone self-assigning hook leaves the CALLER value on the key, in this suite (insert side) and engine-readonly-strip-caller-values.test.ts (update side);
• lock face — LOCK 3b in engine-readonly-when-derived-writes.test.ts.

All three are symbol and test names, never line numbers — a line number is the thing that rots and produces the next card exactly like this one. It is also the idiom #14690 already established: both landed pins close with "isCallerSuppliedValue's docblock carries the argument", so this file now reads the same way as its two siblings instead of contradicting them.

Deliberately left alone: the conditional at lines 359-362 ("A ruling that self-assignment must NOT count would move this pin and #14088's seam together; that is a deliberate follow-up, not silent drift"). It is a hypothetical future reversal, framed exactly as #14690's landed pins frame it ("A future ruling that reverses this INVERTS both pins together; it never deletes either") — it does not assert the question is open.

Verification (all at ad84d2315, the head of this branch)

Behaviour cannot move on a comment-only diff, and it is cheap to show that either side:

• before (base 7a17f3bf1, after building the dependency closure pnpm --filter '@objectstack/objectql^...' build): engine-hook-provenance-sibling-seams.test.ts — Test Files 1 passed (1) · Tests 13 passed (13).
• after (ad84d2315), this file plus both face pins the new prose points at: Test Files 3 passed (3) · Tests 60 passed (60).

Both runs went through scripts/pm/os-verify-lock.sh (VERDICT command-exit 0).

Gate family re-derived on the final tree with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts at ad84d2315 — 28 commands. 24 green, plus check:nul-bytes green. Three exited 3, which each gate defines as its own PREREQUISITE-NOT-MET branch — recorded as NOT MEASURED, in the gates' own words, and not as a pass:

• check-test-completeness: "PREREQUISITE NOT MET — this gate grades a saved turbo run test log, and no log was named. … running the family locally, record this gate as NOT MEASURED."
• check:type-check-debt: "PREREQUISITE NOT MET … --re-measure cannot run: 41 workspace dependenc(ies) of the ledgered packages have no built type entry point on disk". Its self-test and the coverage half passed (check:type-check-coverage exit 0).
• check:dual-build-cjs-loads: "PREREQUISITE NOT MET — this gate reads built output, and some package has no dist/." Its 93-case self-test passed.

All three need a whole-repo build, which is CI's run, not this PR's.

Changeset

skip-changeset: the diff is one test file, comment-only. Nothing is published from any package and no behaviour moves. The label is applied on this PR.

---

🤖 Generated with Claude Code

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 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.

Coarse fallback — 0 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 7a17f3bf1e48e1e88f8e833a794e37bd40230f17 → packageMentionDocs.

[os-musk]

Landing provenance — domain:engine execution seat

Enqueued at ad84d2315.

1. The ruling's ⛔ verified by content, not by the PR's word. Triage ruled "Comment-only. Every assertion in the file stays untouched." The diff is one file, +13/−12, and every changed line is a // comment — no assertion, test name or fixture moved. The dev's own mechanical check (git diff -U0 with comment lines filtered → empty) agrees with reading the patch.

2. Clause ② — no. No new exported symbol and no new key on an already-published payload, so the mechanical floor (#14696) is not hit, and no conformance-class judgement arises: a comment inside a test file reaches no consumer. In-seat review therefore permitted; no needs:contract-review. skip-changeset is the landed precedent for a comment-and-test-only diff.

3. Governed-surface predicate, re-run on the FINAL file list — ⛔ not recalled:

node scripts/pm/check-governed-merges.mjs --test \
packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts
→ 0 of 1 path(s) hit the register (5 surfaces) — NOT governed; ordinary queue landing applies.

4. Every check run green or skipped — 40 check runs read at perPage: 50, each by its own completed + conclusion, ⛔ never by an aggregate. Test Core (1/6) again the long shard (23:56:29Z → 00:16:34Z, ~20 min) and Lint & Repo Gates ~16½ min; both green.

5. Flipped draft: false, read back draft: false, then armed auto-merge SQUASH.⚠️ The API echo reads method: MERGE regardless of what is requested — a known platform artifact; the merge-queue build ref is the authoritative reading.

⚠️The flip and the arm were delayed ~25 minutes by a GitHub rate limit, and the shape is worth recording: the GraphQL pool was exhausted while REST was not. pull_request_read (REST) answered normally throughout, so CI could be read and the PR judged; update_pull_request and search_issues (GraphQL) refused. ⛔ The seat stopped retrying rather than burning quota, and the git read channel — fetch, ls-remote, grep — was unaffected the whole time. Prior sessions recorded this class of outage as "account-wide"; it is not, and the distinction decides what work can continue during one.

⭐ One correction the seat owes this card

The dispatch told the dev that isCallerSuppliedValue was not in rule-validator.ts or engine.ts — "I grepped and got nothing, so it is somewhere else." That was wrong: it is in packages/objectql/src/**validation**/rule-validator.ts, 9 hits, definition at :623, corrected docblock at :578-621. The seat's grep used a path missing the validation/ segment and ran no control, so a path typo and a real absence were indistinguishable — the exact failure the standing zero-hit rule exists to prevent, violated by the seat that wrote the rule down.

⭐ It cost nothing because the dispatch handed the claim over as a Zone 2 item to measure rather than as fact, and told the dev its pointer would be worthless if it named the wrong file. The dev found the real location and said so. That is the third time this shift a labelled-as-assumption has caught a seat error before it reached a PR.

---

Generated by Claude Code

[os-musk]

Fixes#14693

Three passages in packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts still said the readonlyWhen sibling seam was "WITHHELD pending a maintainer ruling" and headed "to the decision inbox, never resolved here". It was ruled — #14259, maintainer ruling B: that seam keeps value equality, a self-assigning hook does not unlock a readonlyWhen state lock, and the asymmetry with the static face is deliberate. #14690 then landed the corrected isCallerSuppliedValue docblock plus a measurement pin on each face, and a cross-reference into this file — so a PR whose purpose is to document the ruling now routes readers straight into the sentence that contradicts it.

Comment-only. Every assertion, test name and fixture is untouched: git diff -U0 on the changed file, with the comment lines filtered out, returns nothing. The stale prose is replaced with a pointer to where the argument now lives rather than a fourth copy of it.

What changed

Two comment blocks, carrying the three stale lines triage measured at :23, :30 and :352 (all three re-measured unmoved on this branch's base 7a17f3bf1):

1. The file header's "THE SIBLING SEAM IS DELIBERATELY NOT HERE" block — lines 21-30, holding the :23 and :30 lines. It now records that the seam was ruled and names where the argument lives. The measurement narrative it used to carry (threading the record turns LOCK 3b red, closed_note committing the forgery) is deliberately not repeated: it lives in the docblock and in LOCK 3b itself.
2. The closing sentence of the MEASURED: a lone self-assigning hook leaves the CALLER value on the key block — the :352 line. "#14259's fork clause sends that one to the decision inbox; nothing here resolves it." becomes a statement that the fork was ruled, plus the pointer.

Where the pointer aims, and why that target is stable

isCallerSuppliedValue's docblock in packages/objectql/src/validation/rule-validator.ts, plus the two face pins named by test name:

• static face — MEASURED: a lone self-assigning hook leaves the CALLER value on the key, in this suite (insert side) and engine-readonly-strip-caller-values.test.ts (update side);
• lock face — LOCK 3b in engine-readonly-when-derived-writes.test.ts.

All three are symbol and test names, never line numbers — a line number is the thing that rots and produces the next card exactly like this one. It is also the idiom #14690 already established: both landed pins close with "isCallerSuppliedValue's docblock carries the argument", so this file now reads the same way as its two siblings instead of contradicting them.

Deliberately left alone: the conditional at lines 359-362 ("A ruling that self-assignment must NOT count would move this pin and #14088's seam together; that is a deliberate follow-up, not silent drift"). It is a hypothetical future reversal, framed exactly as #14690's landed pins frame it ("A future ruling that reverses this INVERTS both pins together; it never deletes either") — it does not assert the question is open.

Verification (all at ad84d2315, the head of this branch)

Behaviour cannot move on a comment-only diff, and it is cheap to show that either side:

• before (base 7a17f3bf1, after building the dependency closure pnpm --filter '@objectstack/objectql^...' build): engine-hook-provenance-sibling-seams.test.ts — Test Files 1 passed (1) · Tests 13 passed (13).
• after (ad84d2315), this file plus both face pins the new prose points at: Test Files 3 passed (3) · Tests 60 passed (60).

Both runs went through scripts/pm/os-verify-lock.sh (VERDICT command-exit 0).

Gate family re-derived on the final tree with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts at ad84d2315 — 28 commands. 24 green, plus check:nul-bytes green. Three exited 3, which each gate defines as its own PREREQUISITE-NOT-MET branch — recorded as NOT MEASURED, in the gates' own words, and not as a pass:

• check-test-completeness: "PREREQUISITE NOT MET — this gate grades a saved turbo run test log, and no log was named. … running the family locally, record this gate as NOT MEASURED."
• check:type-check-debt: "PREREQUISITE NOT MET … --re-measure cannot run: 41 workspace dependenc(ies) of the ledgered packages have no built type entry point on disk". Its self-test and the coverage half passed (check:type-check-coverage exit 0).
• check:dual-build-cjs-loads: "PREREQUISITE NOT MET — this gate reads built output, and some package has no dist/." Its 93-case self-test passed.

All three need a whole-repo build, which is CI's run, not this PR's.

Changeset

skip-changeset: the diff is one test file, comment-only. Nothing is published from any package and no behaviour moves. The label is applied on this PR.

---

🤖 Generated with Claude Code

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 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.

Coarse fallback — 0 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 7a17f3bf1e48e1e88f8e833a794e37bd40230f17 → packageMentionDocs.

[os-musk]

Landing provenance — domain:engine execution seat

Enqueued at ad84d2315.

1. The ruling's ⛔ verified by content, not by the PR's word. Triage ruled "Comment-only. Every assertion in the file stays untouched." The diff is one file, +13/−12, and every changed line is a // comment — no assertion, test name or fixture moved. The dev's own mechanical check (git diff -U0 with comment lines filtered → empty) agrees with reading the patch.

2. Clause ② — no. No new exported symbol and no new key on an already-published payload, so the mechanical floor (#14696) is not hit, and no conformance-class judgement arises: a comment inside a test file reaches no consumer. In-seat review therefore permitted; no needs:contract-review. skip-changeset is the landed precedent for a comment-and-test-only diff.

3. Governed-surface predicate, re-run on the FINAL file list — ⛔ not recalled:

node scripts/pm/check-governed-merges.mjs --test \
packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts
→ 0 of 1 path(s) hit the register (5 surfaces) — NOT governed; ordinary queue landing applies.

4. Every check run green or skipped — 40 check runs read at perPage: 50, each by its own completed + conclusion, ⛔ never by an aggregate. Test Core (1/6) again the long shard (23:56:29Z → 00:16:34Z, ~20 min) and Lint & Repo Gates ~16½ min; both green.

5. Flipped draft: false, read back draft: false, then armed auto-merge SQUASH.⚠️ The API echo reads method: MERGE regardless of what is requested — a known platform artifact; the merge-queue build ref is the authoritative reading.

⚠️The flip and the arm were delayed ~25 minutes by a GitHub rate limit, and the shape is worth recording: the GraphQL pool was exhausted while REST was not. pull_request_read (REST) answered normally throughout, so CI could be read and the PR judged; update_pull_request and search_issues (GraphQL) refused. ⛔ The seat stopped retrying rather than burning quota, and the git read channel — fetch, ls-remote, grep — was unaffected the whole time. Prior sessions recorded this class of outage as "account-wide"; it is not, and the distinction decides what work can continue during one.

⭐ One correction the seat owes this card

The dispatch told the dev that isCallerSuppliedValue was not in rule-validator.ts or engine.ts — "I grepped and got nothing, so it is somewhere else." That was wrong: it is in packages/objectql/src/**validation**/rule-validator.ts, 9 hits, definition at :623, corrected docblock at :578-621. The seat's grep used a path missing the validation/ segment and ran no control, so a path typo and a real absence were indistinguishable — the exact failure the standing zero-hit rule exists to prevent, violated by the seat that wrote the rule down.

⭐ It cost nothing because the dispatch handed the claim over as a Zone 2 item to measure rather than as fact, and told the dev its pointer would be worthless if it named the wrong file. The dev found the real location and said so. That is the third time this shift a labelled-as-assumption has caught a seat error before it reached a PR.

---

Generated by Claude Code

[os-musk]

Fixes#14693

Three passages in packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts still said the readonlyWhen sibling seam was "WITHHELD pending a maintainer ruling" and headed "to the decision inbox, never resolved here". It was ruled — #14259, maintainer ruling B: that seam keeps value equality, a self-assigning hook does not unlock a readonlyWhen state lock, and the asymmetry with the static face is deliberate. #14690 then landed the corrected isCallerSuppliedValue docblock plus a measurement pin on each face, and a cross-reference into this file — so a PR whose purpose is to document the ruling now routes readers straight into the sentence that contradicts it.

Comment-only. Every assertion, test name and fixture is untouched: git diff -U0 on the changed file, with the comment lines filtered out, returns nothing. The stale prose is replaced with a pointer to where the argument now lives rather than a fourth copy of it.

What changed

Two comment blocks, carrying the three stale lines triage measured at :23, :30 and :352 (all three re-measured unmoved on this branch's base 7a17f3bf1):

1. The file header's "THE SIBLING SEAM IS DELIBERATELY NOT HERE" block — lines 21-30, holding the :23 and :30 lines. It now records that the seam was ruled and names where the argument lives. The measurement narrative it used to carry (threading the record turns LOCK 3b red, closed_note committing the forgery) is deliberately not repeated: it lives in the docblock and in LOCK 3b itself.
2. The closing sentence of the MEASURED: a lone self-assigning hook leaves the CALLER value on the key block — the :352 line. "#14259's fork clause sends that one to the decision inbox; nothing here resolves it." becomes a statement that the fork was ruled, plus the pointer.

Where the pointer aims, and why that target is stable

isCallerSuppliedValue's docblock in packages/objectql/src/validation/rule-validator.ts, plus the two face pins named by test name:

• static face — MEASURED: a lone self-assigning hook leaves the CALLER value on the key, in this suite (insert side) and engine-readonly-strip-caller-values.test.ts (update side);
• lock face — LOCK 3b in engine-readonly-when-derived-writes.test.ts.

All three are symbol and test names, never line numbers — a line number is the thing that rots and produces the next card exactly like this one. It is also the idiom #14690 already established: both landed pins close with "isCallerSuppliedValue's docblock carries the argument", so this file now reads the same way as its two siblings instead of contradicting them.

Deliberately left alone: the conditional at lines 359-362 ("A ruling that self-assignment must NOT count would move this pin and #14088's seam together; that is a deliberate follow-up, not silent drift"). It is a hypothetical future reversal, framed exactly as #14690's landed pins frame it ("A future ruling that reverses this INVERTS both pins together; it never deletes either") — it does not assert the question is open.

Verification (all at ad84d2315, the head of this branch)

Behaviour cannot move on a comment-only diff, and it is cheap to show that either side:

• before (base 7a17f3bf1, after building the dependency closure pnpm --filter '@objectstack/objectql^...' build): engine-hook-provenance-sibling-seams.test.ts — Test Files 1 passed (1) · Tests 13 passed (13).
• after (ad84d2315), this file plus both face pins the new prose points at: Test Files 3 passed (3) · Tests 60 passed (60).

Both runs went through scripts/pm/os-verify-lock.sh (VERDICT command-exit 0).

Gate family re-derived on the final tree with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts at ad84d2315 — 28 commands. 24 green, plus check:nul-bytes green. Three exited 3, which each gate defines as its own PREREQUISITE-NOT-MET branch — recorded as NOT MEASURED, in the gates' own words, and not as a pass:

• check-test-completeness: "PREREQUISITE NOT MET — this gate grades a saved turbo run test log, and no log was named. … running the family locally, record this gate as NOT MEASURED."
• check:type-check-debt: "PREREQUISITE NOT MET … --re-measure cannot run: 41 workspace dependenc(ies) of the ledgered packages have no built type entry point on disk". Its self-test and the coverage half passed (check:type-check-coverage exit 0).
• check:dual-build-cjs-loads: "PREREQUISITE NOT MET — this gate reads built output, and some package has no dist/." Its 93-case self-test passed.

All three need a whole-repo build, which is CI's run, not this PR's.

Changeset

skip-changeset: the diff is one test file, comment-only. Nothing is published from any package and no behaviour moves. The label is applied on this PR.

---

🤖 Generated with Claude Code

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 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.

Coarse fallback — 0 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 7a17f3bf1e48e1e88f8e833a794e37bd40230f17 → packageMentionDocs.

[os-musk]

Landing provenance — domain:engine execution seat

Enqueued at ad84d2315.

1. The ruling's ⛔ verified by content, not by the PR's word. Triage ruled "Comment-only. Every assertion in the file stays untouched." The diff is one file, +13/−12, and every changed line is a // comment — no assertion, test name or fixture moved. The dev's own mechanical check (git diff -U0 with comment lines filtered → empty) agrees with reading the patch.

2. Clause ② — no. No new exported symbol and no new key on an already-published payload, so the mechanical floor (#14696) is not hit, and no conformance-class judgement arises: a comment inside a test file reaches no consumer. In-seat review therefore permitted; no needs:contract-review. skip-changeset is the landed precedent for a comment-and-test-only diff.

3. Governed-surface predicate, re-run on the FINAL file list — ⛔ not recalled:

node scripts/pm/check-governed-merges.mjs --test \
packages/objectql/src/engine-hook-provenance-sibling-seams.test.ts
→ 0 of 1 path(s) hit the register (5 surfaces) — NOT governed; ordinary queue landing applies.

4. Every check run green or skipped — 40 check runs read at perPage: 50, each by its own completed + conclusion, ⛔ never by an aggregate. Test Core (1/6) again the long shard (23:56:29Z → 00:16:34Z, ~20 min) and Lint & Repo Gates ~16½ min; both green.

5. Flipped draft: false, read back draft: false, then armed auto-merge SQUASH.⚠️ The API echo reads method: MERGE regardless of what is requested — a known platform artifact; the merge-queue build ref is the authoritative reading.

⚠️The flip and the arm were delayed ~25 minutes by a GitHub rate limit, and the shape is worth recording: the GraphQL pool was exhausted while REST was not. pull_request_read (REST) answered normally throughout, so CI could be read and the PR judged; update_pull_request and search_issues (GraphQL) refused. ⛔ The seat stopped retrying rather than burning quota, and the git read channel — fetch, ls-remote, grep — was unaffected the whole time. Prior sessions recorded this class of outage as "account-wide"; it is not, and the distinction decides what work can continue during one.

⭐ One correction the seat owes this card

The dispatch told the dev that isCallerSuppliedValue was not in rule-validator.ts or engine.ts — "I grepped and got nothing, so it is somewhere else." That was wrong: it is in packages/objectql/src/**validation**/rule-validator.ts, 9 hits, definition at :623, corrected docblock at :578-621. The seat's grep used a path missing the validation/ segment and ran no control, so a path typo and a real absence were indistinguishable — the exact failure the standing zero-hit rule exists to prevent, violated by the seat that wrote the rule down.

⭐ It cost nothing because the dispatch handed the claim over as a Zone 2 item to measure rather than as fact, and told the dev its pointer would be worthless if it named the wrong file. The dev found the real location and said so. That is the third time this shift a labelled-as-assumption has caught a seat error before it reached a PR.

---

Generated by Claude Code