You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(permissions): re-certify the tenant-audit census at 218 write call sites (#14333)
`ObjectStoreSuspendedRunStore.claimSuspension` adds exactly one write call
site on the application surface — the conditional `delete` that decides the
cross-replica advance — so the shrink-only census the gate holds the tree to
moves 217 -> 218. Regenerated with `node scripts/tenant-audit-census.mjs
--write`, and the nine hand-written prose figures the generator does not own
updated by hand to match.
Measured pre-existing state, so the delta is attributable: with these three
sources reverted to the merge base and the census restored to HEAD, the gate
is green at 217 — this PR moves it by exactly one.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AUF1NoViznQK32gqpK8wS8
Copy file name to clipboardExpand all lines: content/docs/permissions/tenant-audit-census.mdx
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ are reported as `undecidable` rather than assumed either way.
98
98
99
99
The same holds twice over for the context. An options argument spelled as a
100
100
literal can be read; one spelled `options`, `{ ...opts }`, or handed through a
101
-
forwarding shim cannot, and **67 of the 217 sites are spelled that way**. A
101
+
forwarding shim cannot, and **67 of the 218 sites are spelled that way**. A
102
102
context resolved from an inline literal or a local `const` can be tested for
103
103
`isSystem`; one arriving from a helper call cannot.
104
104
@@ -147,10 +147,10 @@ reproduce them. Where it disagrees, it disagrees on the page:
147
147
148
148
| carried figure | where it survives | this census |
149
149
| :--- | :--- | ---: |
150
-
| 175 write call sites | quoted in the merged changeset |**217**|
150
+
| 175 write call sites | quoted in the merged changeset |**218**|
151
151
| 24 carrying no tenant context | quoted in the merged changeset |**9** provable and tenancy-enabled; **32** more whose options argument is unreadable |
152
-
| 127 of 175 statically decidable, 48 runtime-parameter-name sites | restated on the `isSystem`-scoping card |**145 of 217** decidable, **72** undecidable |
153
-
| 135 (77%) silenced by the `isSystem` guard before the posture gate | the lost issue body — **no surviving corroboration**|**not reproduced**: 99 decidably elevated, 0 decidably not, 101 undecidable |
152
+
| 127 of 175 statically decidable, 48 runtime-parameter-name sites | restated on the `isSystem`-scoping card |**146 of 218** decidable, **72** undecidable |
153
+
| 135 (77%) silenced by the `isSystem` guard before the posture gate | the lost issue body — **no surviving corroboration**|**not reproduced**: 100 decidably elevated, 0 decidably not, 101 undecidable |
154
154
| 141 and 132, two independent re-derivations | the card that filed this work | — |
155
155
156
156
**The differences are not reconciled, and deliberately so.** The old census's
@@ -161,17 +161,17 @@ at any commit.
161
161
162
162
Two structural facts do plausibly widen this reading against any hand or regex
163
163
one, and both are counted in the generated tables below: the 45 sites reached
164
-
through an erased (`any`) receiver, and the 37 that name their object through a
164
+
through an erased (`any`) receiver, and the 38 that name their object through a
165
165
`const` rather than inline. An instrument that read either the way a person does
166
166
would report a smaller number and would not say so.
167
167
168
168
The fourth row is the one worth flagging to anyone citing it. **The 135 / 77%
169
169
figure has no surviving corroboration anywhere in the tree.** This census reads
170
-
99 of 217 (45%) as decidably elevated, with 101 more whose elevation is a
170
+
100 of 218 (46%) as decidably elevated, with 101 more whose elevation is a
171
171
run-time fact — so the claim is neither confirmed nor refuted, and the honest
172
172
answer is that a static reading cannot settle it.
173
173
174
-
⇒ **Cite `9 / 217`, and say what it is**: the sites whose options argument was
174
+
⇒ **Cite `9 / 218`, and say what it is**: the sites whose options argument was
175
175
READ and holds no tenant context, against a decidably tenancy-enabled object.
176
176
That is the control's provable yield surface. ⛔ Do not cite it as "the sites
177
177
without tenant context" — **32 further sites** have an options argument this
@@ -183,29 +183,29 @@ cannot read, and they are neither in nor out.
183
183
184
184
| what | count |
185
185
| :--- | ---: |
186
-
| write call sites on the application surface |**217**|
187
-
| …whose object name is statically decidable |145|
186
+
| write call sites on the application surface |**218**|
187
+
| …whose object name is statically decidable |146|
188
188
| …whose object name is chosen at run time | 72 |
189
-
| …against an object with tenancy ENABLED |145|
189
+
| …against an object with tenancy ENABLED |146|
190
190
| …against an object that declares tenancy off | 0 |
191
-
| threading a tenant context |133|
191
+
| threading a tenant context |134|
192
192
| PROVABLY carrying none (options read, no context key) |**17**|
193
193
| …of those, against a decidably tenancy-enabled object |**9**|
194
194
| options argument UNREADABLE — may or may not carry one | 67 |
195
195
| …of those, against a decidably tenancy-enabled object | 32 |
196
-
| threading a decidably ELEVATED (`isSystem`) context |99|
196
+
| threading a decidably ELEVATED (`isSystem`) context |100|
197
197
| threading a context that is decidably NOT elevated | 0 |
198
198
| threading a context whose elevation is a run-time fact | 101 |
199
199
200
200
| how the instrument reached the site | count |
201
201
| :--- | ---: |
202
-
| receiver carried a readable engine type |172|
202
+
| receiver carried a readable engine type |173|
203
203
| receiver erased, placed by the object NAME | 19 |
204
204
| receiver erased, placed by an `object: string` PARAMETER | 15 |
205
205
| receiver erased, placed by an `UNTYPED_RECEIVERS` row | 11 |
206
206
207
207
| object name spelled inline | 108 |
208
-
| object name spelled through a `const`|37|
208
+
| object name spelled through a `const`|38|
209
209
| object name is an `object: string` parameter | 19 |
210
210
| object name is some other run-time expression | 53 |
211
211
@@ -224,13 +224,13 @@ holds still. They are required to be HERE and to say WHEN they were true;
224
224
their values are not compared. The reasoning, and the measurement behind it,
0 commit comments