gogogo docs

Get started

• Overview — What gogogo is, who it is for, and the seven async layers it ships.
• Go for almost everything, zig for the exception — The thesis behind the stack: Go for almost everything, Zig as the named exception, and how to choose without hype.
• Architecture decision: flat stack over framework + abstraction — The flat-stack decision record: what it serves, what it replaced, and the migration it completed.
• Getting started — Clone, run, first five minutes, and the commands you need.

Agents

• CLI — The installer as scriptable commands: advise, preview, apply, add, check.
• MCP server — Install the MCP server, wire it into your client, and the six tools.

Core

• Architecture — Directory layout, dependency direction, entry points, and route wiring gotchas.
• Stack in layers, not silos — Every dependency and what it buys, layer by layer.
• Costs, tradeoffs & comparisons — What each choice rejected, what it costs to keep, and when to revisit: Turso vs SQLite vs Postgres, Datastar vs React, and the rest.
• Features — Every capability and its runtime opt-out.
• API routes — Generated inventory of every API route, pinned by tests — the trim and hook gate that proves no route is lost.
• Recipe: API without auth, without Turso — Recipe for stripping auth and the database out of a clone that needs neither.
• Use cases — what each core / plugin / feature is for — What each core, plugin, and feature is for, in business language.
• Scope taxonomy — Core / Plugin / Feature: the rule for deciding what is safe to delete.
• DB concurrency: single-writer today, MVCC if ever (spike doc) — Turso single-writer stance, the probed MVCC path, and revisit triggers.
• Configuration — Every environment variable and runtime constant.
• RBAC (Casbin): the complete guide — Casbin RBAC: role vocabulary, the feature checklist, and hint-vs-enforcement.
• Native boundary (Go-first, Zig as escape hatch) — Go-first policy: why Zig is an exceptional native boundary, the agent decision procedure, and the isolation, testing, and removal rules.
• Native language tradeoffs (exception candidates) — Evidence-backed tradeoffs of Zig, Rust, Nim, Odin, and Mojo as native exception languages, and what a non-Zig proposal must rebut.

Async

• Seven async layers — The seven async layers, SSE Hub record-sync vs ephemeral signals, cross-instance and offline sync.
• Realtime UI recipe (for humans and coding agents) — How to add live UI: client/server patterns, checklist, no invented transports.
• DagNats durable workflows — DagNats capability table, version bounds, learned gotchas, and the add-a-workflow path for LLM agents.
• DagNats trigger console: bootstrap workaround — The upstream DagNats bug that breaks the trigger console on a fresh install, and the removable seed that works around it.

AI

• LLM and AI credits — GoAI configuration and the optional ai-credits / BYOK plugin.
• Review loop — The review loop: Genkit flows, goai generation, and a Jev-compatible classifier judge.

Frontend

• The Todo example — The Todo reference implementation and the contract to imitate.
• UI skins — Pluggable DaisyUI / Basecoat skins and the plugin contract.
• UI sounds — Vendored cuelume sound feedback and its accessibility contract.

Ship

• Deploy to your own box — Server layout, first-time setup, deploy workflow, build pipeline and version badge.
• Desktop & Mobile — Wails v3 desktop/mobile, edge sync, and the native window.
• Admin & Dashboard — Admin surfaces, the single-cookie session, and the DagNats console.

Operate

• Local CI — The five-tier feedback loop and make signoff.
• Code quality — The 33 linters, how to scope them, the Datastar-specific rules, and the ruleguard rules that encode project footguns as CI failures.
• Troubleshooting — Symptoms and where they actually come from.
• Debugging with DuckDB — Query JSONL logs and the Turso file with DuckDB: local operator recipe.

Releases

• All releases — every CHANGELOG.md section as its own article page.