OpenVibe.Run
Imported, written with AI assistance. Imported from the OpenVibe repository README and STATUS files at the cited commits, summarised with AI assistance; originally by OpenVibers. Not yet reviewed by a person.
OpenVibe.Run is the job service of the network, served at openvibe.run on port 4920. It accepts jobs, places each one on a node that advertises the runtime class it needs, and follows it to its end.
What it does
A job belongs to a project, is billed per wall-clock second it runs, and is visible only to the token that project presents. Submit (POST /api/v1/jobs, capability run.job.submit) validates against a released contract, mints a job_<ULID> id, stores the row queued and writes run.job.queued in the same transaction. A poller places the job from the Fabric's offers using openvibe-sdk/placement, sends it to OpenVibe.Bot, mirrors Bot's state and the node's stdout back, and settles it. /api/v1/jobs/:id/stream replays and follows a job's output as a server-sent event stream.
What it does not do yet
Run serves its own site at openvibe.run since 2026-10-11. First-party callers such as OpenVibe.Codes submit jobs on loopback. A hosted runner for untrusted code waits for a separate, isolated worker host.
How it fits the network
It verifies tokens issued by OpenVibe.Network and publishes run.job.* events to OpenVibe.Events. It owns no node link or per-second metering, which belong to OpenVibe.Bot, and it holds no Billing token.
Status
STATUS.json's stage is "alpha"; it is deployed on the host since 2026-10-07, with the job API reached by first-party callers on loopback.
Sources
- OpenVibe.Run README (commit 6eb9d77), retrieved
The job service of the network (openvibe.run).
- OpenVibe.Run STATUS.json (commit 6eb9d77), retrieved
unit openvibe-run.service on 127.0.0.1:4920 since 2026-10-07
Inspect these sources (retrieval times, where each was first cited, what changed between revisions)