Remote machines and linking

Planned. RegesARC 0.0.1 does not provide device pairing, remote model routing, a relay, discovery or a RegesARC equivalent of LM Link. Its private local runtime is not a remote endpoint to expose directly.

Separate compute from control

A future remote workflow should identify the actual machine, serving artifact, runtime capabilities and instance owner. A local chat may request inference on another device, but that does not grant remote filesystem access, command execution or permission to stop shared services.

The interface should make location visible: where prompts are sent, where history is stored, which machine holds model weights, and which endpoint is trusted. A cloud/remote badge must not be confused with a local-only privacy promise.

Pairing and transport requirements

Use explicit device identity, authenticated pairing, scoped credentials, revocation and transport encryption. Publish trust and relay assumptions. Network discovery must not auto-trust an advertised service. Administrative keys remain separate from inference grants, and no key is embedded in a shareable URL or renderer bundle.

Test failure modes deliberately: sleeping devices, network loss, changing addresses, version mismatch, expired credentials, quota/capacity errors and interrupted streams. Reconnecting should not duplicate model loads or tool side effects.

Ownership and cancellation

Canceling a request should target its actual remote work. Disconnecting a client is not proof of canceled allocation. Stopping a private child on the local machine is different from stopping a shared service on another device. Every operation needs a defined owner and recovery policy.

Resource planning must use the remote machine’s captured availability, not the local GPU card. Return the effective model/context/placement and observed timings so users can assess what actually ran.

Reference and qualification

LM Link documentation is a reference for LM Studio’s remote-workload feature. RegesARC has no affiliation or completed interoperability claim.

The atlas’s Remote Machines page is a design study. Release requires a real protocol, authenticated pairing, least-privilege policy, transport tests, restart recovery, remote load/generation/Stop/unload evidence and explicit user-visible data routing. It should not be implemented by opening a private administrative port to the internet.