Forge Pool

Appearance

Architecture ​

Planetary Execution Topology ​

Forge Pool is a contract-centric execution network.

The system is organized into four functional layers:

  • Web Core — control plane: auth, policy, billing, job lifecycle
  • Hub — execution authority: sharding, scheduling, verification, aggregation
  • Agent Mesh — shard execution across heterogeneous compute
  • Memory & Artifacts — blobs, KV, replay traces, immutable execution records

The Kernel defines execution semantics across all layers.

End-to-End Topology ​


Client / Studio
↓
Web Core (Auth / Policy / Billing)
↓
Hub (Plan / Shard / Verify / Aggregate)
↓
Agents (Execute shards)
↓
Aggregation + Artifacts + Replay

Web Core ​

Web Core is the policy boundary:

  • project identity and auth
  • rate limits and quotas
  • billing mode and ledger discipline
  • job lifecycle and immutable records

Hub ​

The Hub is the execution authority:

  • deterministic shard planning
  • scheduling and routing
  • verification enforcement
  • deterministic aggregation and result packaging

The Hub does not “do the math.” It enforces execution integrity.

Agent Mesh ​

Agents are untrusted workers:

  • execute shard-only context
  • return signed results and metrics
  • operate under sandbox constraints
  • participate in verification policy (when enabled)

No single agent defines truth.

Kernel ​

The Kernel defines:

  • canonical execution contract
  • determinism rules and seed derivation
  • replay requirements
  • workload typing and versioning discipline
  • verification policy surface
  • aggregation semantics

Verification ​

Verification is embedded into execution and is policy-controlled:

  • redundant execution (spotcheck / quorum)
  • statistical boundary checks (for probabilistic workloads)
  • integrity hashes (results and artifacts)
  • reputation scoring and scheduling penalties

See: Trust