PHASE 2 — CLONE AND PIN THE SOURCE
Captured: 2026-08-06
Environment: WSL2 / Ubuntu 26.04 LTS, git 2.53.0, running as root
Clone location: /root/audits/ten-proofs        (Linux ext4, NOT /mnt/e)
Pinned worktree: /root/audits/pinned           (detached HEAD)

================================================================
CLONE COMMAND (exact)
================================================================
git -c core.autocrlf=false -c core.eol=lf clone \
    https://github.com/openai/ten-proofs /root/audits/ten-proofs

Exit code: 0
Full clone. NOT shallow — full history retained so that
`git log --all --find-object=<blob>` remains possible.

================================================================
REPOSITORY IDENTITY
================================================================
remote origin (fetch) : https://github.com/openai/ten-proofs
remote origin (push)  : https://github.com/openai/ten-proofs
HEAD commit SHA       : 94bc0feb6a9ff12c7d31d6de640a725c9d43d2b6
committer date        : 2026-08-01T17:22:31-07:00
author date           : 2026-08-01T17:22:31-07:00
commit subject        : "."          (a single period)
tree hash             : 174289e4d4958cb0509874e6e53400e098213de7

history depth         : 1 commit
branches              : main (local); remotes/origin/main; origin/HEAD -> origin/main
tags                  : (none)

NOTE ON HISTORY DEPTH: the repository contains exactly ONE commit. There is
therefore no earlier revision of ConnesRigidity.lean in reachable history.
The audit-prompt fallback
    git log --all --find-object=81cf03e3... -- ConnesRigidity.lean
is moot in this repository: it could only ever return this same commit.
Recorded so that "no historical revision found" is not later misread as a
failed search.

NOTE ON DATES: the commit is dated 2026-08-01, while the GitHub repository
object reports created_at 2026-08-05T21:07:49Z. The commit therefore predates
its publication. This is ordinary for a squashed/imported single-commit push
and is recorded as an observation, not an anomaly.

================================================================
WORKING TREE STATE
================================================================
git status --porcelain=v1 : (empty — clean)
git submodule status      : (empty — no submodules)

Git LFS: git-lfs is NOT installed in this environment, and the repository
contains no .gitattributes. ConnesRigidity.lean is 1,449,151 bytes of real
content whose SHA-256 matches the expected checkpoint, so it is not an LFS
pointer file. No LFS state to record.

Effective git config in the clone (git config --list --show-origin):
    file:.git/config  core.repositoryformatversion=0
    file:.git/config  core.filemode=true
    file:.git/config  core.bare=false
    file:.git/config  core.logallrefupdates=true
    file:.git/config  remote.origin.url=https://github.com/openai/ten-proofs
    file:.git/config  remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
    file:.git/config  branch.main.remote=origin
    file:.git/config  branch.main.merge=refs/heads/main

No core.autocrlf or core.eol entry is persisted in the repo config; the clone
was performed with them forced off on the command line, and the Linux default
is autocrlf=false regardless. Verified empirically below.

================================================================
CHECKPOINT COMPARISON — ConnesRigidity.lean
================================================================
                        EXPECTED (audit prompt)                          OBSERVED (local)                                 RESULT
git blob SHA            81cf03e3f7ccdc66815cc00c9969bcfd2341c8d6         81cf03e3f7ccdc66815cc00c9969bcfd2341c8d6         MATCH
raw SHA-256             31f6c419f341ee6aa5b03bc15800a9d8ee2c654c...      31f6c419f341ee6aa5b03bc15800a9d8ee2c654c...      MATCH
                        ...344aab90bdef0639353ccc91                      ...344aab90bdef0639353ccc91
physical line count     37,374                                           37,374                                           MATCH
byte size               (not specified)                                  1,449,151                                        recorded

LINE-COUNT METHOD (the audit prompt does not define one):
    wc -l  -> 37374
    The file's final byte IS a newline (verified with `tail -c 1`), so every
    physical line is newline-terminated and `wc -l` equals the true physical
    line count. No discrepancy between counting methods arises here.

CRLF INTEGRITY CHECK:
    Count of CR (0x0D) bytes in the file: 0
    => No LF->CRLF rewriting occurred. The SHA-256 above is of genuine
       LF-terminated content, and the known autocrlf hazard did not fire.

ALL FOUR SOURCE-IDENTITY CHECKPOINTS MATCH. The audited revision is
identified as commit 94bc0feb6a9ff12c7d31d6de640a725c9d43d2b6. No mismatch
handling, historical-revision search, or separate-worktree divergence
procedure was required.

================================================================
FINAL THEOREM NAME — DIVERGENCE RESOLVED
================================================================
The audit prompt records the final theorem as:
    exists_nonisomorphic_propertyT_icc_groups_with_isomorphic_factors

formalization.yaml headlines a different, stronger declaration:
    exists_infinite_pairwise_nonisomorphic_propertyT_icc_groups_with_isomorphic_factors

ComparatorChallenges/E_ConnesRigidity.json resolves this: BOTH declarations
exist and BOTH are subject to the repository's own checker, namespaced under
`ConnesRigidity.`:

    "theorem_names": [
      "ConnesRigidity.exists_nonisomorphic_propertyT_icc_groups_with_isomorphic_factors",
      "ConnesRigidity.exists_infinite_pairwise_nonisomorphic_propertyT_icc_groups_with_isomorphic_factors"
    ]

The prompt's checkpoint name is therefore NOT stale — it is one of two
declared results. Which is intermediate and which is final is determined in
the Phase 6/7 source and axiom work, not assumed here.

================================================================
PINNED WORKTREE
================================================================
Command:
    git -C /root/audits/ten-proofs worktree add --detach \
        /root/audits/pinned 94bc0feb6a9ff12c7d31d6de640a725c9d43d2b6

git worktree list:
    /root/audits/ten-proofs  94bc0fe [main]
    /root/audits/pinned      94bc0fe (detached HEAD)

RE-VERIFIED INSIDE THE PINNED WORKTREE (post-checkout):
    HEAD      : 94bc0feb6a9ff12c7d31d6de640a725c9d43d2b6
    SHA-256   : 31f6c419f341ee6aa5b03bc15800a9d8ee2c654c344aab90bdef0639353ccc91
    lines     : 37374
    bytes     : 1449151

Identical to the primary checkout. All build and check work occurs in
/root/audits/pinned so that later movement of origin/main cannot alter the
audited subject.

================================================================
REMOTE-DRIFT BASELINE
================================================================
Captured BEFORE toolchain installation and before any build:

    $ git ls-remote origin refs/heads/main
    94bc0feb6a9ff12c7d31d6de640a725c9d43d2b6	refs/heads/main

This queries the REMOTE, not a local ref (a local ref cannot move without a
fetch, which would make any "unchanged" report vacuous). The same command is
re-run at audit completion and compared against this value. If it differs,
the new SHA is reported separately as its own finding and the pinned
worktree is left untouched — no checkout, merge, pull, rebase, or reset, and
no silent rerun against the new revision.
