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. ork fabrica entrar publishes the first snapshot; run it only when participation is authorized. Each machine performs its own runtime login.
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-remotoThe network roadmap, from any directory
ork network roadmap combines the roadmap 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.
ork network roadmap
ork network roadmap --projeto github:orkastery/orkastery
ork network roadmap --projeto meu-produto --json