FORGE Documentation
FORGE is a chat studio that ships web apps and RIVER data pipelines inside the
Runink ecosystem. You describe what you want in a chat. The platform’s own coding agents
write the code in a repository in the organisation, and CORE verifies it. FORGE is a
category of the CORE console, served at core.runink.org/forge/. It has no domain,
sign-in or front door of its own.
The loop in one paragraph
One chat is one project. A project is one GitHub repository with one or more
lanes. Each lane is a component folder, either a RIVER pipeline or a web app, and
the lanes are listed in forge.yaml at the repo root. You
write a brief for a lane, and your send is the approval. Only then does FORGE
write to GitHub: it creates the repo on the first approval and files the brief
verbatim as a forge issue. CORE’s coding agents pick that issue up, and CORE
verifies each lane folder, posting core/ci/<lane> and core/ci commit statuses that
FORGE reads back live. Free-form text goes to the sovereign in-cluster model, which
only proposes steps. Nothing is filed until you approve.
Where things live
| What | Where |
|---|---|
| The studio (Flutter web) and the backend (Go, gRPC and gRPC-web) | org-runink/forge, one image, namespace forge-system |
Sign-in, the rail, the /forge/ reverse proxy | CORE’s console |
| What is built: repos, briefs, verification | GitHub, read live and never mirrored |
| The chats (transcript and draft canvas) and the actor audit | FORGE’s own encrypted appfs root |
| The coding agents that do the work | CORE (core-forge-run.yml) |
| Verification of every forged repo | CORE (core/ci, core/ci/<lane>) |
Sources
CLAUDE.md; grpc/api/proto/forge/v1/{forge,chat}.proto; grpc/cmd/; grpc/internal/;
flutter/lib/features/forge/.