FORGE

FORGE is the studio that builds web apps and RIVER pipelines inside the Runink ecosystem. It runs as its own service in the forge-system namespace. It has no domain, no OAuth client and no sign-in of its own. CORE serves it at /forge/ on the console’s own origin and embeds it as the last category of the console rail. CORE also verifies every repository FORGE creates.

This section covers FORGE as CORE serves and verifies it. What FORGE does inside its own service is FORGE’s business. These pages describe only the contract that CORE’s code shows.

FORGE has never been deployed to a production installation. The CORE side described here (the proxy, the rail, central verification and the forge issue consumer) is built and tested in this repository. Treat anything that depends on a running FORGE service as unvalidated in production.

Getting Started

The FORGE rail category: Studio, New chat, recent chats, deep links.

Project manifest & pipeline files

forge.yaml spec v1 and what CORE checks in .dsl / .herd files.

Central verification (core/ci)

How CORE finds, verifies and reports on every forged commit.

Verification profiles

The forge, web and pipeline profiles, and the forgecheck subcommands.

API Reference

The /forge/ proxy, GET /api/forge, studio link parameters, postMessage.

Troubleshooting

Real proxy errors and core/ci descriptions: cause and fix.

How the pieces fit

Piece	Where it lives	What it does
FORGE › Studio	console rail, tab `forgeStudio`	Embeds `/forge/` in a same-origin iframe under a page header that names the chat and its project
Chat history	console rail, under the FORGE label	“New chat”, then FORGE’s recent chats, read from FORGE through the `/forge/` proxy
`/forge/` proxy	`forgeproxy.go` in the core-operator console	Requires a CORE session, strips any client identity header, signs `X-Core-Identity`, and reverse-proxies to FORGE
Central verification	`core-verify-sweep.yml` + `core-verify.yml`	Verifies FORGE and every private `forged` repository and posts the `core/ci` commit status
Forger	`core-forge-run.yml`	Takes the oldest open `forge`-labelled issue and runs `core 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. CORE mirrors none of this.

One path to file briefs: FORGE’s. Since 2026-09-25 the console files no briefs, creates no repositories and plans nothing. The old POST /api/forge, /api/forge/change and /api/forge/plan were deleted. See API Reference.