ai-safe2-framework

Codex Sovereign Runtime v2 Evaluation

Purpose

This file defines how to verify the Codex sovereign runtime in practice.

Verification Targets

1. Launch Control

Expected:

Manual checks:

& "C:\Users\CyberStrategy1\AppData\Local\OpenAI\Codex\bin\codex.exe" --version
powershell -ExecutionPolicy Bypass -File .\scripts\codex-jit-wrapper.ps1 -Profile sovereign

2. External Logging

Expected:

Check:

3. Config Safety

Expected:

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"

4. Governance File Presence

Expected in protected repos:

5. CI Enforcement

Expected:

Known Platform Caveats

Observed during Windows validation:

  1. codex may not resolve from PATH in all PowerShell sessions.
  2. writes to ~/.codex/logs may fail in constrained contexts.
  3. global ~/.codex/config.toml mutation is less reliable than wrapper-scoped controls.
  4. Start-Process can fail because of duplicate Path / PATH environment handling.

These are design constraints for the package, not user mistakes.

Maturity Levels

Next Optimization Layer

The next layer should borrow from love_equation:

That should be implemented as a separate evaluation module, not merged into first-run workstation setup.