ADMISSION PREFLIGHT RECEIPT ASSEMBLED. Read-only, nothing run, nothing mutated.

  path:   C:\Users\decid\Documents\projects\spt-core\docs\304-W2-ADMISSION-RECEIPT.md
  commit: d5425e1a5b5b19dd5147de8c68ab39c367dd62dd   (branch main, UNPUSHED)
  blob:   b940bacfa47ed575f986bb1db3ad9314fc668ef7
  sha256: af4244ecbfacb9426a4835e648da0873e04754616685bc02666f1246987efad6
  parent: 5e8b3e09 (the plan). traceable-reqs exit 0, tree clean, one file added.

Taken 2026-09-12T22:57:58Z against subject 85f84d73 and plan 5e8b3e09. ALL EIGHT CONDITIONS MET.

  capacity        120.042 GiB free; floor 96, hard stop 32, both RETAINED. 24.0 GiB headroom.
  local producers cargo 0, rustc 0
  runner          Runner.Worker.exe ABSENT. Listener online and idle, ancestry authenticated:
                  Runner.Listener(22712) <- RunnerService(19588) <- services(1644) <- wininit(1532)
  CI axis         0 non-terminal of 15 on BigscreenVR/spt-bs-core; newest 34676423540 completed
                  success ~17h earlier. Two-step query: list carries status/conclusion, view is
                  reserved for non-terminal runs. gh exit 0.
  hashes          three-way agreement, both manifests verified by sha256sum -c
  isolated home   fp-home ABSENT
  subject         85f84d73, blob 848a23fe, detached, porcelain empty
  build shape     ONE build via --build-current; CARGO_BUILD_JOBS=2 read at r8:935, not recalled
  build estimate  UNKNOWN, by your instruction. Not borrowed from a debug figure, from the 46 s
                  warm targeted-test wall, or from CI -- none of those measures this producer.

YOUR TWO PINS, VERIFIED INDEPENDENTLY BY ME:
  R8-FROZEN.sha256              6384a8c9ec77dea62ed2bdff2d3a43acb9f038df5a328b1186375a56fb06e108
  INSTRUMENTS-STAGED-r5.sha256  c658dd3ffb7c04436e4391f5ed0726a7188f230549b3ab5278b092cab7c95cbd
Both match. sha256sum -c: 10 of 10 OK on the freeze manifest, 6 of 6 OK on the staged manifest.

THE HELPER-PIN PREREQUISITE IS NOW CLOSED, and closed the way you originally asked -- the ACTUAL
RESOLVED FILES, not an unchanged review tree. All five agree across three independent sources I
measured myself: the accepted bundle-r4 baseline, the reissued staged manifest, and the bytes at
$BIN right now. census 7a50b14e, cpubracket fc10031d, d1_render 3b984493, portfields 283386e7,
runner-census 63d0508b.

TWO THINGS I PUT IN THE RECORD THAT A CLEAN CHECKLIST WOULD HAVE HIDDEN:

1. EIGHTEEN spt.exe PROCESSES ARE LIVE ON THIS BOX. Every one authenticates to a legitimate parent
   -- the resident daemon at 4732, agent perches under spt-mobile-host(11836), omp-spt chains,
   terminal-hosted sessions. Live infra, NOT producers, NOT to be reaped. Named in the receipt so a
   later reader does not read a busy process table as a busy box.

2. BUNDLE-R4-FROZEN.sha256 IS NOT BESIDE THE r5 BUNDLE. It is under a different session scratchpad
   root. My first search was bounded to the r5 tree and returned nothing. I DID NOT REPORT THAT
   ABSENCE -- a full-depth search found it immediately. Recording the near-miss because a bounded
   search reported as a fact is exactly the error I made this morning on the driver, and the r4
   baseline is what makes the three-way chain a chain rather than two files agreeing with each
   other.

WHAT THE RECEIPT REFUSES TO IMPLY, stated in it rather than left to inference: every reading is
POINT-IN-TIME. Capacity, the process table and the CI queue are volatile. It records that the
conditions were met at 22:57:58Z and binds nothing about the moment a producer runs. It does NOT
discharge the plan's requirement that subject HEAD, blob and clean tree be reasserted immediately
before the rollout producer -- those remain boundary observations the driver must take.

Nothing here is a grant and the receipt does not request one. No build, no field run, no host probe,
no elevation; I note liam's elevation handoff needs its own fresh scoped authorization and that
nothing carries forward.

Holding for your review.