OpenVibe.Run
You are looking at revision 1, not the published revision 2.
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
Without OV_OAUTH_CLIENT_SECRET Run cannot mint the Network token Bot requires, so the bridge is off and every job stays queued. openvibe.run is parked, answering a 302 to openvibe.network, until Run has a product surface.
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 5a8d998), retrieved
The job service of the network (openvibe.run).
- OpenVibe.Run STATUS.json (commit 5a8d998), 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)