Skip to main content

How WonderForge Works

WonderForge is built on a single, powerful idea: everything is an artifact. A workspace, a document, an image, a conversation, a build pipeline, a deployment target — they are all artifacts. Each one has an identity (a unique ID) and a name. That's it. One kind of thing, one set of operations, one mental model.

This uniformity is not an accident. Traditional platforms force you to learn different rules for different entity types — files behave one way, projects another, settings yet another. WonderForge eliminates that cognitive overhead. Once you understand how artifacts work, you understand how everything works.

The forge metaphor​

The name is intentional. In a blacksmith's forge, raw materials are shaped, combined, and transformed into finished works. The same material can become anything depending on how it is worked. WonderForge applies this principle to digital creation: artifacts are your raw materials, and the platform gives you the tools to shape, connect, and transform them into whatever you need.

The terminology follows suit. Flux — the substance a blacksmith uses to fuse metals together — is the name for the relationship system that binds artifacts to each other. It is a small touch, but it reflects a design philosophy: the platform should feel like a creative workshop, not a database.

What this section covers​

These pages explain the foundational concepts that make WonderForge work. Start here to build your mental model, then move to the guides for hands-on practice.

  • Type System — How artifact type definitions give structure and meaning to the uniform artifact model, including specs, status, schemas, and API groups.

  • Flux & Relationships — How artifacts connect to each other through flux relationships that carry semantic meaning and drive behavior across the system.

  • Flux Types — The complete catalog of nine built-in relationship types, organized into structural, reference, and operational categories.

  • Events — How every change in WonderForge becomes an observable, auditable event that flows through the artifact graph.

  • Subscriptions — How to listen for changes and react, routing events to subscribers and external systems.

  • MCP Server — How AI agents interact with WonderForge natively through the Model Context Protocol, the agent-first interface.

Each concept builds on the ones before it. The type system gives artifacts their shape. Flux gives them relationships. Events make those relationships reactive. Subscriptions route those reactions. And the MCP server opens all of it to AI agents as first-class participants.