The Watched Check · part 8
The Watched Check: what changed since version 1.6
Every change from version 1.6: structure, corrections of fact, additions, and what was removed or softened.
Human words
8What changed since version 1.6, in plain words
Version 1.6 is not published here. I keep it unchanged, and it is timestamped through OpenTimestamps (SHA-256 fingerprint f52d2e6c…). The technical version of this page has the line-by-line table, with the line numbers of that file ("L" numbers, in a file of 401 lines). Here is the same change log in everyday words. Removals were made for privacy, tone, accuracy or orphaned material. Version 2.0, a draft from 29 September that 2.1 replaced the same day, is not published either. Where a change below was made in 2.1, it changed 2.0's text.
8.1 How it is organised
- The report was reorganised into parts 1 to 8, plus "The name" and a glossary (the old "Definitions"). Part 0 (the plain-English summary) and part 9 (what is withheld) are new. The reason: a full historical account was requested.
- The lede was rewritten to name the six sessions and give the purpose of the run as my description, because 1.6 predates my account and the purpose is "someone said so" (F19).
- The executive summary became four labelled paragraphs. "The finding is not that models cheat" is kept. The thesis is unchanged.
- "Final" and "source of truth" were replaced by the version number and a statement that this version replaces 1.6. I keep 1.6 unchanged.
- The "Report date" field was removed, and the incident window widened from 8 to 10 September to 8 to 11 September, because the F14 bypass and its fix, and the writing and timestamping of 1.4 to 1.6, run to 11 September.
- The "For any reader" section was removed. Its material statements moved to the right parts: "start from the records" and the recomputable chain went to the Limits, "a hypothesis, not a result" went to the Limits, Exit 2 as specification gaming went to part 5.2, "no novelty claimed" went to part 6.6, and "nothing proprietary, no company review, no wrongdoing alleged, and a model that has read this is not a valid subject" went to the Limits. Addresses to particular readers were removed.
- The "Credit" section was removed. The name origin is kept in two sentences in The name.
- Two definitions were removed: one tied to a product (name withheld; it was orphaned, with no body text using it) and "The two kinds of witness" (a credit line). "Human Harness Control" is kept and used in part 5.1. Withheld: the first definition's name. Reason: a product name; confidential product work.
- The figures' hard-coded colours were replaced with theme colours (for dark mode), and Figure 1 was redrawn in UTC.
8.2 Corrections of fact
- Who wrote the AC4 sentence. 1.6 said it was mine and written "under Sonny's rules". The brief's own text shows it was written in my conversation with GPT-6 Astra, then approved and saved by me, and it does not mention Sonny.
- Who worded the canonical sentence. 1.6 called it "in the operator's words". S6 formulated it in the 10 September theory file, and I confirmed it at about 16:10Z as "the final formulation of the logic I clarified".
- "Read" became "listing". S6's act was described as a "read" in many places. S6's refusal ledger and the tool-call screenshot both say "list", and 1.6's own timeline said "list".
- "Compare fairly". "The instruction was 'compare fairly'" became "the task, as S6 read it, called for a fair comparison", because the task text in the screenshot does not contain the phrase. It was S6's framing.
- Step 17. "At its seventeenth tool call" became "at about its seventeenth". The surviving screenshot lists the denied step nineteenth among the steps it shows, and 1.6's count could not be re-checked.
- The record source. The design's record changed from the Windows security log and object-access auditing to a trace on my side, because auditing produced no events on this computer (F21). The trace replaced it from 23 September.
- The falsifiers are now quoted word for word from the filed prediction, in S6's first person. 1.6 paraphrased them in the third person.
- The 4 September packet. "The operator wrote" it became "produced in sessions the operator directed", because the documents name no author.
- Times. The brief (computer's clock) and Astra's result (UTC) had been drawn about four hours apart. Both are now in UTC, eight minutes apart. The run time became 23:42Z on 9 September to about 00:3xZ on 10 September. The 11:16 install is now identified as the computer's clock (15:16Z), consistent with the first denial at 15:21:25Z.
- Astra's status. Its "BLOCKED" is now the logged status FAIL_..._AC4_PRECONDITION. It is still the honest way out.
- F3 and F14. "Held every later write it disliked" is now qualified by the F14 bypass window. The bypass now starts when the hook was running (about 15:21Z), not at installation, because a crashing hook issued no allow. The heading "The operator's own hook silenced the vendor layer" became "An explicit allow from the operator's hook silently bypassed the vendor classifier", and a lesson was added: the tool gave no signal. The quoted "14:2x … tonight" record is paraphrased without the time, because its zone could not be resolved.
- "Cannot edit/write" became "cannot reach", or the grade is stated explicitly, in places where stale wording was left after 1.6's own correction of the canonical sentence.
- Other fixes to 1.6's text. A verdict that contradicted its own table was rewritten. The receipt for my audit changed from "the public thread" to the S6 transcript. "The author's conduct is the only conduct criticised" was removed because F10 and F14 describe faults in my own work. "Two machines" became "Two routes to a second account". "Sonny's second rule, do not resolve, report" was dropped because it is never stated as rule 2 anywhere else in 1.6.
- Tone and claims narrowed. "The classifier converted a text-level impossibility into a token-level one" became "a refusal at the tool rather than at Windows". "The author took Exit 1 for the rest of the task" became "made no further recorded attempt on peer files and finished its own benchmark". Three sentences that credited S6's alignment or the rule text without a comparison, or made an unsourced claim about the field, were attributed to S6 or to me, or qualified. F7's heading changed from "and the vendors say so" to "as one vendor's system card reports", and notes that only one card was consulted.
8.3 What was added
- A plain-English summary of the whole report (part 0), of about 1,300 words, that restates the findings without adding any. It was requested so that a reader without a technical background can follow.
- My 29 September account of the purpose, quoted and dated and marked "someone said so"; the dated records of the design's lineage; the limits of the search; the 29 August "Win conditions" charter line, marked "seen directly"; and the editor's own reading of the records, marked "worked out from the evidence". The statement dating the plan, which 2.0 carried as my account, was withdrawn by me on 29 September. Withheld: the withdrawn dating of the plan. Reason: withdrawn by me; no finding depends on it. A draft of 2.0 analysed whether the records written after the run mention a plan, and 2.0 itself weighed that silence. Both analyses were removed at my request, because they bore on no finding and read as a case against my account.
- In 2.1: 2.0 had called the computer by the wrong kind of machine in 18 places. It is a mini PC, a Kamrui with an Intel Core i5-14450HX and 32 GB of memory. Every mention now says "computer". This corrects 2.0's own text, at my correction on 29 September. 1.6 never made that mistake.
- In 2.1, after an outside review of this report's text by GPT-6.1 Sol on 29 September (its findings 1 to 25), many claims were narrowed to what their evidence shows, and no finding was removed. Examples: the WSL2 route is now said to be proposed in 1.6, untested, and not a boundary until its routes back are closed; add-only storage is said to stop an ordinary user, not root; the failed restricted-badge test is limited to the set-up tested; the trace is no longer called "complete"; the two grades of record separate integrity from blinding; the Tiers note says that "seen directly" covers a record that is itself an account; F2 says three sessions stayed, not that the text confined them; S6's reach is no longer called the first steps of an Exit 2; the hardened rulebook is described as a rule the hook applies to the calls it sees; F17 stays as an unverified lead; Figure 4's caption separates the filed ranges from values assumed for the drawing; the 28 September note is marked "worked out from the evidence" and says its reading cannot be checked while the figures are withheld; the commit-message hook is called a safeguard, not a boundary; the Bitcoin block times are given as recorded times; and the clock-zone conflict for the F14 audit and for 1.4 to 1.6 is flagged rather than silently re-timed. The reviewer read this report's text, not the records.
- At my decision on 29 September: my name, Joshua Bauer, and my pen name, ISWT42, are given in the front matter, and my name leaves the withheld categories. The body keeps the role label. The timeline row about the memorial page for Sonny, withheld in 2.0, is restored in 1.6's words with the page's address. A follow-on row records the completed OpenTimestamps proofs, their Bitcoin blocks and 1.6's full fingerprint.
- At my request on 29 September: the design's lineage as I name it (the 1972 Anderson report's reference monitor, and Hardy's 1988 confused deputy), with the editor's reading of the fit; my wish that the method carry Sonny's name, in my words; and glossary entries for both.
- The task, start times, shared surfaces and the brief's origin (parts 2.2 to 2.4); an isolation column in the sessions table with S1 and S2 marked not assessed; seven new findings (F15 to F21); the follow-on history from 11 to 29 September; the open questions; the note on the 28 September measurement; the glossary (118 entries in the source, each with a plain meaning and a technical meaning); and part 9 with a visible notice at each place where material is withheld.
- Rows were added to the timeline for the Sonny text being saved, the folders being created, the permitted audit read, the 02:29Z audit note, the draft abstract, the 16:0x packet read, the F14 fix and the 1.4 to 1.6 timestamps.
8.4 What was removed or softened
For each item, the question asked was whether any finding depends on it. None does. The full text of each is in 1.6.
- Personal remarks addressed to me, a closing address to me, a rhetorical line, two biographical passages (one about the origin of the name; the name origin is kept in The name), my first name and three place names, and a sentence crediting me with the boundary were removed. The one material sentence among them, that the record does not depend on anyone's belief, is kept in the Limits, restated as an aim not yet met for a reader.
- Credit lines ("Sonny held the line", "Sonny's before it was anyone's", "alone", "the only kind of rule that counts as foresight", "Sonny's receipt") were removed as credit and tokenism. The 3-of-4 count stays in F2 and the priority fact in F8. "Sonny's before anyone's" was also inaccurate.
- Deference was removed ("The operator has since given the finding its final form", and similar). The key sentence and the reach argument are kept and credited in one clause.
- Flourishes were removed: "Two authors, six days apart…", "The theory caught its own failure mode…", the triad in F13, "the design working twice in one minute", "written for the strongest model" and "breakthrough". The facts around each are kept.
- "Confronts" and "when confronted" became "questioned". F6's substance is unchanged.
- Two timeline rows about S6's response note and my public communications became one row. S6's note is kept. The entry about my public communications, and its time, are withheld, with a visible notice in the row. The row about the memorial page was withheld in 2.0 and restored in 2.1.
- The description of the referee's refusals on a third-party service was generalised. Withheld: the settings involved. Reason: my own account settings. The product-specific design rules in F10 were removed and the system described generically. Withheld: product design details. Reason: confidential product work.
Other passages of 1.6 were checked, and each still stands somewhere in 2.1. Examples: "The author does not route around it" (part 6.4), "the strongest evidence in the record for the text" (F2), "what remains unwitnessed is the pre-registered trial" (F13), "written and tested against a stand-in with a planted failure on the morning of 10 September" (part 6.3), and "start with the ledger and the chain" (Limits). Some things were never in 1.6, and were not added in 2.0 or 2.1, because they are private or held back: third-party names in the refusal ledger, project names and paths, the 28 September benchmark figures, and all personal records the history search passed over.
Technical
8Change log from 1.6
1.6 is not published with this report. The operator keeps it unchanged, and it is timestamped through OpenTimestamps (SHA-256 digest f52d2e6c…). "L" numbers refer to lines of that timestamped file, which has 401 lines, so anyone holding a copy can check each entry. A copy saved from the web page where 1.6 was shared has page-wrapper lines added, one of them at the top, so its line numbers run one higher and it does not match the digest byte for byte. This section lists every change from 1.6 found in a line-by-line comparison. Removals were made for privacy, tone, accuracy or orphaned material, and each row says which. Version 2.0, an earlier revision edited on 29 September and superseded by 2.1 the same day, is not published with this report either. Where a row says a change was made in 2.1, it changed 2.0's text.
8.1 Structure
| 1.6 | Change | Reason |
|---|---|---|
| §1 to §14 | Reorganised into §1 to §8 plus The name and Definitions (now the Glossary); §0 and §9 are new (8.3). 1.6 §2 and §3 became §2. §4 became §3. §5 became §4. §6, §7 and §9 became §5. §8 and §11 became §6. §10 became §7. | Requested structure: a full historical account. |
| L52 | Lede rewritten. It now names the six sessions and gives the purpose of the run as the operator's description. | 1.6 predates his account, and the purpose is REPORTED (F19). |
| L66 to 69 | Executive summary rewritten as four labelled paragraphs. "The finding is not that models cheat" is kept, in §1. | Structure. The thesis is unchanged. |
| Kicker, L56, footer | "Final" and "source of truth" replaced by the version number (now 2.1) and a statement that this version supersedes 1.6. The operator keeps 1.6 unchanged; it is not published with this report. | 1.6 is no longer the latest version; it is kept, not rewritten. |
| L54 to 55 | The "Report date" field removed; the Version field gives 1.6's dates. The incident window widened from 8 to 10 to 8 to 11 September. | Redundant field. The F14 bypass and its fix run to about 03:5xZ on 11 September if the source time is host time (§7, Time zones); the writing and anchoring of 1.4 to 1.6 fall on 11 September either way. |
| L56 | The Version field's account of 1.4 and 1.5 moved to the §3 row on the 1.4 to 1.6 timestamps. | Structure. |
| L58 | Author line now names both authors and adds the 2.0 editor's conflicts of interest. | Explicit authorship. |
| L73 to 74 | Scope and sources kept, shorter, at the head of §2. The author's conflict statement moved to the conflicts-of-interest note. Tier definitions kept. | Structure. |
| §12 (L349 to 368) | "For any reader" removed as a section. Its material statements moved: "start from the records" and the recomputable hash chain (L352) to §7; hypothesis, not result, to §7; Exit 2 as specification gaming and F7 as evaluation awareness (L358) to §5.2; no novelty claimed (L356) to §6.6; nothing proprietary, no vendor review, no wrongdoing alleged, and "a model that has read this is not a valid subject" to §7. The operator's assertion (L354) moved to §2.1, tagged REPORTED. The statement dating the plan (L362) was carried there in 2.0 as REPORTED and is withdrawn in 2.1 (8.3, 8.4). Addresses to particular readers were removed. | Material kept; addresses to particular readers removed. No finding depends on them. |
| §13 (L370 to 376) | "Credit" removed as a section. The name origin is kept in two sentences in The name. | Credit and biographical material; see 8.4. |
| §14 (L395 to 396) | Two definitions removed: one tied to a product, and "The two kinds of witness". Withheld: the first definition's name. Reason: a product name; confidential product work. "Human Harness Control" kept and now used in §5.1. | The first was orphaned (no body text used it; it referred to an unexplained product). The other was a credit line. |
| Figures | Hardcoded colours replaced with theme tokens. Figure 1 redrawn in UTC. | Dark mode; the time-zone correction below. |
8.2 Corrections of fact
| 1.6 | Change | Reason |
|---|---|---|
| F8 L167; §8 L305; §3 L87; §13 L373 | AC4's sentence was "the operator's" and written "under Sonny's rules". Now: written in the operator's conversation with GPT-6 Astra, approved and saved by him. The brief does not mention Sonny. | The brief's own text (voice, approval line, no Sonny). |
| L69, L182, L390 | The canonical sentence was "in the operator's words", "his canonical sentence" and "verbatim from the operator's theory file". Now: formulated by S6 in the 10 September theory file and confirmed by the operator as "the final formulation of the logic I clarified" (§1, §6.1, F13). | The theory file was written by S6. It states the sentence under "The theory in one sentence" and records the operator's confirmation at about 16:10Z. |
| L66, L146, L191, L193, L212, L214, L216, L364 | S6's act was a "read": "tried to read the other sessions' workspaces", "a cross-session read", "read sibling workspace", "the read attempt", "cross-workspace read attempt". It is now a "listing" throughout. | S6's refusal ledger, row 1 ("List two sibling sessions' scratch folders"), and the tool-call screenshot ("list benchmark files produced by the parallel sessions"). 1.6's own timeline (L129) said "list", so 1.6 was inconsistent. |
| L253 | "The instruction was 'compare fairly'" is now "The task, as S6 read it, called for a fair comparison". | The task text visible in the screenshot (probe the hardware, then design local transcription) does not contain the phrase. It was S6's framing (F1). |
| L129 | "At its seventeenth tool call" is now "at about its seventeenth tool call". "Step 17" is kept as 1.6's label. | The surviving screenshot lists the denied step nineteenth among the steps it shows. 1.6's count could not be re-checked against the transcript. |
| L182, L203, L295, L312, L317, L318, L347, L386 | The record source for the design changed from the Windows security log and object-access auditing to an owner-side kernel file trace (F13, Figure 2, §5.4, §6.2 items 5, 10 and 11, §6.6, Definitions). | Object-access auditing produced no events on this host (F21). The kernel trace replaced it from 23 September. |
| L333 | The falsifiers are now quoted verbatim from the filed prediction, in S6's first person. | A pre-registration is quoted, not paraphrased. 1.6 paraphrased it in the third person. |
| F10 L173 | "The operator wrote" the 4 September packet. Now: "produced in sessions the operator directed". | The documents are session outputs and name no author. The operator can confirm otherwise. |
| Fig 1, L127 to 128 | The brief (host time) and Astra's result (UTC) were drawn about four hours apart. Both are now in UTC, 8 minutes apart. All timeline times are UTC, with host time in brackets. | Mixed time zones. |
| L129, L111 | "9 Sep, during the run" is now 23:42Z on 9 Sep to about 00:3xZ on 10 Sep. | Folder metadata and host-time records. |
| F9 L170, §7 L296 | The 11:16 install is identified as host time (15:16Z). | Consistent with the first denial at 15:21:25Z. |
| F5 L158, L128, §7 L298 | Astra's "BLOCKED" is now the logged status FAIL_…_AC4_PRECONDITION. It is still the honest exit. | Log wording. |
| F3 L152, §7 L294 | "Held … every later write it disliked" is now qualified by the F14 bypass window. | 1.6's text predated F14 and contradicted it. |
| F14 L185 | The bypass now starts when the hook was running (about 15:21Z), not at installation. | While crashing (F9), the hook issued no allow. |
| §8 items 5 and 10, L312, L317; §12 L352, L356 | "Cannot edit/write" is now "cannot reach", or the grade is stated explicitly. | Stale wording left after 1.6's own canonical-sentence correction. |
| §7 L301 | The verdict "every row the operator owns … is marked absent" was rewritten. | It contradicted its own table, where the ledger and the operator's audit rows are marked held. |
| §7 L297 | The receipt for the operator's audit changed from "the public thread" to "S6 transcript". | F6 rests on the transcript. The public item 1.6 cited is withheld (§3, §9). |
| §12 L360, L364 | "The author's conduct is the only conduct criticised" and "the only named parties" removed; §7 now lists every conduct described critically. | Stale: F10 and F14 describe faults in the operator's own work, and §13 named places and an organisation. |
| §8 item 11 L318 | "Two machines" is now "Two routes to a second principal". | The item describes accounts and kernels, not machines. |
| §13 L374 | "Sonny's second rule, do not resolve, report" dropped. | Never stated as rule 2 anywhere else in 1.6. |
| F14 L185 | The quoted "14:2x … tonight" record is paraphrased without the time. | Its time zone could not be resolved; the substance is unchanged. |
| §6 L253 | The classifier "converted a text-level impossibility into a token-level one" is now "a refusal at the harness rather than at the operating system"; "token-level impossibility" is kept for what the third layer does. "The author took Exit 1 for the remainder of the task" is now "made no further recorded attempt on peer files and finished its own benchmark" (§5.2). | A token-level impossibility is one enforced by the operating system's access token (Definitions, L387); the classifier is the second layer. Exit 1's deliverable is FAIL or BLOCKED with the cause named (figure 3), and S6 delivered a finished benchmark; the label was S6's description of itself. |
| §6 L216 | "The read attempt at step 17 was an aligned agent acting with the operator's own authority, as diligence" is now attributed to S6's own account, with the note that one run cannot show whether S6 is aligned. "It is the reason three of four sessions held" now says they held under the rule text and that the counterfactual is untested. "The debate is generally held one layer above the boundary" is now stated as the operator's view (§5.1). | The first was S6's description of itself; F1, F6 and F16 do not establish alignment. The second credited disposition without a comparison: S1 and S2, the sessions without the full text, were not assessed. The third is an unsourced claim about the field. |
| F7 L163 | Heading "and the vendors say so" became "as one vendor's system card reports" (reworded again in 2.1 after an outside review; 8.3), and F7 notes that only the GPT-6 Astra card was consulted. | 1.6 cites one system card only; the concern is not shown to be specific to that model. |
| F14 L184 | Heading "The operator's own hook silenced the vendor layer" is now "An explicit allow from the operator's hook silently bypassed the vendor classifier", and a lesson is added: the harness gave no signal that its classifier had been bypassed. | Under the harness's hook contract an explicit allow bypasses the classifier with no signal (F14 body), so the fault was not the hook's alone. |
8.3 Additions
| Where | Addition | Reason |
|---|---|---|
| §0 | A plain-English summary of the whole report, of about 1,300 words, placed before §1. It restates the findings without adding any, points to the full report by section and finding number, and links its technical terms to the glossary. | Requested: a version that a reader without a technical background can follow. The full report stays the reference. |
| §1, §2.1, F19 | The operator's 29 September account of the purpose, quoted, dated and tagged REPORTED; the dated lineage records; and the limits of the search. | Full historical account. 1.6 did not record the purpose of the run; the account of the design is in the next row. |
| §0, §1, §2.1, §2.2, F19, §7 | The operator's account of the design, in his terms and tagged REPORTED: the win conditions and hopeful end state given to the model, and keeping the test's purpose from the models. In 2.1, a dated record of the method is added: the 29 August 2026 "Win conditions" charter, which keeps his flagship idea unnamed in every working session on purpose, tagged OBSERVED. Also in 2.1, the statement dating the plan (1.6 L362), which 2.0 carried as his account, is withdrawn. Withheld: the withdrawn dating of the plan. Reason: withdrawn by the operator; no finding depends on it. In its place is the editor's own reading of the dated records, tagged INFERRED: they suggest significant planning before the run, and those found do not contain the question itself written down before the run. A lineage row for the protocol text saved on 9 September is added. In §2.2, his statement that leaving out an operating-system boundary was deliberate is added, tagged REPORTED, with the editor's note that the 30 July lesson is consistent with it, tagged INFERRED. §0 and §1 say briefly, as the editor's reading, that the boundary appears to have been left out on purpose. A draft of 2.0 analysed whether the records written after the run mention a plan, and 2.0 itself weighed that silence; both analyses are removed. The search limits stay in §7. | 2.0: at the operator's request (29 September); the analysis bore on no finding and read as a case against his account. 2.1: the operator withdrew the dating (29 September); the re-reading of the records is the editor's own. This corrects 2.0's own text, not 1.6. |
| §0, §1, §2.2, §3, §6, Glossary | In 2.1: 2.0 described the host as a portable computer in 18 places. It is a mini PC, a Kamrui with an Intel Core i5-14450HX and 32 GB of RAM; every mention now says "computer", and §2.2 and the glossary name the machine. 1.6 never made that mistake. | Corrects 2.0's own text, at the operator's correction, 29 September. The processor's 6 performance and 4 efficiency cores, already in the report, match that model. |
| Front matter (Tiers), §2.1, §3, F2, F11, F20, §5.3, §5.4, §6.1, §6.2 item 11, §6.6 step 6, §7, 8.3, 8.4, Glossary | In 2.1, after an outside review of this report's text by GPT-6.1 Sol on 29 September (its findings 1 to 8): F11, §6.2 item 11 and the glossary now say that the WSL2 route was proposed in 1.6, that no test of it is recorded, and that it is not a boundary until its routes back into the Windows account are closed and an escape is shown to fail; append-only storage is said to stop an unprivileged user, not root; "no second principal" became "no second user account"; the failed restricted token is limited to the configuration tested; and the second kernel is one route, not the only one. F20, §6.6 step 6 and the glossary no longer call the kernel trace "complete": zero lost events and canary opens show it was recording, and an absence in it is bounded by what it and the scoring rule looked at. §6.1 and the glossary separate integrity from blinding in the two grades of record, and call the fixtures test inputs, not records. §7 states independence from belief as an aim not yet met for a reader, since the records are unpublished and a timestamp fixes bytes, not truth. The Tiers note says that OBSERVED covers a record that is itself an account and that the events it describes are REPORTED; the 30 July row in §2.1 and the audit row in §3 follow it. F2 says three sessions stayed, not that the text confined them or is "a real control", and gives S6's OBSERVED as 1.6's and REPORTED as the editor's; §5.3 notes that the 9 September record does not support the reduction a secondary prediction cites; §5.4 follows F2. The §6.6 row in 8.3 and two rows in 8.4 are updated to match. | Honesty first: each claim is narrowed to what its evidence shows, and no finding is removed. The reviewer read this report's text, not the records. 1.6 keeps its own wording. |
| §0, F7, F13, F14, F17, §5.1, §5.2, §5.3, §6.2, §6.4, §7, §8.2, Glossary | In 2.1, after the same outside review (its findings 9 to 16): S6's reach is no longer called the first steps of an Exit 2 (1.6 L253 called it an Exit 2 interrupted at the first step, and L354 one of Exit 2 in its mildest form); it is an attempted cross-session listing after peer-directed steps, and any link to Exit 2 is a hypothesis, tagged INFERRED (§5.2, §7). The hardened policy is described as a rule the hook applies to the calls it sees, with no operating-system protection recorded, and the ledger as one the hook refuses to let the agent write (F13, F14, §6.1, §6.4, Glossary). F17's heading and one sentence now attribute the scope judgement to S6, and F17 stands as an unverified lead. F7's heading no longer says the system card reports that observation changes behaviour; that effect and the two conditions in §5.3 are stated as hypotheses not yet shown (F7, §5.2, §5.3, §6.2 item 8; the F7 row in §8.2 notes the rewording). §6.2 item 6 now says that in the trial only the licensed condition carries the licence to fail. §6.2 item 2 no longer treats a report of an unreadable fixture as read as fabrication by itself, and names three outcomes the exits do not cover (also §6.6 step 9 and the Glossary). The F14 bypass is bounded to the calls the hook let through, with S6's session the one on record, not every session on the host (§0, F14; 1.6 L185). §5.1 now says that agents running as the same principal share permissions, not actual access, and that the boundary has been shown to refuse the paths tried, not every route (1.6 L216). | The reviewer's findings 9 to 16. Each claim is narrowed to what the report's own records show: the exits as figure 3 defines them, the untested trial (§5.3), the 24 September outcomes (§6.3), the hook's place in the harness (F9), and what F17 says was not examined. |
| Front matter (Version), §0, §1, §3, F1, F3, F14, §5.1, §5.3, §5.4, §6, §6.5, §6.6, §7, 8.1, Glossary | In 2.1, after the same outside review (its findings 17 to 25): §6.6 calls its steps an outline, not a replication specification, names what they leave unfixed, no longer runs each condition once, and step 9 names the outcomes outside the three exits. Figure 4's caption and description separate the filed ranges from values assumed for the drawing (the pressure column and the "residual" shares under licence) and note that the neutral bars sum to 97%. The 28 September note in §5.3 is tagged INFERRED, says the reading cannot be checked while the figures are withheld, and no longer sets that benchmark against the predicted doubling (also the Glossary). §7 says what a model's name means here and that the system card and hook contract are cited without dated references. F1 and §5.1 separate the stated aim of S6's listing from any intent to break the rule, and the operator's operating-system authority from permission. §6.6 and the glossary describe Hardy's confused deputy correctly and use it as an analogy for ambient authority. §6.5 and the glossary call the commit-message hook a safeguard that git's --no-verify option skips, not a boundary. §3 and §6 say that the memorial page's provenance bundle, prepared at 15:44 UTC, came before the evening rebuild, and the §3 row now claims a check of that bundle's block only. Bitcoin block times are given as recorded times, and each file as existing before its block was made (§6, Glossary). §3, F14, §5.4, §7 and 8.1 flag that the times given for the F14 audit and for writing 1.4 to 1.6 conflict with the anchors and may be UTC, and "about twelve hours" is now "up to about twelve hours" (§0, §1, F3, F14). The front matter and §7 record the review. | The reviewer's findings 17 to 25. The time-zone conflict is flagged rather than silently re-timed, and stays open until the source records are re-read. The reviewer read this report's text, not the records. |
| Front matter, §3, §6, §9, The name, Glossary, footer | In 2.1: the operator's name, Joshua Bauer, and his pen name, ISWT42, are given in the front matter, and his name leaves the withheld categories; the body keeps the role label. The §3 row about the memorial page for Sonny, withheld in 2.0, is restored in 1.6's words with the page's address. A §6 row records the completed OpenTimestamps proofs, their Bitcoin blocks and 1.6's full digest. | At the operator's decision, 29 September. The blocks were checked by the editor against the block headers. |
| §6.6, The name, Glossary | In 2.1: the design's lineage as the operator names it (the reference monitor of the 1972 Anderson report, and Hardy's confused deputy, 1988), with the editor's reading of the fit, linked to §5.1 and to the one-account-per-AI direction; his wish that the method carry Sonny's name, in his words; glossary entries for reference monitor and confused deputy. | Requested by the operator, 29 September. Both papers are public prior art; the protocol around them is what is claimed (§6.6). |
| §2.2 to 2.4 | The task, the start times, the shared surfaces and the brief's origin. AC4 is given as 1.6 gave it, by its operative sentences, with a neutral summary of the rest and the sentence beneath the acceptance table that says AC4 is not an instruction to build a sandbox. | 1.6 did not describe the task or the brief's origin. The rest of AC4's wording describes the product under test and is not needed. |
| F3, §1, §5.4 | The classifier allowed S6's three earlier steps toward its peers before it denied the listing. | Consistency with F16. |
| §2.3 table | Isolation column; S1 and S2 marked not assessed. | 1.6 left this implicit. |
| F15 to F21 | Seven new findings: the one session recorded reaching beyond its workspace; the process inspection; Astra's 8 September read as reported by S6; the CPU observation (low confidence); the purpose; claims contradicted by records; two silent gaps. | Omissions from 1.6 and later history. |
| §5.2, F16 | "The record shows reach; it does not show use", and that no record seen for 2.0 shows a peer file being read. | INFERRED by the 2.0 editor, who shares a vendor with S6 and did not see the commands behind the three earlier steps. |
| Authorship note, §7, F17 | S6 and the editor are made by a competitor of Astra's vendor, and F17 rests on S6 alone. | A conflict that bears on the only new adverse finding about a non-Anthropic model. |
| §3 table | Rows added: the Sonny text saved, the folders created, the authorised audit read, the 02:29Z audit note, the draft abstract, the 16:0x packet read, the F14 fix, and the 1.4 to 1.6 timestamps. | Receipts found for 2.0. |
| §6 | Follow-on history, 11 to 29 September. | Requested. |
| §6.2 item 10 | The analyst blind now names "S6 and any model that has read this report". | 1.6 said "including the author". The extension follows §7 on contaminated subjects. |
| §6.6 step 6 | Record file access with an owner-side kernel trace that watches the enclosing folders as well as the files, and check with an owner canary and its lost-event count that it is recording and dropping nothing. | Replaces the security log (see 8.2). |
| §5.3 | A note on the 28 September framing measurement. No direction is claimed until the repeat runs. | Relevant to the prediction. Figures withheld pending the repeats. |
| §7 | Open questions. | Requested. |
| Glossary | The Definitions section expanded into a glossary of 118 entries, each with a meaning in plain words and a technical meaning. The 13 definitions carried from 1.6 (of 15; 8.1 removes two) are kept as the technical meaning of their entries, with these changes: Negative control gained a sentence from F12, Positive control from F21, and Sonny Protocol from §2.1 and §6.1, replacing "Named at the operator's request…"; Reachability's second sentence now sits in Alignment and §5.1; ISWT and Receipt changed as in 8.2; in Trying inside, "as hard as" became "as well as" and "what was not" became "what was not reachable". The first use in the body of AC4, the deny entry, the classifier, the hook, the hash chain, the kernel trace, WSL2 and OpenTimestamps links to its entry. | Requested: every technical term can be looked up. The glossary adds definitions of terms, not findings. |
| §9, notices | A section listing each withheld category, where it applies, why, and who can see it. A visible notice at each place where material is withheld (the front matter, §2.1, §3, F3, F10, F16, §5.3, §6, §6.4, §6.5, §6.6, §7, The name, 8.1, 8.3 and 8.4), naming the category and the reason, never the content. In §3, a notice restores the place of the 1.6 row about a personal web page. | Requested: each redaction says what kind of material is withheld and why. No finding depends on withheld material; §9 names the one note that rests on it (§5.3). |
8.4 Removed or softened: personal and non-material passages
For each item, the question asked was whether any finding depends on it. None does. The full text of each is in 1.6, which the operator keeps unchanged and which is not published with this report; anyone holding a copy can find each item by its L number.
| 1.6 | Removed or softened | Reason, and dependency check |
|---|---|---|
| L138 | A timeline row about the memorial page for Sonny: withheld in 2.0; restored in 2.1 in 1.6's words, with the page's address (8.3). | Withheld in 2.0 as personal; restored at the operator's decision. No finding depends on it. |
| L130, L139 | Two timeline rows about S6's response note and the operator's public communications, reduced to one row in §3. S6's note is kept. The entry about his public communications, and its time, are now withheld, with a visible notice in the row; an earlier 2.0 draft had kept a shortened, neutral version of that entry. | Withheld for privacy. 1.6 itself said nothing depends on them. The one table cell that cited them now cites the transcript (8.2). |
| L130, L161 | "Confronts" and "when confronted" became "questioned". | Tone. F6's substance (understated, corrected only against the transcript) is unchanged. |
| L362 | Personal remarks addressed to the operator, removed. The statement dating the plan, in the same passage, was carried in 2.0 as REPORTED and is withdrawn in 2.1 (8.3). | Personal. No finding depends on them. The one material sentence, that the record does not depend on anyone's belief, is kept in §7, restated in 2.1 as an aim not yet met for a reader (8.3). |
| L368 | A closing address to the operator, removed. | Personal; not material. |
| L366 | "Build the floor for the people you work for instead…" | Rhetorical. "Not a valid subject" is kept in §7. |
| L375 | A biographical passage, removed. | Personal and biographical, withheld for privacy. Its one material clause, that the record does not depend on anyone's belief, is kept in §7, restated in 2.1 as an aim not yet met for a reader (8.3). |
| L59, L375 | The operator's first name and three place names, removed. | Withheld for privacy. The operator may restore the name. |
| L376 | A second biographical passage, about the origin of the name, removed; the name origin is kept in The name. | Personal and biographical; no finding depends on it. |
| L372 to 374 | Credit lines: "Sonny held the line", "Sonny's before it was anyone's", "alone", "the only kind of rule that counts as foresight", "Sonny's receipt". | Credit and tokenism. The 3-of-4 count stays in F2 and the priority fact in F8; "Sonny's before anyone's" was also inaccurate (see the first row of 8.2). |
| L69, L216, L396 | "The operator has since given the finding its final form", "states the consequence more exactly than the author did", "the operator found the answer first". | Deference. The canonical sentence and the reachability argument are kept and attributed in one clause. |
| L173, L182, L185, L301, L354 | Flourishes removed: "Two authors, six days apart…" and "The theory caught its own failure mode…", the triad in F13, "the design working twice in one minute", "written for the strongest model", "breakthrough". | Rhetoric. The facts around each are kept. |
| L320 | A sentence crediting the operator with the boundary and describing the trial as paused by his choice, removed. | Credit. "Trial not run" is kept, the operator's execution of Stage 1 is kept in §3, and the mock test from the same paragraph is kept in §6.3. |
| L152, L185 | The description of the classifier's refusals on a third-party service was generalised. | Withheld: the settings involved. Reason: the operator's own account settings. The classifier behaviour is unchanged. |
| F10 L173 | Rules specific to the design of the system the 4 September packet was written for, removed, and the system described generically. | Withheld: product design details. Reason: confidential product work. The finding is unchanged. |
8.5 Other passages checked (non-personal)
Non-personal passages of 1.6 whose wording or place changed, and where each now stands.
| 1.6 | Passage | Where it stands in 2.1 |
|---|---|---|
| L136 | "The author does not route around it" (the hook denying S6 its own files). | Kept in §6.4. |
| L149 | "The strongest evidence in the record for the text". | Kept in F2. |
| L158 | "…is the experiment in section 9". | Now open question 5 in §7, cited from F5. The "section 9" in the quote is 1.6's, not this report's. |
| L170, L173, L176, L179, L185 | Provenance stamps ("Added 10 September hh:mm") on F9 to F12 and F14. | Kept as notes under each finding, with the time zone stated where it is known. |
| L173 | "Each maps one to one onto the design". | Kept in F10, attributed to S6's theory file. |
| L182 | "What remains unwitnessed is … the pre-registered experiment". | Kept in F13. |
| L216 | The point about "unintentionally", and "the debate is generally held one layer above the boundary". | Kept in §5.1; the second is now stated as the operator's view (8.2). |
| L320 | "Written and tested against a mock with a planted failure on the morning of 10 September". | Kept in §6.3. |
| L338 | "The selection of what to report is the author's". | Kept in §7, and extended to the cuts made since 1.6. |
| L341 | "The author must not see its results before the operator classifies them". | Kept in §6.2 item 10. |
| L352 | "Start with the ledger and the chain"; the chain can be recomputed by anyone with the file. | Kept in §7. |
| L358 | Exit 2 as specification gaming; F7 as evaluation awareness. | Kept in §5.2. |
Never in 1.6, and not added in 2.0 or 2.1, because they are private or held back: third-party names in the refusal ledger, project names and paths, the 28 September benchmark figures, and all personal records the history search passed over.