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
08 / Proof of WorkBeta workflow

A result you can inspect.

Review recorded file changes, checks, model findings and approvals instead of relying on a completion message.

Public demo · no login needed. Real workspace use requires sign-in, project access and a configured release.

TAKE A LOOK INSIDE

See how the workflow fits together.

Interactive illustration

All screens use synthetic sample content. Clicking through this demo does not run a model, access your files, change an account or use your allowance.

  1. Select a recorded task in Verification. Inspect its actual status and changed-file evidence.

  2. Inspect command exit codes and output. Distinguish executed checks from model review and unperformed validation.

  3. Review the exact diff and unresolved limitations. Record a private review decision or request a change.

g.Proof of WorkSAMPLE
ILLUSTRATIVE WORKSPACE

Evidence / Checkout timeout

Files

Recorded changes only

Task

Recorded execution identity

Status

Based on required evidence

This is a sample evidence layout, not a passed task.
Step 1 of 3

A useful first request

Show the evidence for this fix: changed files, actual checks, missing validation and any remaining risks.

MADE FOR Authors, reviewers and engineering leads

When it earns its place.

Decide whether a change has enough evidence to move forward, and see exactly what has not been tested.

THE USEFUL RESULT

A review decision backed by recorded observations.

Private review access is limited to permitted workspace members. Evidence does not reveal hidden model reasoning.

CURRENT CAPABILITIES

Know exactly what to expect.

Implemented beta workflow. Your server needs the matching release, project access and required setup.

Implemented in the beta

  • Recorded checks, evidence packets and private reviews.
  • Exact-diff approvals and honest incomplete states.

Not available yet

  • Evidence for checks that were never configured or executed.
  • Production-similarity scoring and universal performance guarantees.

GET READY

Start with the right context.

  • An existing recorded engineering execution.
  • Configured checks and current permission to view its project.

Brain workflows require the matching API/Web release and an authorized managed project. The model, executor and integrations must be configured for the task you choose. Opening a demo does not enable an integration.

Open verification workspace

Practical guides

Verified fixes, memory and private reviewsWeb workspaceEngineering task evidenceWeb workspaceDiscuss your team's setup