FORGE / DEVELOPER PLATFORM

Nodes & runtime

Capability readiness is more than a heartbeat.

Preview documentation. Availability is explicit; no public API or MCP deployment is implied.

Eligibility

A compatible Node must have a fresh heartbeat, reported and approved capabilities, required provider authentication, capacity, placement policy and compatible journal/envelope contracts. Central remains the scheduling authority.

API access

The Developer API does not issue Node credentials and does not expose internal claim or Designer lease endpoints. Customer agents act as ordinary scoped users, never as internal Nodes or administrators.

State and recovery

Reuse existing Run ownership, fencing and journal mechanisms. Historical recovery failures are not waived by this preview. No historical campaign or ledger migration is part of Developer Platform.

Source: tools/developer-platform/portal/content.mjs · 0.1.0-preview