Forge Pool

Appearance

Execution Surface Architecture ​

The Forge Pool API is easiest to understand when separated into execution authorities.

Public Surface ​

The public surface is what developers and customers interact with directly.

This includes:

  • authentication
  • project-scoped execution
  • canonical request submission
  • result retrieval and artifact references

This layer is presented through Web Core.

Web Core ​

Web Core is the system boundary for:

  • authentication
  • tenancy
  • project ownership
  • billing context
  • persistence
  • public API lifecycle

Web Core does not perform the distributed execution itself. It governs access to it.

Hub ​

Hub is the execution authority of the Planetary Kernel runtime.

Hub handles:

  • workload planning
  • shard construction
  • seed propagation
  • verification policy handling
  • deterministic reduction
  • replay metadata production

Hub is execution truth, not dashboard identity.

Agents ​

Agents execute shard-level work.

They are responsible for:

  • receiving deterministic shard payloads
  • executing the assigned work
  • returning result payloads and metrics
  • participating in mixed-trust verification flows when required

Agents do not own global job truth. That belongs to the Hub reduction layer.

Adapters, Studio, and Labs ​

These sit above the Kernel and make Forge Pool more usable in real workflows.

  • Adapters translate domain-specific inputs into canonical Kernel execution envelopes
  • Studio orchestrates workflows, stages, and artifact-aware composition
  • Labs package domain narratives and higher-order execution patterns for verticals

These layers do not replace the Kernel. They rely on it.

The Key Idea ​

Forge Pool is not a pile of unrelated APIs. It is a layered planetary execution system.

The API becomes easy to understand when you see the stack like this:

text
Public Client
  -> Web Core
  -> Hub / Planetary Kernel Runtime
  -> Agents
  -> Artifacts / Replay / Platform Surfaces

That is the architectural truth the API documentation should communicate.