FORGE

The FORGE planner, and the forger that builds what it plans. See also FORGE.

What it does

Describe the application or data pipeline you want. FORGE proposes the work, you shape it as lanes on a canvas, nothing is filed until you approve, and then Runink TIDE drafts the code as a pull request.

• Planner (FORGE chat): proposes steps, each a new app or a change to an existing one, with a brief for each. You edit the lanes and components on the canvas yourself.
• Forger: once armed, takes the oldest open brief that FORGE filed after your approval and that nobody has edited since, and drafts the code as a draft pull request. Any other brief is left for a person, and the run says which.

What it reads

• Planner: your message, the apps that already exist, and the app you selected.
• Forger: the filed brief and the project’s repository.

What it produces

• Planner: a reply and a list of proposed steps, shown on the canvas for approval.
• Forger: a draft pull request with the pipeline or app code. TIDE checks that it builds; it does not run tests. Every forged commit is then checked by TIDE’s central verification.

Human oversight

A person approves or edits every proposed step, and a brief is filed only after approval, word for word. A person reviews and merges the forger’s pull request. FORGE never merges or deploys.

Model

• Planner: Qwen3.6-35B-A3B, by Qwen, licensed Apache-2.0 (the general tier).
• Forger’s coding step: Qwen3-Coder-30B-A3B, by Qwen, licensed Apache-2.0 (the coder tier).

Runink domain adaptation for this agent is planned; this release uses the base model.

Where it runs and data handling

On your TIDE deployment’s own inference, on your Server or in your cloud. Briefs and code go to that model plane and to no third-party AI service. FORGE is served inside the TIDE console, on your TIDE sign-in.

Guardrails

• Nothing is filed or built until a person approves.
• The canvas offers only components from the approved catalogue and the connections the project may use.
• The planner’s steps are checked by the shared judgement checks before they are offered, and the planner’s own verdict words are removed.
• Settings whose names look like credentials are refused. The coding step is instructed not to call an external AI service, deploy or merge, or change databases or CI, and its pull request is a draft a person reviews.

Limitations

• In preview, as described above.
• The canvas works from the approved catalogue; anything else needs a person.
• It does not deploy, merge, or touch CI or databases.

Evaluation

No published evaluation scores yet.

Illustrative example

Invented project. “Add a pipeline that collects reefer temperatures from the yard’s MQTT broker into a table, with lineage.” FORGE proposes one new pipeline with a brief; the owner places it as a lane on an approved connection, with three catalogue components, and approves with one edit, “keep 90 days”. The brief is filed, and the forger later opens a draft pull request with the pipeline for the owner to review.