Skip to content

Commit 6194d7e

Browse files
committed
docs(perf): step 7 — the CIM query has now run, so stop saying it has not
The note's "what is still not verified" section claimed the CIM virtualization query "has never executed anywhere, since this container is not Windows". Run 2050 executed it on windows-latest and it returned Win32_ComputerSystem Manufacturer=Microsoft Corporation Model=Virtual Machine, alongside AMD EPYC 7763 64-Core Processor for cpu_model. The sentence was true when written and false one CI run later. What remains unverified is capture on a DEDICATED Windows measurement host. A hosted runner validates the capture mechanism; it is not Step-7 environment evidence, and the tool classifying it honestly as a virtual machine does not make it admissible. Documentation only. No code, no control and no frozen source touched; the harness digest is unchanged at 562a7f7232da. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CYLNQy6tLXqsV1CbuNqsSb
1 parent fd3f09f commit 6194d7e

1 file changed

Lines changed: 8 additions & 5 deletions

File tree

‎docs/notes/p022-263a-step7-environment-capture.md‎

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -218,8 +218,11 @@ string and prints nothing.
218218

219219
## What is still NOT verified
220220

221-
Capture on a **dedicated** Windows host. A hosted runner is not one, and the CIM
222-
virtualization query added above has never executed anywhere, since this container
223-
is not Windows. `envcapture-windows-fixture` exercises the schema and drift rule
224-
on a synthetic manifest and now says exactly that rather than claiming the
225-
Windows branches are unrun.
221+
Capture on a **dedicated** Windows measurement host. The CIM queries have now
222+
executed successfully on GitHub-hosted Windows CI — run 2050 returned
223+
`AMD EPYC 7763 64-Core Processor` for `cpu_model` and `Win32_ComputerSystem
224+
Manufacturer=Microsoft Corporation Model=Virtual Machine` for `virtualization` —
225+
but a hosted runner is validation of the capture **mechanism**, not Step-7
226+
environment evidence. `envcapture-windows-fixture` exercises the schema and drift
227+
rule on a synthetic manifest and says so rather than claiming the Windows branches
228+
are unrun.

0 commit comments

Comments
 (0)