This file defines how to verify the Codex sovereign runtime in practice.
Expected:
PATH aloneManual checks:
& "C:\Users\CyberStrategy1\AppData\Local\OpenAI\Codex\bin\codex.exe" --version
powershell -ExecutionPolicy Bypass -File .\scripts\codex-jit-wrapper.ps1 -Profile sovereign
Expected:
wrapper-sessions.log creatednotify.log created when Codex emits notificationsCheck:
C:\Users\<user>\.codex\logs.codex-runtime-logs in the workspaceExpected:
Manual checks:
powershell -ExecutionPolicy Bypass -File .\scripts\audit-codex-install.ps1
powershell -ExecutionPolicy Bypass -File .\scripts\scan-dangerous-config.ps1 -SearchRoot "C:\path\to\repos"
Expected in protected repos:
IDENTITY.mdSOUL.mdAGENTS.mdUSER.mdTOOLS.mdSUBAGENT-POLICY.mdExpected:
Observed during Windows validation:
codex may not resolve from PATH in all PowerShell sessions.~/.codex/logs may fail in constrained contexts.~/.codex/config.toml mutation is less reliable than wrapper-scoped controls.Start-Process can fail because of duplicate Path / PATH environment handling.These are design constraints for the package, not user mistakes.
Level 1: governance files present, audits runnableLevel 2: wrapper launch working with external logsLevel 3: CI enforcement activeLevel 4: optional post-run alignment scoring / drift reviewThe next layer should borrow from love_equation:
That should be implemented as a separate evaluation module, not merged into first-run workstation setup.