GoRunChat Overview

GoRunChat is ready for implementation work from the active architecture contract.

Product runtime implementation has not started. Shell runtime proof exists. Production app deployment is not signed off. Production app DNS is not signed off.

This guide turns the active repo canon into public build instructions. It names the stack, ownership boundaries, implementation waves, runtime inputs, infrastructure state, deploy path, audit rules, and writing style.

Current Status

• Architecture and contract signoff: Go.
• Implementation start signoff: Go.
• Product runtime signoff: Not yet started.
• Production deployment signoff: No.
• Production app DNS cutover signoff: No.

Implementation teams may start from the contract. They must still prove each wave with the runtime tests and infrastructure checks named in the docs.

Product Target

GoRunChat is a Go-native replacement for LibreChat behavior.

LibreChat remains read-only predecessor evidence. GoRunChat implements the replacement behavior in this repo. It does not patch LibreChat source to make parity true.

The first parity target keeps the tested product behavior from LibreChat where the contract preserves it. When predecessor evidence exposed a blocker, GoRunChat uses the replacement spec as the normative behavior.

Fixed Stack

• Backend: Go, net/http, chi, explicit middleware, and explicit service layers.
• Web: templ, htmx, raw SSE, and small JavaScript islands for live chat behavior.
• Native mac: SwiftUI backed by a Go local service and shared contracts.
• Codex: Rust stays authoritative for execution, session state, config, sandboxing, plugin lifecycle, and login state through codex app-server.
• Storage: MongoDB Atlas for operational data and Memorystore for Redis for replay, ordering, and coordination.
• Providers: official Go SDKs for OpenAI, Anthropic, Google, and MCP where they fit.
• Audit: application audit log, immutable chat and discovery journal, BigQuery query copy, and Cloud Storage archive.

Postgres, River, and pgvector are later cutover work. They are not first-parity work.

Build Rule

Do not treat a design closure as runtime proof.

The replacement spec closes architecture ambiguity. Runtime signoff still requires mounted route tests, browser tests, repository predicate tests, generated DTO checks, and infrastructure validation.

Any mutating route covered by audit or discovery must fail closed when required records cannot be written.

Source Canon

Use these repo docs as the active source set:

• docs/architecture/contract.md
• docs/architecture/gorunchat-replacement-spec.md
• docs/architecture/schema-parity-inventory.md
• docs/architecture/w5a-execution.md
• docs/infra/infra-inventory.md
• docs/infra/runtime.md
• docs/infra/secrets.md
• docs/infra/deploy.md
• docs/implementation/ready-to-build.md