Forge Pool

Appearance

Economy Overview ​

Forge Pool uses a unified execution-native economic model designed for deterministic, auditable computation at planetary scale.

The economy layer is not a detached billing backend added on top of infrastructure.

It is structurally tied to:

  • execution
  • replay
  • verification
  • attribution
  • settlement
  • provider participation

Forge Pool derives economic activity directly from verified computation across the runtime.

This allows the system to preserve:

  • accounting integrity
  • replay compatibility
  • enterprise auditability
  • provider fairness
  • ecosystem trust

across heterogeneous infrastructure and workload types.

1. The Core Principle ​

Forge Pool accounts for:

verified execution

—not nominal infrastructure ownership or idle capacity.

Workloads become economically meaningful only after they pass through the canonical execution lifecycle:

text
request
→ planning
→ execution
→ verification
→ aggregation
→ settlement
→ replayable ledger record

This ensures that:

  • customers are billed for attributable computation
  • providers are compensated for verified contribution
  • accounting remains replay-compatible
  • settlement remains auditable

The economic model is therefore downstream of execution itself.

2. Economy as Runtime Architecture ​

Forge Pool treats economic coordination as part of the execution architecture.

The economy layer exists to coordinate:

  • usage accounting
  • Credit attribution
  • provider settlement
  • replay-aware auditing
  • ecosystem governance
  • enterprise visibility

Because execution, replay, and settlement are structurally connected, economic trust cannot rely solely on external accounting systems.

Instead, Forge couples:

  • deterministic execution
  • replayability
  • attribution
  • accounting
  • settlement

into one coherent runtime model.

3. The Core Components ​

The Forge Pool economy consists of several tightly connected components.

Credits ​

Credits are the normalized unit of verified execution across workloads.

They allow organizations to reason about usage independently from:

  • hardware type
  • infrastructure ownership
  • machine topology
  • provider mix

See Credits.

Billing ​

Billing defines how execution usage is measured, invoiced, controlled, and exported for operational and finance workflows.

See Billing.

Execution Accounting ​

Execution Accounting defines how workloads become attributable, verifiable, replayable economic records.

It governs:

  • settlement eligibility
  • accounting states
  • replay-aware attribution
  • provider contribution accounting
  • finalized execution records

See Execution Accounting.

Marketplace ​

The Marketplace defines how adapters, compute providers, and ecosystem participants interact through a shared execution economy.

See Marketplace.

Node Payouts ​

Node Payouts define how compute providers are compensated for verified execution contributed to the runtime.

See Node Payouts.

Provider Policy ​

Provider Policy defines operational, security, and participation requirements for compute providers participating in the runtime.

See Provider Policy.

Adapter Governance ​

Adapter Governance defines the trust, determinism, replay, and publication rules governing adapters within the ecosystem.

See Adapter Governance.

Economic Integrity ​

Economic Integrity defines the architectural principles that preserve trust, replayability, attribution correctness, and settlement integrity across the execution economy.

See Economic Integrity.

4. Design Principles ​

Forge Pool’s economy follows several core invariants.

Execution-Native ​

Economic activity derives from verified computation rather than infrastructure reservation.

Deterministic ​

Accounting and attribution are structurally tied to deterministic execution semantics.

Replay-Compatible ​

Replayability is part of the economic trust model, not merely a debugging feature.

Auditable ​

Usage, attribution, and settlement remain tied to replayable execution records and ledger-backed accounting.

Infrastructure-Neutral ​

The economic system is designed to operate across heterogeneous infrastructure and provider types.

Enterprise-Compatible ​

The economy supports governance, budgeting, reconciliation, export workflows, and organizational accounting controls.

Ecosystem-Expandable ​

The model supports official, private, and partner ecosystem participation without fragmenting the execution substrate.

5. Ecosystem Participants ​

The Forge Pool economy supports several participant classes.

Customers ​

Organizations executing workloads across probabilistic, graph, media, memory, search, and adapter-driven execution domains.

Providers ​

Operators contributing verified compute capacity to the runtime.

Partners and Adapter Authors ​

Organizations building domain-specific execution surfaces, adapters, and ecosystem integrations.

Enterprise Operators ​

Organizations operating private or hybrid execution domains with custom governance and settlement requirements.

6. Trust and Governance ​

Forge Pool treats governance as a structural requirement for economic trust.

Governance systems exist to preserve:

  • execution integrity
  • replay correctness
  • provider reliability
  • settlement integrity
  • ecosystem safety

Governance mechanisms may include:

  • provider qualification
  • trust weighting
  • replay validation
  • adapter governance
  • execution verification
  • anomaly detection
  • policy enforcement

The goal is not arbitrary restriction.

The goal is to ensure that ecosystem expansion does not weaken deterministic computation or enterprise trust.

7. Relationship to the Runtime ​

The economy layer is inseparable from the Forge runtime architecture.

Web Core ​

Defines:

  • public execution access
  • billing surfaces
  • ledger interfaces
  • policy enforcement
  • settlement coordination

Hub ​

Coordinates:

  • planning
  • shard decomposition
  • verification
  • aggregation
  • replay coordination

Agent Mesh ​

Executes distributed workloads and contributes attributable execution capacity.

Kernel Primitives ​

Provide reusable compute families whose execution becomes economically measurable through canonical accounting.

Adapters ​

Extend the economy outward into real-world systems while preserving canonical execution semantics.

8. Why This Exists ​

Traditional infrastructure billing models are typically based on:

  • machines
  • reserved capacity
  • regions
  • infrastructure ownership

Forge Pool instead models:

  • execution
  • verification
  • replay
  • attribution
  • contribution

This allows the runtime to scale across heterogeneous infrastructure while preserving consistent economic semantics.

The objective is not merely billing.

The objective is to make planetary-scale execution commercially usable, operationally trustworthy, and replay-compatible.

9. Long-Term Direction ​

The economic architecture is designed to support future expansion such as:

  • advanced replay accounting
  • marketplace-level settlement
  • provider certification
  • regulated execution domains
  • delegated enterprise settlement
  • hybrid execution economies
  • execution-class specialization

Future evolution will preserve deterministic accounting principles.

10. Summary ​

Forge Pool’s economy is designed as an execution-derived economic architecture.

It connects:

  • workloads
  • replay
  • accounting
  • providers
  • adapters
  • settlement
  • governance

into one coherent runtime model.

The result is an economic system that is:

  • usage-based
  • replay-compatible
  • auditable
  • provider-aware
  • enterprise-compatible
  • structurally tied to verified computation

Forge Pool does not treat economics as a detached business layer.

Economic truth emerges from execution itself.