HUMAN-CONTROLLED AGENT RUNTIME FOR REAL CODEBASES

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.

Select Runtime Authority Boundary:
AUTHORITY:ASK [READ-ONLY]
MUTATION:DENIED ✗
COLOR IDENTITY:Teal (#2dd4bf)
BRAND // UNIFORM
OHGO_ASK
OHGO logo
OHGO BLOB — ASK MODE

Analyzing symbols, reading specs, & planning tasks. No code changes allowed.

LOGO: BOUNCE // WATER // SWIMAUTHORITY: ASK

01. THE THREE WORKSPACES

Architectural Invariant: Workspaces are runtime authority boundaries, not UI visual themes.

EXACTLY 3 PRIMARY WORKSPACES
ASKTEAL
Understand & Reason

Read-only workspace for understanding user intent, searching codebases, dependency analysis, git inspection, and architectural planning.

Mutation Authority:
NONE (Read Only)
Allowed Tools:
readgrepgloblswebfetch
FUZZMAGENTA
Discover & Probe

Adversarial and exploratory investigation. Executes commands, stress tests, benchmarks, and reproduces bugs without mutating repository source files.

Mutation Authority:
EXECUTE YES / MUTATE NO
Allowed Tools:
readbash*waitgrep
BUILDBLUE
Change & Implement

Sole repository mutation authority. Performs patches, creates files, refactors code, runs builds, and executes verification steps.

Mutation Authority:
FULL REPOSITORY MUTATION
Allowed Tools:
writeeditbashread

02. RUNTIME SIMULATOR & TOOL ADMISSION

Test how OHGO admits or denies tools below the UI based on Capability Policy.

ACTIVE:ASK
ohgo-repl — workspace::ask
OHGO Agent Runtime v1.0.0 [Target: Go Codebase]
Authority pipeline: Workspace → Capability Policy → Tool Admission → Execution
[ASK WORKSPACE LOADED] Read-only capabilities active. Model: provider/fast-model
Type help, select sample prompts below, or test write mutations.
PRESETS:
ask>

03. ARCHITECTURE & ARTIFACT HANDOFFS

Cross-workspace workflows communicate using structured artifacts—never conversation inheritance.

Canonical Loop & Artifact Flow:
ARTIFACT HANDOFF CONTRACT
Click on any architecture step above to inspect how structured artifacts bridge boundaries without passing implicit write authority across workspaces.

04. CORE ARCHITECTURAL INVARIANTS

Non-negotiable rules governing runtime authority, sessions, and persistence.

I1-I4. THREE AUTHORITIESRUNTIME

Exactly three primary workspaces (ASK, FUZZ, BUILD). BUILD is the sole mutation authority. ASK & FUZZ can never mutate code.

I5 & I14. MODEL UNTRUSTEDPOLICY

Model output is untrusted proposal. The runtime capability policy enforces boundaries below the UI regardless of model intent or prompts.

I6 & I17. EPHEMERAL $SUPSUPPORT

$sup opens a quick reference query layer on the SUP model role. It never alters main task history, persistent context, or workspace state.

I8 & I10. SESSION TRUTHPERSISTENCE

Sessions retain resolved effective models across restarts in ~/.ohgo/sessions.db. Unfinished states resume truthfully; unknown stays unknown.

I11. PROJECT IDENTITYMETADATA

<root>/.ohgo/project.yml establishes stable project identification without duplicating global session storage databases.

I18. AUDIT-FIRST SEAMSENGINE

Existing execution engine is preserved. Architectural changes occur only at defined seams through audit, minimal change, and verification.