Overview
Architecture and planning documentation for Gitwami, the AI-first git host.
Gitwami is an AI-first git host — a git server with code intelligence
(GitNexus), AI pull-request review, and automated merge-conflict resolution,
driven from the rgh CLI. It runs self-hosted as a native NixOS service.
These pages are the living design documents behind that work. They are research/proposals, not yet-shipped features — each says so at the top.
Documents
ActiveGraph continuity layer
Evolving the agent architecture from stateless per-table job queues toward one typed graph, an append-only event log, and behaviors that react to change.
NixOS sandbox fleet
A forkable, stateful, NixOS-native execution layer for agent code — nixos-anywhere + disko + Firecracker microVMs, with workspace snapshots as physical memory.
Developer-facing features
How the developer wins — rewind/fork runs, warm + semantic memory, reactive auto-review, per-line provenance, per-repo agents — map onto the existing code, mostly as small located changes.
Domain name research
Availability research behind the Gitwami rebrand — git + Japanese-mastery naming, checked via the Namecheap MCP.
How they fit together
The continuity-layer plan owns the graph, event log, and behaviors; the sandbox-fleet plan is the deep dive on the execution layer those behaviors run in. The developer-facing features map those ideas onto concrete, located code changes. Together they describe a self-improving agent: fork a sandbox and a subgraph, run both, diff the result subgraphs, and promote the winner.