Your work. Your space.

Find the right Gonu tool for the next step.

Features & demosExplore Engineering Brain workflows and sample screensExploreWeb ChatFor quick questions, planning and everyday workTry nowDesktop WorkerFor local repository work with a dedicated desktop appDownloadVS Code ExtensionFor developers who already work in VS CodeSource betaGonu CLIFor terminal workflows and structured task inspectionSource betaGonu IDEFor developers exploring an integrated Gonu editorNot releasedDocs & demosPractical guides for every Gonu toolLearn
Skip to content
gonu.
Checking account…Try on web
Web workspace

Verified fixes, memory and private reviews

Inspect real checks, protect acceptance rules, correct memory, cap task usage and review alternatives before choosing a result.

Open verification workspaceExplore the example

WHEN IT HELPS

Put it to work.

Use this when a change affects a critical flow such as login, subscriptions or workspace permissions, and the team needs evidence rather than a completion label.

Before you begin

  • A Gonu account with access to the selected project.
  • Backend verification migration 033 and an existing recorded engineering task.
  • A configured, offline Docker executor and managed server project for Change Rehearsal.

WALK THROUGH IT

See the workflow, step by step.

Interactive example

Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.

  1. In Engineering → Verification → Business rules, an owner/admin links expected behavior to an existing executable check and protects its test files. Approving a rule does not authorize running commands.

  2. Use Worker, CLI or VS Code with a selected repository. Provide build/test commands and, for a bug, an optional focused reproduction command. Approve the plan, file changes and commands. The same reproduction must fail before editing and pass afterward.

  3. In Memory, inspect source and revision; correct, pin, forget or restore entries. Preview authorized context for a question. In Task budgets, set a cumulative conversation cap that follows the same session across tools.

  4. Change Rehearsal prepares explicit file alternatives, then runs one command on a baseline and two separate offline copies after approval. Private reviews freeze task evidence for selected existing workspace members. Reviewers can approve recorded results or request changes; owners can revoke access.

gonu / Verified fixes, memory and private reviewsSAMPLE
g.
ILLUSTRATIVE SCREEN · 1 / 4

Business rules / Illustrative setup

RequirementA failed payment must not grant paid access.
CheckAn existing project test command
Protected filetests/payment_access.py
Example only · your real screen shows your own data.
Step 1 of 4

THE USEFUL RESULT

What you should leave with.

An inspectable evidence packet, corrected persistent context, an enforced conversation budget and a private decision trail. Results cover only the commands and environment actually tested.

Know the boundaries.

  • Model review is not a security certification or a production-readiness guarantee.
  • Rehearsal V1 compares explicit replacements in a bounded managed project; it does not recreate production or upload local folders.
  • Task caps are usage units, not guaranteed currency prices. Failed or incomplete provider responses may retain reserved usage.
  • Memory preview does not promise perfect recall or identical reasoning across models. Private reviews require existing authorized members.

IF SOMETHING DOESN’T WORK

A result is incomplete, a budget stops execution, or rehearsal cannot start.

Read the recorded failed/missing check. Fix the specific prerequisite or explicitly increase the task cap. For rehearsal, verify the Docker executor and configured image; there is no host-execution fallback. Never mark an unrun check as passed.

Contact support