DYNAMIC PATH.
ASK AUTHORITY.
TRUTHFUL STATE.
OHGO enforces structural execution boundaries across your codebase. Models are untrusted proposal engines—the runtime controls tool admission, capability policy, and state verification.
Analyzing symbols, reading specs, & planning tasks. No code changes allowed.
01. THE THREE WORKSPACES
Architectural Invariant: Workspaces are runtime authority boundaries, not UI visual themes.
Read-only workspace for understanding user intent, searching codebases, dependency analysis, git inspection, and architectural planning.
Adversarial and exploratory investigation. Executes commands, stress tests, benchmarks, and reproduces bugs without mutating repository source files.
Sole repository mutation authority. Performs patches, creates files, refactors code, runs builds, and executes verification steps.
02. RUNTIME SIMULATOR & TOOL ADMISSION
Test how OHGO admits or denies tools below the UI based on Capability Policy.
Authority pipeline: Workspace → Capability Policy → Tool Admission → Execution
03. ARCHITECTURE & ARTIFACT HANDOFFS
Cross-workspace workflows communicate using structured artifacts—never conversation inheritance.
04. CORE ARCHITECTURAL INVARIANTS
Non-negotiable rules governing runtime authority, sessions, and persistence.
Exactly three primary workspaces (ASK, FUZZ, BUILD). BUILD is the sole mutation authority. ASK & FUZZ can never mutate code.
Model output is untrusted proposal. The runtime capability policy enforces boundaries below the UI regardless of model intent or prompts.
$sup opens a quick reference query layer on the SUP model role. It never alters main task history, persistent context, or workspace state.
Sessions retain resolved effective models across restarts in ~/.ohgo/sessions.db. Unfinished states resume truthfully; unknown stays unknown.
<root>/.ohgo/project.yml establishes stable project identification without duplicating global session storage databases.
Existing execution engine is preserved. Architectural changes occur only at defined seams through audit, minimal change, and verification.