Powered by Arcanum
The Forge
The world's first full-lifecycle Inference IDE.
Bring the full work of inference into one durable development environment.
Inference, treated as development
Why inference needs an IDE
Inference work is more than a prompt. Prompts, Spells, Sessions, and agent workflows are first-class development artifacts, alongside the context, memory, tools, policy, evaluation, and operations that give each its purpose, history, evidence, and controls.
One complete lifecycle
From an artifact's first definition to its operation in the world.
-
Document
Give the artifact, its intent, and its source a clear home.
-
Version
Keep named revisions, their changes, and the active choice legible.
-
Prove
Test behavior with evidence before the work carries real consequences.
-
Control
Apply the policy, approvals, budgets, and visibility that govern operation.
-
Operate
Run the work through the durable runtime that owns inference.
Document
Make the inference artifact readable.
The Atelier gives Prompts and Spells a home. Use the Codex for standing instructions and metadata alongside markdown source; the Spell editor and Scriptorium keep that source readable in a deliberate source, split, and preview view.
Version
Let every active choice have a history.
The Mirror makes named versions available for activation, inspection, and diff, so a revision is a decision rather than a mystery. The Ledger supplies local status, diff, and commit for workshop artifacts as part of that limited source-control boundary.
Prove
Put inference behavior under examination.
The Proving Grounds bring Trials and Inquisitors together with comparisons and inference traces, so evidence can travel with the work instead of being reconstructed after a result surprises you.
Control
Keep the operator's boundaries visible.
- Policy and approvals
- Wards make policy and operator approvals visible at the point they matter.
- Work in motion
- The War Table keeps agents and their assigned work in operational view.
- Tools and spend
- The Arsenal and Treasury keep available tools, budgets, and spend legible.
- Operational visibility
- The Anvil brings connection, status, and the current operating context together.
Operate
Work through the runtime that owns the result.
The Tome carries Sessions forward, while Campaigns bring agent workflows, tools, memory, policy, and budgets into durable work through Arcanum. The Forge keeps that complete operating context legible while Arcanum performs inference and owns the server-side logic.
One workbench, one source of truth
A thin, authenticated client over Arcanum.
The Forge is an authenticated HTTP-only Avalonia client. Arcanum runs inference and owns server logic; Compendium owns configuration editing. Those separate responsibilities keep the workbench useful without duplicating the runtime's authority.
Current boundaries
The scope is clear on purpose.
The Forge does not run inference or open the Grimoire. The Ledger is limited to local status, diff, and commit; it does not promise push, pull, reset, or rebase. This is a text-led account of the product lifecycle, not a simulated application surface.
The road to The Forge
Start with Arcanum. Join the road to The Forge.
Arcanum comes first; private beta participation helps shape the full-lifecycle Inference IDE that follows.