feat: rule Q63 in three limbs; take the human headcount off /legal/privacy/; close R10; ratify /med-arb/

Pouya's rulings, 2026-09-02.

Q63(a) — wording approved with two trims: the editorial closing sentence is
struck, and the mailbox clause is rewritten per (b).

Q63(b) — info@smlcompany.ca is a delegated mailbox read by Pouya and by
administrative staff. The page said "anyone who can reach that mailbox"; it now
says who. The answer reached four sentences, not the one the ruling named, in
three sections: "my mailbox" had been written as a personal one throughout.

Q63(c) — the account root credential is held by Pouya, has no programmatic key
and carries MFA. The page now states the first two.

And the answer to (c) took the human headcount off the page. His attestation:
"two people is an exaggeration... a handful is accurate — the simulation counts
identities, not humans, and the two are not the same claim." The enumeration was
exhaustive and the inference off it was not: two IAM identities is a LOWER BOUND
on people and was published as an exact count. The page now attributes read
access to "the account's administrators — me, and the small number of people who
administer it with me", and the false inference is corrected at its source in
docs/reference/intake-table-access-verification.md as well as on the page.

R10 — CLOSED on a fresh one-line confirmation, not on the 2026-08-28 stamp.
ADRIC, ADRIO, the three OBA sections and the CTF all current. Re-stamped on all
four stamp-bearing sites; the row stays live, because its trigger is an event.

/med-arb/ — ratified as shipped, no credential line restored. His note for the
record: med-arb is a service he provides, not a designation.

The tripwire is unchanged and proven both ways: exit 0 on the revised page,
exit 1 with 5 matches on the pre-correction bytes rebuilt from bd282aa.

A sentence added to back the correction had no command behind it. "The table
carries no policy of its own granting access to anyone" was published with
nothing in the repo establishing it — a DynamoDB resource policy is invisible to
describe-table, and every simulation on file asks what a principal may do.
Measured rather than deleted: get-resource-policy returns PolicyNotFoundException,
and describe-organization returns AWSOrganizationsNotInUseException, which is
what makes the Identity Center zero conclusive rather than merely local. Both
recorded as commands 7 and 8; R21 gains claim (v) and two falsifiers.

Q64 OPENED, with a TODO(pouya) and an unticked cutover item: "I hold it" is true
whether or not a second person holds it, and reads as sole custody one paragraph
below "the small number of people who administer it with me". The request to
strike the possessive now is declined with a reason — he dictated the clause —
and the page cannot ship while the TODO stands.

Two review rounds, 22 findings, 21 resolved, 1 declined. Nine of round 2's twelve
were defects in round 1's own repairs. Stopped at two per D19.

Gates, exit status read: check 0 · build 0 (23 pages) · check:claims 0 ·
og:proof 0 · check:intake 0 · lint 0 · router.test 0 (30/30) · lighthouse 0,
worst of 23 99/100/100/100, /legal/privacy/ 100/100/100.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Md3GndFqWPzK78xAoebsg5

scripts/check-claims.mjs

@@ -415,27 +415,37 @@ const FIXTURES = {
      the wording a correction is likely to reach for. Where a fixture is one of
      those, the comment beside it says so. */
   mustNotMatch: [
-    /* NEGATIVE FIXTURES FOR `sole-administrator-q62`. The first three are the
-       REPLACEMENT COPY ITSELF, verbatim from the corrected `/legal/privacy/` —
+    /* NEGATIVE FIXTURES FOR `sole-administrator-q62`. The first SEVEN are LIVE
+       PAGE COPY, verbatim from the corrected `/legal/privacy/` —
        which is the fixture that matters, because Q62's ruling required this
        pattern to be proven silent on the true sentence as well as loud on the
-       false one. THEY MUST BE RE-SYNCED WHENEVER THAT COPY CHANGES — round 1's
-       set went stale within the hour, when the audit rewrote three of the four
-       paragraphs they were copied from. The rest are near misses on the same
-       subject: the pattern is anchored on five strings that reached `dist/`, not
-       on the ideas in them, so a truthful sentence about administrative access
-       must pass. */
-    'Two people can. The table sits in an Amazon Web Services account that also runs systems unrelated to this practice, and that account has two administrators — me, and one other person who administers it with me.',
-    'No one outside those two people has been granted access to the table, and that is measured rather than assumed: every user and every role in the account was simulated against this table, and the only ones that come back able to read it lead to those same two people.',
+       false one. THEY MUST BE RE-SYNCED WHENEVER THAT COPY CHANGES — this set
+       has now gone stale twice, once within the hour of being written and again
+       when Pouya's 2026-09-02 ruling took the human headcount off the page. The
+       rest are near misses on the same subject: the pattern is anchored on five
+       strings that reached `dist/`, not on the ideas in them, so a truthful
+       sentence about administrative access must pass. */
+    "The account's administrators can — me, and the small number of people who administer it with me. The table sits in an Amazon Web Services account that also runs systems unrelated to this practice, and administrative access to that account carries the ability to read the table. That is who can read the stored record; who reads the notification email is a separate question, answered in the last paragraph of this section.",
+    'The access itself is measured rather than assumed: every user and every role in the account was simulated against this table, and every identity that comes back able to read it is reachable only by those administrators.',
+    "The account's root credential — the one path no policy constrains — has no programmatic key, and I hold it.",
     'Two things in the system are narrower than I am, and they are worth stating because they are the part you cannot check for yourself.',
-    'No one else is sent it. There is no CRM, no mailing list and no analytics on the submission.',
-    'Which means there are three copies, not one. The notification in my own mailbox, which is on Google Workspace — so Google holds a copy of whatever you sent me, and so does anyone who can reach that mailbox.',
     /* The replacement summary, which must not trip the third-surface alternative. */
-    'Which means there are three copies, not one. The record in the table, which the two people above can read.',
+    "There are therefore three copies of what you send. The record in the table, which the account's administrators can read.",
+    "The notification, which lands in the practice's mailbox — read by me and by administrative staff — on Google Workspace, so Google holds a copy of whatever you sent me.",
+    'No one else is sent it. There is no CRM, no mailing list and no analytics on the submission.',
     'The table is reachable by the function that writes to it.',
     'Two accounts hold administrative access to the AWS account, and the function that writes to the table cannot read it.',
-    'Nobody else has access to my mailbox.',
-    'There is no team. Every inquiry is read by me.',
+    /* ⚠️ TWO FIXTURES WERE REMOVED FROM HERE ON 2026-09-02 AND THE REASON
+       MATTERS MORE THAN THE STRINGS: `'Nobody else has access to my mailbox.'`
+       and `'There is no team. Every inquiry is read by me.'` They were added as
+       harmless near-misses, and §7's `info@smlcompany.ca` row then established
+       that the mailbox is DELEGATED — Pouya and administrative staff — which
+       makes both FALSE. The second is also a paraphrase of a `mustMatch` breach
+       string. This list is documented as the copy the site legitimately
+       publishes, so a maintainer reaching for a tidier answer would have found
+       one here, which is how this page acquired its false sentence the first
+       time. Removing a false fixture keeps the list true; it is not a coverage
+       change and the freeze does not reach it. `adversarial-reviewer`, round 1. */
     'I act as a neutral. I do not act for a party in a matter I take, and each party should have their own legal advice.',
     'I run a process, I do not run a case for anybody in it.',
     'I will not run a process whose shape nobody agreed to in advance.',