FORGE
FORGE is a category of Runink TIDE, next to Overview, DevEx, DataEx and Intelligence: the studio inside TIDE that builds web apps and RIVER pipelines. FORGE and TIDE are one app, and FORGE is its canvas-style side: FORGE’s services run inside the TIDE console, on the console’s own session, and FORGE › Studio is a console route, the lanes canvas. It has no domain, no OAuth client, no sign-in, no namespace and no service of its own. TIDE also verifies every repository FORGE creates.
FORGE_OWNER_EMAIL is set and names you. Unset means nobody, unlike the console’s other access lists, where unset means every signed-in operator. FORGE’s reads (the studio, the chat history, the planner) need only a TIDE session.This section covers FORGE as TIDE serves and verifies it.
How the pieces fit
| Piece | Where it lives | What it does |
|---|---|---|
| FORGE › Studio | console rail, tab forgeStudio | The lanes canvas as a console route, under a page header that names the chat and its project, with a notice for each missing capability (GET /api/forge-studio) |
| Chat history | the Studio header’s Chats button | FORGE’s recent chats, read from FORGE’s in-process ChatService; the rail itself has only “New chat” |
| FORGE services | the TIDE console | FORGE’s Identity, Forge, Project and chat services on the console’s gRPC-web server; GitHub writes gated on FORGE_OWNER_EMAIL |
| Central verification | a TIDE workflow | Verifies every private forged repository and posts the core/ci commit status |
| Forger | a TIDE workflow | Takes the oldest open forge-labelled issue and runs tide session against it. Disarmed by default |
GitHub is the database. A forged app is its repository (topic forged). Its work queue is its forge-labelled issues. Its build state is the core/ci commit status on its default-branch head. TIDE mirrors none of this.
One path to file briefs: FORGE’s. The console itself files no briefs, creates no repositories and plans nothing. See API Reference.