CODEX_GodMode_ON

Create controlled, local-first document case files with immutable intake, native PDF extraction, page-scoped OCR escalation, evidence anchors, validation gates, and reproducible archives. Use when Codex must organize or verify sensitive tax, legal, compliance, audit, or administrative paperwork without silently installing tools, uploading documents, submitting forms, deleting originals, or treating model output as verified evidence.

Reproduce, isolate, fix, and re-test regressions or runtime failures with bounded evidence gathering, one implementation writer, and outcome-based verification. Use with godmode-workflow when a failure needs diagnosis before repair.

Route cross-domain Codex work through bounded advisory specialists with frozen ownership and explicit handoffs. Use with godmode-workflow when runtime, workflow, governance, quality, documentation, or CI concerns need separate analysis.

Build a disposable local-only prototype through a fast single-writer loop with mandatory watermarks and end-to-end outcome evidence. Use only when production correctness, security review, and release readiness are explicitly deferred.

Perform a findings-first code, architecture, contract, or release-risk review with bounded read-only specialists and evidence-backed severity. Use when the requested outcome is assessment rather than implementation.

Orchestrate non-trivial Codex delivery through governance and capability preflight, bounded parallel discovery, a frozen single-writer contract, independent validation, outcome evidence, and release handoff. Use for complex implementation, migration, or release work that benefits from coordinated subagents.

Apply conservative best practices for SwiftUI work on macOS and iOS, including state flow, target-safe changes, and focused Xcode validation.

Apply conservative best practices for Flutter and Dart work, including composable widgets, explicit state boundaries, and focused analyze/test runs.

Bootstrap repo-local governance before parallel Codex implementation starts in an empty, newly initialized, or undocumented workspace.

Classify release impact, discover the repo's release law, and draft the correct release artifact or PR copy for the current workspace.

Apply conservative best practices for React, Next.js, and Node.js work, including explicit client boundaries, server-first data flow, and focused validation.