Guides
Work across machines
Coordinate reservations and inspect shared snapshots without transferring credentials.
Joining is an explicit operation
The shared factory uses remote state branches for reservations and machine snapshots. Membership belongs to the machine, not the project: ork fabrica entrar publishes the first snapshot; run it only when participation is authorized. The team’s request in orkastery.yaml (fabrica.compartilhada: true) does not turn publishing on: the manifest comes with the repository, and only the machine decides to publish its snapshot. Each machine performs its own runtime login.
fabrica.remoto is the name of a git remote already configured in the clone, not a URL: only letters, digits, dot, underscore and hyphen, no leading hyphen, no .. and up to 64 characters. The same applies to --remoto in ork fabrica, ork roadmap, ork ship registrar-pr, ork ci status and ork ship --para. Outside that format, the value never reaches git: the refusal is typed (fabrica.remoto-invalido, roadmap.remoto-invalido, ship.remoto-invalido or ci.remoto-invalido) and shows the redacted value. For another server, create the remote with git remote add and put its name in the manifest.
Inspect before taking work
Reservations prevent two machines from taking the same item. Offline, inspect the last copy and consider its timestamp. The public snapshot excludes prompts, transcripts, credentials and local paths. Pending decisions must be answered through the responsible machine’s authenticated ingress.
ork board --sem-remoto
ork fabrica --sem-remotoA person’s network: Orkastery Network
The shared factory lives on one project’s remote. The network brings together one person’s machines, across all projects, in a private repository of theirs on the forge, <user>/orkastery-network. ork network entrar creates the home when it is missing, publishes the first snapshot and only then records membership; after that, the machine publishes on its own at the pulse heartbeat and on thread events. Identity comes from the already authenticated gh or glab; ork never reads a token. A machine that already ran ork fabrica entrar is a member without redoing anything.
The home receives the name, hostname, forge and login, runtimes and hosts with their version, projects with a credential-free remote, and the last heartbeat. It never receives a token, password, account email, paid plan, credential file path, prompt, transcript or log. Publishing requires a private home, checked on the forge, and HTTPS only.
ork doctor has a rede line: membership, home, last heartbeat and last failure from rede.log. It only reads local files and never blocks; it becomes a warning when the failure is newer than the heartbeat or when the heartbeat is older than 3 hours. The home’s REDE.md lists machines with a heartbeat in the last 14 days; those stopped for longer go to the footer and to ork network status. The network was released in version 0.5.3.
ork network entrar --maquina pc-casa
ork network status
ork network publicar
ork network sairThe network roadmap, from any directory
ork network roadmap combines the roadmap’s status report, reservations and each machine’s threads, with the source and time of every part. It runs from any directory, even outside a clone. The roadmap comes from the remote base, the same for every machine; this machine contributes its local state, and the others their published snapshots.
Without a clone, it reads through the forge CLI you have already authenticated, gh or glab, using queries only; no token leaves it. Anything not read appears as a typed gap with the next step: a machine without a heartbeat for more than 3 h, a forge without login, no network. The answer never says empty because it did not read.
The person’s network also enters the overview, in the Network by person section: the home and each machine, with its heartbeat and the projects it declares. A project declared only by a network machine can be requested by name, without a clone or registration here, and a network machine that has not published to the project’s factory appears with unread threads (gap maquina.sem-fabrica), never with zero active. ORK_REDE_LER=0 turns this reading off.
ork network roadmap
ork network roadmap --projeto github:orkastery/orkastery
ork network roadmap --projeto meu-produto --json