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
11 / Institutional MemoryBeta workflow

Keep the knowledge through the handoff.

Retain deliberately shared design decisions, incidents and handover notes with ownership and revision history.

Explore the demo Open onboarding & handover

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

Interactive demoWhen to use itCurrent capabilitiesSetup & guides

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. Add a shared decision or handover note with references and a clear owner.

  2. Edit the shared record as decisions change. Reassign responsibility when needed; previous revisions remain inspectable.

  3. Generate the onboarding guide or export permitted project knowledge, then review it before sharing.

g.Institutional MemorySAMPLE
ILLUSTRATIVE WORKSPACE

Handover / Async settlement

Why

Keep request handling bounded

[S1]
Reference

Selected architecture note

[S2]
Owner

Explicit project assignment

[S3]
Synthetic note; only deliberately shared knowledge is retained.
Step 1 of 3

A useful first request

Create an onboarding outline for settlement using the shared decisions. Cite sources and mark missing operational knowledge.

MADE FOR Growing teams and maintainers

When it earns its place.

Help a new teammate understand why a system works this way after roles change or an engineer leaves.

THE USEFUL RESULT

A durable, reviewable handover that remains useful as team membership changes.

Source permissions are rechecked; personal memory is never silently included in a team export.

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

  • Versioned shared decisions, incidents and handover records.
  • Ownership reassignment and portable knowledge exports.
  • Bounded relevant records in ordinary project chat across models.

Not available yet

  • Automatic capture of every review, meeting and external discussion.
  • Perfect recall or identical reasoning across different models.

GET READY

Start with the right context.

  • Approved project-shared knowledge and reference sources.
  • An authorized owner for handover records.

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 onboarding & handover

Practical guides

Shared rules, memory & auditWeb workspaceKnowledge & source documentsWeb workspaceEngineering Brain: your software and its historyWeb workspaceDiscuss your team's setup