Auto Secure Login · ASL rBroker · Help guide

Run the work.
Understand the resources.

rBroker is more than a monitoring screen. It includes a local GPU lease server, real CPU workers, signed fleet reporting and a shared fleet coordinator. You choose which parts run on each computer.

1. Choose how this computer operates

Mode	How it starts	After closing rBroker / signing out	Administrator needed?
Desktop hosting	Open Host & setup and start the components you want.	Keep rBroker open. Normal close checks for active local work; it must not silently kill busy GPU/CPU hosts. Signing out or shutting down can interrupt work.	No, for ordinary desktop use.
Always-running service	Install the optional service companion once and approve Windows. Selected components start automatically at boot.	Continues independently of the desktop and signed-in user. The machine must remain awake and powered on.	Yes, for service installation, configuration and management. Not for ordinary monitoring by an authorized user.
Connect to an existing service	Use its local connection and authorized client configuration.	The independently managed service keeps its own lifecycle.	rBroker does not elevate to take it over.

Installing or opening the desktop alone does not start all the servers. Version 1.1.0 requires explicit desktop starts. Version 1.2.0 adds an explicit service-install option; service mode is never enabled without approval. Installing service mode does not convert, stop or import an existing broker automatically.

A computer normally needs its own local CPU/GPU services only if it will execute that work. A fleet normally needs one reachable coordinator, not a separate coordinator on every computer. Viewing a fleet is not the same as joining it, and joining is not the same as starting reporting.

2. What runs where?

Component	Purpose	Default connection
Local GPU broker	Grants owned GPU-memory leases, checks safe capacity, tracks attachments/heartbeats and protects admission. It does not render or train a model by itself.	`127.0.0.1:28793`, local computer only.
ASL Parallel Work	Executes registered CPU/I/O tasks through real worker processes under one shared worker-slot budget. Jobs declare owner, project and purpose.	`127.0.0.1:28792`, local computer only.
Fleet reporter	Sends signed, selected resource and work summaries from this computer to the chosen coordinator. A GPU is not required.	Outbound to your configured HTTPS server.
Fleet coordinator	Authenticates membership and collects signed reports so authorized viewers see computers across networks.	`127.0.0.1:28810` behind your trusted HTTPS reverse proxy.
Desktop interface and clients	Display resources, manage explicitly owned hosts, provide setup/help, and supply local workload integration commands.	Native Windows application; no Electron.

The local GPU broker is the admission authority. The fleet server's display is not a GPU grant. Installing rBroker also does not automatically make unrelated programs use its leases or turn their work into registered CPU jobs; those programs must integrate with the supplied client/API.

3. Requirements and permission boundaries

Native x64 Windows 10 build 19041 or later, or Windows 11. This is not a 32-bit, ARM-native or S-mode package. Minimum build targeting is not a promise that every Windows edition remains vendor-supported; current .NET support on Windows 10 is edition-specific.
Python, Node.js and the .NET runtime are included. You do not have to install them separately for bundled Windows hosting.
Fleet membership, system RAM/CPU reporting, CPU workers and coordinator hosting do not require an NVIDIA GPU.
Local GPU admission currently requires one supported NVIDIA GPU, an installed compatible driver, and usable telemetry. An AMD/Intel GPU is not automatically supported for GPU leases.
A private fleet needs a reachable coordinator, appropriate joining/viewing credentials and trusted HTTPS for other computers. A purchase does not supply your domain, server or an included paid hosting subscription.
Service mode uses the restricted Windows LocalService account with an ASL-specific service identity. It does not save your Windows password or run workloads as LocalSystem.
Normal use changes no firewall, router, driver, antivirus, certificate trust or Windows security setting. If a preview installer is blocked, record the exact message; do not weaken protection to force it through.

4. First setup: run inside the desktop

Install and open ASL rBroker. Choose Refresh now. A fresh computer may correctly show unavailable GPU/Parallel services until you start them.
For CPU work, open Host & setup, choose a modest worker limit such as 1–2 on a laptop, and select Start Parallel Work. Then run Run small CPU self-test. This processes four small JSON records using actual workers.
For GPU work on a supported machine, choose Detect GPU, review the physical capacity and single system allowance, and select Create and start private broker.
If either default/selected local port already belongs to a service, stop here for that component. Connect to the existing service with its authorized configuration; do not create a competing authority.
If using an existing fleet, follow Connect and join. Creating a local fleet server is optional and not required to connect to our hosted server.
Keep the app open while its hosted components are needed. On reopening the desktop, these manual components are not automatically started again.

Desktop Stop my idle broker and Stop my idle Parallel Work affect only children started by that desktop instance. An active lease or accepted CPU job prevents normal shutdown. Unexpected loss of the owning UI tells the surviving hosts to drain new admissions while existing work finishes. Forced process termination, power loss or Windows shutdown can still interrupt work.

5. Install the optional always-running service

In rBroker 1.2.0, go to Host & setup → Export Windows service installer. Save to a new ZIP filename. Export prepares files only; it does not install, start or elevate anything.
Use Windows Extract All. Do not run setup from inside the compressed folder. Inside the extracted folder, open service\RBroker.Service.exe. Keep the complete extracted bundle together.
Choose Administrator setup / management. Approve Windows if you want to proceed. Cancellation is respected; the app does not repeatedly reopen the prompt.
Choose the components this computer should run: Parallel Work, GPU broker, optional fleet coordinator, and optional fleet reporting. GPU is not selected merely because hardware exists.
Set the CPU worker limit. For a GPU, use Detect supported GPU and review the single allowance. Hardware is checked again by setup; a manually supplied capacity is not blindly trusted.
Optionally approve one specific local read-only file folder. Blank means JSON tasks only. This approval does not grant new Windows filesystem rights; the service identity must already be able to read the folder. Do not approve a whole drive, network share or mapped drive.
For unattended reporting to an existing fleet, check reporting and enter its trusted HTTPS origin, a joining-enabled fleet key and a computer name. Choose resource and work-label sharing. The key is used once for joining and is not stored. The service creates its own protected identity; it does not copy the desktop's identity.
Select Install selected components and start automatically. Setup validates the package and selected ports, creates protected versioned files, provisions private state, registers the service and requests start.
Choose Refresh service status, then check actual GPU/Parallel health in the desktop with Refresh now. A Windows service marked Running is a supervisor state, not proof that every component or every GPU counter is healthy.

What installation creates

Service name: ASLrBrokerHost; display name: ASL rBroker Background Host.
Versioned program files: C:\Program Files\ASL rBroker Service\1.2.0.0 on a normal Windows installation.
Protected machine state: C:\ProgramData\ASL-rBroker-Service. Windows may locate Program Files/ProgramData differently; the app uses the system's actual locations.
Administrator-writable configuration and code. The selected Windows operator has read/client access. The ASL-specific service identity can write runtime data/logs, not its program code or configuration.
Automatic boot startup and bounded Windows recovery attempts for supervisor failure. This is ordinary local service code, not an AI task or paid-model loop.

The service installer is a native companion. The Store package does not silently declare privileged packaged-service or elevation capabilities. Installing it is an explicit Windows administrator operation outside the MSIX; it is not proof Microsoft has certified the companion.

6. Use, configure, stop and remove service mode

Daily use

Once installed and running, you can close rBroker and the setup window. The service keeps its selected components running while the computer is awake. It starts without an interactive login at the next normal Windows boot. Sleep suspends execution/network availability; “always-running” does not override sleep, shutdown, power loss or an unavailable network.

Open Check Windows service status in the desktop. To manage it, choose Open installed service management folder, open RBroker.Service.exe, then approve Administrator setup. The normal monitor does not require an elevated desktop.

Change worker limits, components or reporting choices

Load existing saved service selections in its setup window.
Choose Drain and stop. Wait until Windows reports Stopped.
Change the explicit selections. Enter the joining-enabled fleet key again if reporting is selected; it was never saved. Keep the existing service operator/account.
Choose Apply selections to a stopped service and start it. Existing signing keys, local credentials and replay/lease state are preserved.
Refresh service and component status. If a settings update fails, startup is blocked by an incomplete-update marker until the intended settings are successfully reapplied. Do not remove the marker to bypass validation.

Stop safely

The service's stop command means drain: stop new GPU/CPU admissions and wait for accepted jobs/leases to finish. Windows may show Stopping while this happens. Check job owners rather than force-killing the service. A desktop idle-only stop and a service drain are different actions. The latter intentionally closes new admission while waiting.

Unexpected component exits are timestamped in the supervisor log and shown as degraded component state. The supervisor does not repeatedly recreate a failed GPU broker or scheduler over old work. Recovery checks ports and previous exact process identities; surviving children prevent a replacement. The original failure remains evidence, not something to clear by deleting the database.

Remove or restore registration

Choose Remove stopped service registration only after it is Stopped. This removes the Windows service registration and preserves versioned binaries and private state. It does not erase identities, credentials, lease/replay databases or logs. Uninstalling the desktop does not remove this independent service.

To restore the same preserved installation, choose Re-register preserved installation with its matching setup version. It verifies protected storage and package integrity and keeps existing keys/settings. This is not an automatic upgrade to different code. Retained files are explicitly preserved, not a promise of a disk-cleaning uninstall.

7. Connect and join a fleet

Get the coordinator's HTTPS address and an authorized fleet key from its operator. The hostname is configurable; an ASL address is optional.
Open Fleet, enter the address/key and Connect. A working view proves viewing permission, not joining permission.
Review the computer name and select Join fleet. The app sends a signed public identity. No private signing key is uploaded and no JSON copy/paste is required.
Joining registers membership only. On Connect this machine, choose what to share and select Start reporting for desktop-session reporting.
For service-mode reporting, use the service setup's reporting option instead. It owns a distinct identity and continues when the desktop closes. Do not start a second desktop reporter for the same computer unless you deliberately want separate entries.
Repeat on the other computers. They can be on different networks. Each node sends outbound HTTPS to the common server; no shared drive or same-subnet connection is required.

Join requires coordinator 0.5.0+ and explicit join permission on the connected key. New private servers give their creator key permission. Existing server operators can run node setup.mjs enable-join STATE_DIRECTORY FLEET_ID during a coordinator-only maintenance stop. Later authorized joins do not require a restart. Existing GPU work does not need to be stopped for joining.

Manual public JSON export/import remains available. It is an alternative onboarding mechanism, not a replacement for Start reporting. A normal instance supports up to 32 enrolled identities. Repeated Join for the same identity is idempotent; reinstalling or inventing a new identity to clear an error can consume extra membership and confuse ownership.

If you switch from desktop to service reporting, the old desktop identity is not silently overwritten. Stop the old reporter and have the fleet operator disable/remove the old membership if appropriate. Old reports should become stale/offline; do not interpret them as newly running work.

8. Host your own fleet on LAN or the internet

You can explicitly host a coordinator in the desktop, select coordinator in the Windows service companion, or deploy the standalone Node.js source on Linux. For unattended Linux hosting, use the included installation guide and systemd template. The Windows app can export the standalone server source. A local-only coordinator can be evaluated without a domain; access from other computers requires proper HTTPS setup.

Choose one coordinator computer/server and preserve its private state directory.
Desktop mode: Create private server, Start server, then View my local fleet. Service mode: select coordinator during setup; it creates the private my-fleet configuration and viewer key.
Configure your own trusted certificate, DNS and HTTPS reverse proxy to the coordinator's loopback port 28810. The app does not make router/firewall changes for you.
Publish only /health, /v1/fleet, /v1/fleet/join and /v1/fleet/nodes/{nodeId}/sync. Join is POST with a 4096-byte limit. Preserve authorization/signature headers and do not cache private fleet responses.
Never expose GPU port 28793 or Parallel Work port 28792 to the LAN/internet. Remote reporting is not an arbitrary remote-execution interface.
Distribute the private fleet key securely to authorized people. Service coordinator key location: config\server\viewer-token.txt within the protected service state folder. Do not put it in URLs, screenshots, public pages or support logs.

To begin unattended reporting to a newly self-hosted coordinator, first establish its reachable HTTPS endpoint. Then load saved service selections, drain/stop, enable reporting with that endpoint/key and apply. Selected reporting remains opt-in.

9. Run CPU work through Parallel Work

Parallel Work is a real local scheduler, not merely a CPU graph. Start it in desktop mode or select it in service mode. Its registered handlers include a small JSON task lane and approved read-only file work. A GPU is not needed.

Start with a modest maximum worker count. The budget is shared across concurrent jobs; requesting eight workers in two jobs does not authorize sixteen workers.
Run the desktop small CPU self-test only against the desktop's own host. For a service-owned host, use the documented service configuration and local client below.
Have each project submit a registered task type and declare its project, purpose, owner and unique session ID. The scheduler records worker PID, process creation identity, parent, job and exit evidence.
Use an explicit approved local folder for file tasks. A path permission error is not a reason to grant whole-drive access.
Keep job receipts and poll the returned job ID for its terminal result. A caller timeout does not mean its accepted job never ran.

For a Store installation, the app provides the rbroker.exe execution alias. For the standalone preview, use the installed RBroker.exe path. Save GPU and Parallel consumer instructions from the desktop for the desktop mode's paths. For service mode, replace the configuration path:

rbroker.exe --parallel-client "C:\ProgramData\ASL-rBroker-Service\config\parallel\config.json" GET /health

rbroker.exe --parallel-client "C:\ProgramData\ASL-rBroker-Service\config\parallel\config.json" GET /v1/activity

To submit work, invoke POST /v1/jobs with this JSON on standard input. Use your language's process API or an equivalent shell pipe; credentials are read locally, not inserted into the command line.

{
  "taskType": "core.sha256-json",
  "workers": 1,
  "items": [{"id": "example-1", "payload": {"message": "small test"}}],
  "work": {
    "project": "my-project",
    "purpose": "Verify one small CPU task",
    "owner": "other",
    "sessionId": "my-unique-session-id"
  }
}

The supplied client restricts operations to documented registered routes. There is no generic shell-command task or arbitrary-code upload endpoint. To inspect capabilities, request GET /v1/capabilities. Workload/result data stays local; opted-in fleet activity shares descriptions and bounded status, not the input payloads.

10. Run a GPU workload with its own lease

A GPU lease is an owned reservation for a workload. A visible free-memory number, a fleet entry or another project's lease is not permission to use the GPU. Each integrated workload uses the official local client to obtain a fresh grant, attach its process and maintain heartbeats.

rbroker.exe --client --config "C:\ProgramData\ASL-rBroker-Service\config\gpu\config.json" launch --owner other --session-id UNIQUE_SESSION --label "Project: what this GPU job is doing" --requested-mib 4096 --minimum-mib 1024 -- PROGRAM ARGUMENTS

The example is for a service-owned broker. Use the desktop's exported configuration path for a desktop-owned broker, and your existing service's authorized client/configuration if that computer already has an independently installed broker. Do not copy another session's lease ID or capability.

Heartbeats use the server-confirmed expiry and leave time for the HTTP request. Authentication rejection is not a transient permission to keep working.
Capacity/admission failure must remain visible to the project. Reduce the request or wait for legitimate capacity; do not launch unleased work to “test” availability.
Processes may hold a lease while temporarily idle between model operations. Investigate the declared purpose, process identity and owner before treating idle utilization as abandonment.
Unknown/stale telemetry blocks new admission. A service running in Windows session 0 still needs usable driver/counter access. Supported GPU detection alone is not proof that all required telemetry works.
No automatic job migration, cross-machine pooled VRAM, model weights or renderer is supplied by rBroker itself.

11. Understand system RAM and GPU memory

System RAM is the computer's ordinary physical memory. It is separate from GPU VRAM. Resource reporting is not a system-wide RAM reservation or process memory limiter.
Physical GPU RAM is the card's actual dedicated memory. Used/free readings describe physical telemetry, not ownership.
System allowance is counted once to establish the broker-managed pool. Review it for the actual card; do not apply a 5 GiB allowance blindly to a smaller GPU.
Lease commitments are promises already made to jobs. A grant may exceed what that job has resident at a particular instant.
Available for a new lease is constrained by both remaining managed budget and physical free memory after accounting for outstanding promises. It is not simply total minus all displayed labels.
Windows allocation references can overlap. They are not necessarily exclusive VRAM and must not be added as a second system reserve.

Unknown is not zero. Missing GPU telemetry should not be shown as an empty card with all memory available. Fleet reports display last-known observations and their ages; only the local broker can make a current admission decision.

12. Refreshing, stale data and background activity

Refresh now is manual. Active monitor enables a two-second refresh while the desktop is open; it is off by default. Displayed records continue aging so a stopped connection does not look permanently current.

The service and optional reporter have their own ordinary operating loops. Turning off Active monitor does not stop a service, disable jobs or stop an explicitly enabled reporter. Closing a viewer does not cancel someone else's lease. No monitoring loop calls an AI model or schedules a Codex/Claude task.

A fresh fleet report and fresh GPU telemetry are different clocks. The computer can be online while GPU data is unknown. Once reports stop, remote cards become stale/offline; their old workload names are last-known information, not proof those processes still exist.

13. Windows accounts, folders and credentials

Desktop mode protects keys for the current Windows account. Service mode has a separate machine-protected identity and access-controlled storage. Machine DPAPI is combined with restricted filesystem permissions; it is not a reason to put encrypted credentials in a shared folder.

The service runs under LocalService plus its ASL service identity. It does not automatically see your mapped drives, authenticated network shares, private profile files or interactive environment. Approving a folder permits the registered handler to use it; it does not modify Windows ACLs. Start with a small local test folder already readable by the service account. Ask an administrator for narrowly scoped read permission when needed rather than granting broad write access.

The operator selected during initial setup can read service client configuration and protected credentials. Other Windows accounts do not gain access just because they can view public health. Do not run the entire desktop as administrator as a substitute for setting proper client permissions. Changing the designated operator is an explicit administrative recovery task, not an automatic user switch.

For detailed activity from an existing service, select its authorized protected Parallel credential in the desktop. Public worker health is available without it. A fleet viewer key, fleet joining permission, local GPU bearer credential and a private per-lease capability are different permissions.

14. Troubleshooting by symptom

What you see	What it means / what to do
GPU or Parallel unavailable on first launch	The app may be open without a host running. Start the desired desktop component or check the installed service. A GPU is optional for fleet/CPU functions.
Port already managed / competing scheduler refused	An existing listener owns the default/selected port. Do not stop it blindly. Connect to its authorized service or leave that component unselected in setup.
Windows service Running, component unavailable	Running identifies the native supervisor. Check actual component health and timestamped supervisor stdout/stderr for startup failure or a later exit.
401 / authentication required	Wrong credential, wrong scope/account, revoked permission or invalid proof. Use the right credential for this endpoint. Never borrow a lease or treat rejected authentication as permission to continue.
Join denied / 403	The key may be viewer-only, joining disabled or that node disabled. The fleet operator must authorize joining. Reinstalling is not the fix.
Join route not found / 404	Verify coordinator 0.5.0+ and the reverse proxy's exact Join route. Manual public-record enrollment remains available.
409 on enrollment	Check identity collision, maximum memberships, computer clock and server response. Preserve existing keys. Do not generate repeated new identities.
429 or no worker/GPU capacity	A shared budget is exhausted, admission is draining, or a rate limit applies. Respect it, inspect active owners and retry only as the documented client permits.
503 / persistence or mutation trouble	The authority cannot safely complete the request. Keep failure evidence and inspect timestamped service/storage logs. Read-only health success alone does not prove mutation paths work. Do not delete the database.
Service Stopping for a long time	Accepted jobs/leases may still be draining. Inspect their owners and current state. Do not kill processes or delete leases just to make the status turn green.
Incomplete configuration update	The service deliberately blocks startup after an interrupted/failed settings update. Correct the intended selections/authorization and reapply while stopped. Do not remove the safety marker by hand.
Folder access denied	Check both the approved folder list and Windows permissions for the service identity. A mapped user drive may not exist in service session 0.
Installed but missing from fleet	Installation, Connect, Join and Start reporting are separate. Verify the correct identity is enrolled, reporting is enabled and HTTPS/clock/permissions work.
Two entries for one computer	Desktop and service identities are intentionally distinct. Stop the unwanted reporter and have the fleet operator handle old membership; do not overwrite either private key.
Administrator approval canceled	No repeated prompt is created. Return to service setup and approve explicitly when ready. A canceled operation is not an installed service.

Where the error evidence is

Desktop Diagnostics & help displays occurrence times and guidance. Its private diagnostics preserve child start identity, stdout/stderr and exits. Service supervisor events are in data\supervisor.log beneath the service state directory, with a bounded previous log. Component logs and ownership journals are under the corresponding data subfolders. Service component state is also recorded in data\status.json; it is a last-written record, not a live health promise.

Native setup errors are timestamped in the approving account's Local AppData folder under ASL\rBrokerServiceSetup\setup.log. The setup window displays the path. Windows Service Control Manager events can help identify startup/account failures before a child starts. Do not post whole private directories or raw credentials when seeking help.

15. Recovery, updates and backups

Identify which installation owns the work: existing shared service, desktop host or new service companion. Record the version and error time.
Check current lease/job ownership before disruptive actions. Public free memory does not justify deleting another process's reservation.
For an installed companion, drain/stop before applying settings or changing its registered code. Let accepted work finish; do not bypass the drain with a forced kill.
Keep configuration, identity, encryption material and replay/sequence state together. Do not restore an old replay database during a routine code rollback.
A failed first setup retains evidence. Re-run the exact matching bundle with the same intended selections to resume an incomplete provisioning step. If package integrity differs, stop and get the matching intact bundle; do not overwrite it with unrelated files.
A completed, removed service can be re-registered from its verified preserved installation. Different-version upgrades require an explicitly tested maintenance procedure; the desktop does not silently update an independent running service.
Repairing a desktop installation does not migrate or delete the service's state. Removing the service registration does not erase the retained state or program files.

Do not use a backup of encrypted files without its matching key or assume a DPAPI identity is portable to another machine. Backups and screenshots containing private fleet information need the same access restrictions as the live state.

16. What is shared, and what is not?

Before explicitly starting a reporter, no fleet telemetry is published. Joining sends the public computer/key identifiers, public signing key, selected display name and proof of possession to the selected coordinator. Private signing keys remain local. The coordinator stores membership in an encrypted ledger.

Opted-in reports contain computer identity, health, lease grants/owners/session IDs, worker activity and selected resource/work descriptions. They do not include prompts, model files, job input/results, environment variables, process command lines, local filesystem paths or local GPU bearer credentials. Labels are supplied by projects: do not place secrets or customer records in them.

The coordinator operator controls access, retention and backups. Removing an identity/report does not erase every operator backup. Exported desktop diagnostic summaries intentionally omit private paths and credentials; the private logs contain more detail and need review before sharing.

The desktop/service do not include advertising, AI-model calls, automatic cleanup, pooled cross-computer VRAM, automatic job migration, arbitrary remote command execution, fan control or driver installation. Ordinary machine/service operation consumes local CPU/RAM and network traffic, not AI tokens. Microsoft, Windows and other software apply their own policies.

17. Check that your installation really works

Confirm the installed version. Do not expect the 1.2 service feature in a 1.1 app.
Desktop mode: verify manual startup, one small CPU task, displayed status and safe idle stop.
Service mode: verify Windows reports the intended service/account/start type, check each selected component, close the desktop and confirm the service remains running.
Confirm only the intended components own the local ports. Do not intentionally start a second GPU broker or scheduler.
For fleet reporting, check the specific service/desktop identity becomes online with real resource data. Then stop its reporter/service safely and verify the card ages to stale/offline.
Submit one tiny registered CPU job before a heavy workload. Keep its receipt and owner/session details.
Only test GPU admission through an owned official-client lease, on supported hardware with fresh telemetry.
Do not reboot a busy shared machine just to test boot startup. Schedule that physical acceptance when its users/workloads allow it. Unit/package tests do not replace this real-machine check.

Windows 11 OMEN tests, Windows 10 laptop tests, service session-0 tests, package validation and Microsoft Store certification are separate acceptance gates. A successful install or Store upload must not be described as proof all these gates passed.

18. Support and source references

Contact support@autosecurelogin.com. Include app/service version, Windows edition/build, hosting mode, component, exact error time and a safe summary. Describe whether work is still active. Do not include viewer/joining keys, private signing files, bearer tokens or whole private state folders.

Get help without exposing your fleet

Use the subject ASL rBroker — brief description of the problem. Tell us the result you wanted and the result you actually saw. For example: “This laptop joined successfully at 14:10 MDT, but its fleet card still says offline after Start reporting.” That is more useful than “it does not work,” and it helps distinguish enrollment, reporting and local execution.

Open Diagnostics & help. Note the displayed app version and, if applicable, the separately installed service version. An updated desktop can coexist with an older companion; report both.
Record the exact error wording and occurrence time, including timezone. Say whether it happened once, after every start, or only while other work was running. Describe when it last worked.
Use Save safe diagnostic summary before closing the app. This session history is not a permanent system-wide incident log. Review the exported file before attaching it.
If sharing a screenshot, crop to the relevant error. Hide names or work labels you consider private, and keep fleet keys, paths and unrelated windows out of the image.
Say whether an active job, GPU lease or independent service is still running. Support must know this before suggesting a stop, repair or configuration change.

You can copy this checklist into your email and fill in only the fields that apply:

Product: ASL rBroker
Desktop version / service version:
Windows edition, build and x64 architecture:
Mode: desktop hosting / Windows service / existing service / viewer only
Component: GPU / Parallel Work / reporting / coordinator / desktop
What I expected:
What happened, including exact error text:
First occurrence / most recent occurrence and timezone:
Last known successful action:
Steps that reproduce it:
Active work that must not be interrupted:
Safe diagnostic summary attached: yes / no

Never email a fleet/viewer key, local bearer token, private signing key, encrypted credential file, whole ProgramData/LocalState folder, database backup, full process command line, customer files or AI prompts. Encrypted files are still sensitive. The ordinary support workflow does not require your Windows password, payment-card details or permission to disable antivirus. If more detailed logs are needed, agree on a narrow, reviewed excerpt first.

For problems with a customer-operated fleet's permissions or server availability, contact that fleet's administrator as well. ASL support does not automatically have access to another operator's server or the authority to release their jobs. For a Microsoft Store purchase or payment issue, use Microsoft's purchase support; do not include payment information in technical logs. No response-time or round-the-clock support guarantee is implied by this guide.

Product: rbroker.autosecurelogin.com. This guide is included offline and can be printed. Runtime licenses are included beside it.

19. Your first ten minutes: make one thing work

A new installation is intentionally quiet. The main window is a control panel, not a promise that every optional component is running. Start with the smallest useful setup, confirm its result, then add the next part. You do not need a server on the internet, a GPU or a second computer for the first CPU check.

Path A: this computer will do local CPU work

Open rBroker and leave Active monitor off initially. Select Refresh now. System RAM should become a real reading; missing local services should be identified as unavailable, not fabricated as healthy.
Open Host & setup. Set Maximum concurrent worker slots to 1 or 2. This is a starting point for a light test, not a claim that your hardware can safely run every task at that concurrency.
Choose Start Parallel Work. If rBroker says a scheduler already exists, use that installation's authorized client instead of trying other ports to create another budget.
Choose Run small CPU self-test. This uses real local workers on four tiny records. It does not benchmark a model, open your files or allocate GPU memory.
Refresh the local view and check the worker health. After the test completes, an idle count is expected. Save the consumer instructions if you will connect a project. Stop the idle app-owned worker host when finished if you do not want it running.

Path B: this computer will only view an existing fleet

Get the HTTPS address and viewer key from your fleet administrator. Open Fleet, enter them and choose Connect / refresh fleet. You can stop here. Viewing does not require creating a computer identity, joining, starting GPU/CPU hosts or sharing this computer's data. Disconnect forgets the viewer key held by this window; it does not unenroll computers.

Path C: this computer should appear in a fleet

Complete Connect, then Join fleet, then choose sharing options and Start reporting. Each step has a different purpose. A successful Join without a running reporter can leave an enrolled computer offline. A reporter without a local GPU broker can still publish independent computer presence and opted-in system RAM/CPU information.

What success looks like

For local CPU work, success means an accepted job reaches a terminal result and the workers are healthy afterward. For fleet reporting, success means the correct named identity has a recent report on the intended server. For GPU work, success requires an owned lease and a correctly supervised workload; a green health card alone is insufficient. Do not add heavyweight training, rendering or file scans until the relevant small check succeeds.

20. Two computers, one fleet: a complete walkthrough

Imagine a home workstation and a laptop at another address. The workstation may have an NVIDIA GPU; the laptop may have no supported GPU. They can belong to the same fleet because both contact the same reachable HTTPS coordinator. They do not need a shared drive, VPN, matching Windows account or inbound connection to each other's GPU/CPU ports.

Step 1 — establish the shared destination

Use an existing authorized fleet or host one using the server instructions. The operator supplies an address such as https://fleet.example.com and a joining-enabled key. The example is a placeholder, not a working service. An ASL product purchase does not automatically create a private hosted fleet or give every buyer access to ASL's internal computers.

If the coordinator is on the workstation, its default 127.0.0.1:28810 address is not reachable from the laptop: loopback always means “this computer.” A trusted HTTPS reverse proxy and reachable name provide the shared address. An administrator must handle server publication separately; rBroker does not open router ports or weaken a firewall automatically.

Step 2 — join the workstation

In Fleet, connect using the supplied address/key. Set a recognizable name such as Home workstation and select Join fleet. Wait for a successful response. Then open Connect this machine, confirm the reporting destination, choose resource/work-label sharing and Start reporting. Return to Fleet and refresh. The named computer should appear with a recent report. No GPU lease should be created merely by joining.

Step 3 — join the laptop

Repeat with a different friendly name such as Travel laptop. Use the same fleet address and a key authorized for that fleet. The laptop creates its own private identity; do not copy the workstation's private files to it. If it has no supported GPU, an unavailable GPU section is normal. Resource sharing can still show system RAM and CPU, and local Parallel Work can still execute supported registered tasks.

Step 4 — prove you are seeing new reports

Refresh the fleet on either computer and inspect the report age for both identities. Stop only the laptop's reporter, leaving its local CPU host alone if needed. Its fleet information should age rather than remain permanently current. Start its reporter again and check that the same identity becomes current. Do not mistake an old workload label on a stale card for evidence that the job still exists.

Step 5 — choose execution separately

Start the local GPU broker only on an eligible, previously unmanaged GPU machine. Start Parallel Work on each machine that should accept local registered CPU jobs. Integrate each project on the computer where it actually runs. Joining a laptop does not cause a workstation's model to move to it or let a GPU-less laptop reserve the workstation's card through the fleet display.

Step 6 — make selected computers unattended, if needed

Service mode is useful on a machine expected to keep reporting or hosting when nobody is signed in. Install the optional companion deliberately and select only the components it should own. Do not install it on top of active desktop hosts. Coordinate a safe idle stop first, and recognize that the service reporter has its own identity. Keep the laptop in desktop mode if you prefer work to be explicitly started during each session. “Same fleet” does not require every member to use the same hosting mode.

21. Read the dashboard: worked examples

System RAM is not GPU RAM

A computer with 64 GiB of system RAM and a 16 GiB graphics card has two different memory resources. Free system RAM cannot simply be added to the card's VRAM lease budget. Windows “shared GPU memory” also must not be presented as extra dedicated card capacity. rBroker reports system memory; it does not impose a system-wide RAM quota on all applications.

MiB and GiB are binary units: 1 GiB is 1,024 MiB. An advertised decimal GB number can differ from Windows or driver readings without memory being missing. Compare like units and the same timestamp before diagnosing a discrepancy.

A single-allowance GPU example

This example uses made-up readings, not your current computer. Suppose physical GPU capacity is 32,768 MiB, the configured system allowance is 5,120 MiB, and active commitments total 8,192 MiB.

The managed pool is 32,768 − 5,120 = 27,648 MiB.
The remaining policy budget is 27,648 − 8,192 = 19,456 MiB.
Physical telemetry supplies a separate safety ceiling. If physical free memory is 18,000 MiB and outstanding promises not yet backed by physical use total 2,048 MiB, that ceiling is 18,000 − 2,048 = 15,952 MiB.
The new-lease amount cannot exceed the smaller ceiling: 15,952 MiB in this simplified example, assuming fresh consistent telemetry and all other admission checks pass.

The system allowance was used once, in step 1. It is not subtracted again from the already-free physical reading in step 3. Desktop allocation references are not another automatic reserve. Additional non-budget conditions, such as draining, exclusive access or unreliable telemetry, can still prevent a grant even when this arithmetic is positive.

Why a lease and utilization can disagree

A job may reserve 8 GiB, load a model using 6 GiB, briefly use little GPU compute while reading input, then resume. Its lease is a promise; GPU utilization is an instantaneous measurement. Neither low utilization nor unused portions of a valid grant authorize another project to take the lease. Inspect the owner, attached process creation identity, label, heartbeat and expiry together. PIDs alone can be reused after a process exits.

Worker slots are not CPU percentages

Four worker slots means at most four scheduler-controlled worker slots are budgeted together. It does not mean the entire PC is restricted to 4% or four cores, and unrelated software can still use CPU, RAM and storage. Heavy disk tasks may saturate an external drive with fewer workers. Start small and increase only after observing responsiveness, job completion and storage behavior.

Online, healthy, idle and current are different

Online refers to recent contact. Healthy refers to a component's reported checks. Idle means no reported active work at that observation. Current means the observation has not aged beyond its freshness rules. A computer can report online while its GPU broker is unhealthy, or a healthy worker service can be idle. A previously healthy card can become stale without a new error response ever arriving.

22. Connect a project or AI coding tool correctly

rBroker does not read an AI conversation and automatically discover the purpose of its processes. The integration must declare that information. Use Save GPU and Parallel consumer instructions for an app-owned installation, or the authorized service configuration in the CPU and GPU examples. Confirm which installation owns the local ports before handing configuration to a project.

Give a project these non-secret instructions

The local hosting mode and authorized configuration location on that same computer. A path on one PC is not proof the same path exists on another.
A readable project name, a specific purpose such as “Generate product turntable preview,” the appropriate owner category, and a unique session identifier.
The amount of GPU memory genuinely required, or the number of Parallel workers appropriate for the registered task.
The requirement to keep receipts, handle rejected admission visibly, supervise heartbeats and release only its own lease.
The approved local input folder when using registered file handlers, without granting broad drive access.

Do not paste private bearer tokens, per-lease capabilities or fleet keys into prompts, repository documentation or command histories. A correctly authorized local client reads its protected credential itself. The viewer key used to see a fleet is not a substitute for the GPU client's credential.

GPU client parameters are a contract

requested-mib expresses the desired grant; minimum-mib must be an amount the workload can actually run within. Do not copy the example's smaller minimum into a model launcher that cannot adapt to a smaller grant. If the program always needs 4,096 MiB, request a compatible minimum rather than accepting 1,024 MiB and exceeding it. rBroker coordinates participating programs; it is not a driver-level memory sandbox that makes arbitrary over-allocation impossible.

The supervised launch must wrap the real long-lived workload, not only a shell that immediately starts an unrelated detached GPU process and exits. The integration needs a reliable relationship between the lease owner, supervisor and actual workload process. A project that bypasses this relationship can produce misleading ownership or an early release.

CPU task lifecycle

Submit the supported task type and work metadata, retain the returned job ID, and use the documented status/result routes until the job reaches a terminal state. A network or caller timeout does not prove that no job was accepted. Check the existing receipt before blindly resubmitting the same work. Job inputs/results stay local; sharing work descriptions does not upload them to the fleet server.

What another AI task is allowed to infer

A successful status request means that request worked. It is not proof that an authenticated lease request will succeed. A fleet report shows last-known information, not remote execution permission. An idle-looking GPU does not authorize a shared-service restart, database deletion or another project's lease release. Report the exact rejected operation and time to the local operator instead of bypassing the authority.

23. Troubleshoot in the right order

First identify the layer that failed. Checking in this order avoids reinstalling an extension, changing a firewall or restarting a shared service when the actual problem is a missing host, wrong credential or stale view.

1 — is the expected local component running?

Refresh the local page. If this is a new desktop installation, check Host & setup for an explicit start result. If service mode is installed, check Windows service status and the health of each selected component. If only the coordinator was selected, unavailable local GPU/Parallel ports are expected. If an independent service owns those ports, record its identity and use its supported configuration; rBroker's app-owned stop buttons must not take it over.

2 — does the failure affect viewing, joining or reporting?

If Fleet cannot Connect, first check the configured HTTPS address and authorized viewer key. If Connect works but Join fails, inspect joining permission and the server's Join response. If Join works but the computer stays offline, check Start reporting, the reporting address, identity and sharing selections. These are separate operations with separate evidence. Repeatedly creating a new identity is not a connectivity repair.

3 — is the clock and HTTPS path trustworthy?

Signed requests depend on reasonable computer clocks. Check Windows date, time and timezone on both endpoints if reports are rejected around a time change. An HTTPS certificate warning is a server-name, certificate or trust problem to fix with the operator; do not disable validation. A company proxy, captive portal or unstable Wi-Fi can interrupt reporting even while a local worker continues normally. Test the exact configured destination, not an unrelated public homepage.

4 — what did the specific request return?

For 401, stop treating the credential as valid; verify endpoint, account and credential scope. For 403, have the operator check authorization. For 429, respect the stated rate, capacity or drain restriction. For 503, record the service's storage/mutation evidence and time. A successful read-only health call does not cancel a failed write-path result. Preserve the error before performing a maintenance action.

5 — is this a reporting problem or a workload problem?

If local job receipts and leases are healthy but a fleet card is stale, investigate the reporter/coordinator path without restarting working CPU/GPU hosts. If the local authority is rejecting heartbeats or admission, a green remote card from earlier is not evidence of recovery. Both failures can happen together, but the evidence must identify which request failed and where.

When to stop troubleshooting and contact support

Stop before deleting a database, rotating keys, changing broad folder permissions, killing unknown PIDs or restarting a shared authority with accepted work. Use the support checklist and email support@autosecurelogin.com. Include the earliest useful error and latest recurrence, not just the newest secondary failure. Never deliberately reproduce a system crash or GPU out-of-memory event to collect a screenshot.

24. Daily operation and planned maintenance

At the beginning of work

Confirm the intended computer, installed version and hosting mode. Refresh status, inspect current owners, and check the age of fleet reports. Start only components that are not already managed. Confirm the application you are about to run is using its own integration and identity. If the PC feels slow, compare system RAM, CPU/worker activity and storage activity separately; GPU free memory alone does not explain whole-PC responsiveness.

Before closing or signing out

In desktop mode, keep the owning app open while its work is needed. A refused close is telling you work still depends on it. In service mode, closing the viewer should not stop the independent service; check its actual status rather than assuming an open window is required. Signing out, sleep and a full Windows shutdown are different events. The service survives sign-out by design, but no software can continue executing on a powered-off computer.

Before changing the service configuration

Tell local workload owners that new admissions will stop, then use Drain and stop. Wait for Stopped and preserve relevant job receipts. Change only intended selections and reapply. A failed reporting Join can leave an incomplete-update guard; fix the cause and reapply rather than removing that marker. The setup requires the joining key again because it does not save that shared secret.

Before installing a newer desktop or companion

Save the diagnostic summary first, then close the desktop normally when its owned work permits. A desktop update does not automatically replace a separately installed service. Record both versions and follow the release's service upgrade instructions. Do not copy new executables over the currently running Program Files installation or restore an older replay ledger to make a version change appear successful.

After maintenance

Verify the selected components individually, run a tiny permitted CPU job if appropriate, and confirm signed reporting uses the expected identity. Check that admission has reopened before asking projects to resume. Keep the prior release and protected evidence until the new version's relevant acceptance checks pass. A Store certification result, a unit test and a real boot-cycle check prove different things; none should be silently substituted for another.

25. Frequently asked questions

Is this just a monitor?

No. The Windows package includes local GPU admission, real CPU workers and optional coordinator/reporting components. They run when explicitly started in desktop mode or when explicitly selected in an installed service. A viewer-only setup is also supported.

Do I need to leave a terminal or a separate server window open?

Not for app-owned hosting: rBroker owns those background processes, and its desktop window remains the session owner. For the optional installed Windows service, neither the rBroker window nor a terminal needs to stay open. An independently installed older broker still has its own lifecycle until deliberately migrated.

Must I run the whole app as administrator?

No. Normal monitoring, viewing and desktop hosting use ordinary user permissions. Installing or managing the optional machine service requires explicit administrator approval. Running the entire app elevated does not repair wrong credentials or missing folder permissions.

Does joining start GPU or CPU jobs?

No. Join registers a signed public computer identity. Reporting is a separate opt-in action. Jobs are submitted separately by integrated local projects. Joining does not give the fleet server a remote shell or permission to steal another lease.

Can every computer use my 32 GiB card at once?

Membership does not pool or remotely export VRAM. Work using that card must run on its computer and obtain its own local grant. Concurrent local workloads may be admitted when the broker's current constraints permit; the fleet screen itself never grants capacity.

Why does an inactive project still have a lease?

A valid supervised workload can be temporarily idle, and a failed cleanup may also leave evidence that needs investigation. Check the exact process identity, last heartbeat, expiry and owner before deciding. Do not release it solely because utilization is low. The owning integration is responsible for correct release on completion.

Does turning off Active monitor save AI tokens?

There are no AI-model calls in that timer. Turning it off reduces dashboard refresh activity; it does not stop selected service components, reporter loops or jobs. rBroker itself does not create recurring Codex or Claude tasks.

Where is the fleet key, and can support give me one?

The fleet operator controls its keys. For a coordinator you created in the desktop, use the explicitly labeled private key control. The service coordinator's protected key location is documented above. There is no universal public key for all customers, and ASL support cannot issue access to a private third-party fleet.

Will it work with AMD, Intel or no GPU?

The core fleet and CPU features do not require NVIDIA hardware. The bundled GPU admission path currently requires one supported NVIDIA card and usable driver telemetry. Viewing an existing supported legacy broker does not add native admission support for a different GPU vendor.

Will uninstalling erase all my information?

Service removal deliberately retains protected state and files, and uninstalling the desktop does not remove its independent service. Server backups and reports are controlled by the coordinator operator. Consult the privacy/recovery sections before deciding what to retain or delete; removal is not advertised as a secure erasure tool.

Can I use it without internet access?

Offline help and authorized local GPU/CPU work do not require a cloud AI service. Fleet viewing/reporting requires access to the selected coordinator, which can be on a properly configured local network. Internet loss can make a remote fleet stale without proving local jobs stopped. Microsoft Store installation/licensing and external support follow their own connectivity requirements.

26. Plain-language glossary

Broker / admission authority: The local service that decides whether a new GPU memory promise can safely be made. It does not perform the rendering itself.
Lease: A time-limited, owned reservation. Its owner must maintain the required heartbeat and release it when the workload ends.
Heartbeat: A periodic request confirming that a lease owner is still present. Fleet reports also occur periodically, but a fleet report is not a GPU lease heartbeat.
Coordinator / fleet server: The shared destination that authenticates membership and collects signed computer summaries. It can be customer-hosted and need not run on every fleet member.
Reporter / publisher: The selected local component that sends this computer's signed summary to its configured server.
Node / identity: A registered reporting identity with its own key. Friendly names are labels; copying a name does not copy ownership. Desktop and service reporters have distinct identities.
Viewer key / joining permission: A secret that authorizes fleet viewing; the operator must separately enable its ability to enroll computers. It is not a local GPU token.
Loopback / localhost: An address that reaches only the computer making the request. Another computer's localhost is not your workstation.
Worker slot: A unit in Parallel Work's shared concurrency budget, not a whole-machine CPU or RAM limit.
Drain: Stop accepting new work while waiting for previously accepted jobs or leases to finish. This can take time without the program being frozen.
LocalService / session 0: The restricted Windows account and non-interactive session used by the companion. Your signed-in desktop and mapped drives are not automatically available there.
Fail closed: Refuse a new grant or unauthorized operation when safety or ownership cannot be verified, instead of guessing that it is safe.
Replay state: The record that prevents an old signed report from being accepted as new. Rolling it back independently of keys and other state can compromise that protection.
MSIX / service companion: The Windows desktop app package / a separately installed native Windows service. Updating one does not automatically update the other.

Still unsure which term or step applies? Email support@autosecurelogin.com with the exact screen and the result you want. You do not need to know the internal component names to ask for help.

28. Preview: receive described CPU work and recover it safely

What must already be connected?

The computer must be enrolled under its own protected identity, reporting a current snapshot, and connected to the intended fleet. Its local consent must be confirmed, and the fleet owner must grant the named dispatcher compatible limits. The owner must explicitly enable the optional job ledger using enable-job-delivery on a stopped, supported coordinator; see the source job-delivery guide. The proxy must allow the authenticated dispatcher offer/read/cancel routes and signed node poll/read/check/claim/settle routes under /v1/fleet/. Never expose the local worker or GPU ports to the internet.

Start only this app's own Parallel Work host explicitly. This preview refuses older workers that cannot retain the full work description. It does not borrow another account's credentials or take over an existing machine service. If another authority is already running, preserve its current work; do not start a competing scheduler just to test this preview. The dispatcher must use the typed API and separate dispatcher credential. The native screen receives offers; it is not yet an AI Hub project planner.

Read the task before you start it

On the Fleet page, select Read fleet offers. This is a one-time read, not an automatic execution loop. Choose the task and inspect its title, project, purpose, stage and expected result. A session number is only a secondary reference; it cannot replace the description.
Select Claim selected offer. The app saves the exact pending claim before sending its signed request. A claim reserves ownership of this attempt, not GPU memory or CPU threads. If the reply is lost, use Read saved local work and Retry saved claim. The original attempt is reused; a new competing owner is not created.
Select Start selected CPU work. The app checks current ownership, consent, dispatcher permission, installed handler support and currently available system RAM. It then commits its local submission record before the single request to Parallel Work. The canonical worker still controls the shared CPU worker budget. RAM is only checked at that moment; this is not a reserved-memory guarantee or a hard per-process cap.
Select Read progress / save result. The app reads only the saved local job ID. Once the worker is terminal and its allocated worker count is zero, the app checks the expected item IDs, counts and echo/hash results, then encrypts the result in the local recovery journal.
Select Send stopped receipt. Only stopped evidence allows the fleet ownership record to settle. A lost receipt response can be reconciled without running the job again. Its time is the coordinator's observation after the local result was saved; local worker timestamps remain in the private result record. A receipt digest is not a transferred file or assembled final deliverable.

Understand the saved state and the next safe action

State shown	What it means	What to do
Claim delivery unresolved	The claim may already belong to this attempt on the server.	Read saved local work and retry the saved claim. Do not create a different offer to sidestep it.
Claim saved—not started locally	Ownership is confirmed; no local submission has begun.	Start explicitly, or choose Skip before starting and send the not-started receipt.
Submission unresolved	The single worker submission began, but its reply or durable acknowledgement is missing. The worker might have run it.	Do not start again, skip it, erase the journal or clear the server slot. Preserve the recorded time and ownership logs for evidence-based recovery. A worker 404 after restart does not prove the work never ran. This preview deliberately offers no unsafe “force success” recovery button.
Worker accepted	A specific local worker job is saved.	Read progress. Cancel this local job requests cooperative cancellation only for that ID; already running chunks may finish.
Stopped result saved	The result or failure is recorded after the worker stopped.	Send the stopped receipt. This does not upload the result data.
Stopped receipt unresolved / confirmed	Delivery is uncertain / the server has confirmed settlement.	Retry only the receipt when unresolved. Confirmed history stays recorded; no silent deletion or re-execution occurs.

Block, disconnect, close and failure

Block new fleet work locally does not wait for the fleet network request. It changes the same local generation checked by submission. A submission already committed locally may finish; Block never kills another process or releases its lease. Disconnecting the viewer also does not prove that work stopped. Read the protected local records after reopening. Normal close waits for the bounded helper action; accepted worker jobs remain subject to the existing safe-close rules.

HTTP 401/403 means authentication was rejected, not permission to try another person's key. HTTP 409 requires ownership, policy or revision reconciliation. A timeout or service outage never triggers an automatic submission retry. Whole-response deadlines also cover a stalled body. A corrupt, inaccessible or full journal fails closed and preserves the existing data. The preview retains up to 64 local records and has no automatic cleanup that could erase replay evidence. Service-account onboarding, portable protected storage, retention/recovery tooling and real multi-machine GPU/media acceptance remain separate release work.

For help, email support@autosecurelogin.com. Include the app, coordinator and worker versions; readable task title; displayed state and last-recorded time; and the action you took. Never attach private input/result contents, keys, DPAPI files or the whole journal. Existing GPU jobs, fleet members and unrelated services should not be restarted as a troubleshooting shortcut.

29. Independent products, one described workflow

rBroker 1.3.0, coordinator 0.12.0 and canonical Parallel Work 0.2.3 are the tested source/candidate baseline for this section. An older deployed server can still supply a fleet view while refusing newer permissions, jobs or transfer routes. Check each actual version; do not assume the web guide installed an upgrade.

rBroker works by itself: start selected local hosts, run supported CPU work, admit integrated GPU clients, and operate or join a fleet. AI Hub adds readable multi-step planning, approval, dependencies and verified delivery. Steward adds diagnostics and explanations without granting resources. Master Suite embeds their native workspaces and engines in one separate product; it does not require the three standalone programs or launch their desktop windows.

Each product keeps its own protected profile. Installing Suite does not copy a standalone key or authorize a second broker. If the GPU or worker port already has an owner, connect to that authority and leave its jobs running. A viewer connection, fleet membership and execution permission are three different states.

Enroll each node with Join fleet; review its name and the information being shared. JSON export/import remains an optional administration path. Private signing keys stay local.
Configure the node's allowed dispatcher, supported handlers, resource ceilings and expiry. Approve compatible dispatcher permissions at the coordinator. Neither permission alone is sufficient.
In AI Hub or Suite, save and review a plan with a title, project, purpose, stage and expected result for every step. Select actual capable nodes and required input/output destinations. IDs are secondary correlation details, never the task description.
Approve that exact saved plan and advance it. The node executor checks current ownership and obtains local resources before doing work. A queued or claimed step is not an active GPU grant.
Read the stopped receipt and final delivery state. A renderer exiting successfully is not proof the file reached the chosen laptop folder.

The current registered handlers support bounded JSON work, hashing and the reviewed shape-animation/media path. They are not an unrestricted remote command facility or an automatic installation of arbitrary creative tools. A local media encoder is explicitly selected and checked; third-party tools, models and provider usage have separate availability and licensing requirements.

30. CPU slots, system RAM and GPU RAM

The canonical worker admits CPU slots and declared system RAM under one shared budget before accepting a managed job. It retains that commitment until the owned worker allocation stops. This is scheduling admission, not a claim to pin physical pages or constrain unrelated applications. New managed work refuses an older worker that cannot enforce the declared reservation. Older callers remain visibly unreserved rather than receiving a fabricated RAM guarantee.

GPU RAM is a separate graphics-card resource. Supported media work also obtains an owned, time-limited GPU lease and attaches the exact process identity. A task cannot borrow another session's lease. Reserved MiB, actually observed dedicated usage, Windows allocation references and system RAM must not be added together.

For example, the OMEN development card reports 32,607 MiB physical memory. One 5,120 MiB Windows allowance leaves a 27,487 MiB managed ceiling. That same allowance is not deducted again as a second physical-free buffer. Active commitments and any separately justified admission constraint are shown with their reasons. This is the OMEN policy, not a promise of a 28 GB grant on a smaller card or every customer installation.

Heartbeat retries must fit within the server-confirmed expiry, including the HTTP timeout. A 401/403 authentication rejection is not a temporary stall: stop the owned workload safely. Missing or inconsistent telemetry is unknown, not zero usage. Inspect ownership, process creation time and the latest measurement rather than releasing a seemingly idle PID's grant from another app.

31. Inputs, results and interrupted transfers

Approved workflow input and result data uses separate fleet/job/artifact-scoped authorization. The coordinator stores encrypted, bounded chunks; the receiver checks the complete digest before publishing the final file without silently replacing an existing destination. Resource admission does not authorize arbitrary file access.

When a connection breaks, reopen the original workflow and resume its original transfer. Confirmed chunks are reused. If a sender loses the acknowledgement, it asks for the original transfer's state rather than assuming the upload failed and rendering again. A partial output is not shown as a delivered final product.

A dependency becomes eligible only after its required predecessor output is verified. A laptop may receive the finished work from a GPU workstation even when they are on different networks: each computer contacts the configured HTTPS coordinator outbound. Keep local GPU/worker ports private.

Allow space on the coordinator and receiving node for pending content. A 256 KiB binary chunk expands to about 342 KiB in JSON/base64. The documented HTTPS proxy limit is 384 KiB, covering the application's 360 KiB request limit. HTTP 413 means the request exceeded a transport limit; it is not evidence of a bad GPU or stolen lease. Upgrade only the intended authenticated routes, not the whole server's authorization.

Unknown submission, damaged storage, identity drift and an unconfirmed stop remain visible recovery states. Preserve the original attempt and journal. Do not delete private state to turn an uncertain operation into an apparently empty queue. Terminal node history can be archived through the reviewed administration path; protected replay evidence remains. AI Hub's explicit workflow archive requires verified destinations and preserves output files.

32. Service upgrades and portable nodes

The optional Windows service runs selected components as LocalService, independently of an open desktop. It has its own identity, configuration and explicit CPU-only execution consent. It does not import the user's provider keys, enable a GPU-media executor automatically, or move interactive fan control into Windows Session 0.

Review the new package and preserve the existing service's private identity/configuration securely. A public enrollment JSON file alone is not a private-key backup.
Use Drain and stop on the service you own. Wait for accepted jobs and exact child processes to stop. Do not terminate other projects to make an upgrade test pass.
Run the newer service management companion and approve Windows when requested. The 1.2-to-1.3 transaction checks the stopped registration, process identity, protected paths and complete payload before switching versions.
The replacement remains stopped until its upgrade is verified. Existing selections and identities are retained; new components and executor permissions are not silently enabled.
If interrupted, retain the pending record and resume the intended transaction. Do not delete its marker, rotate identities or point an older writer at newer data. Refresh actual component health after the deliberate start.

Linux headless nodes use the same signed outbound protocol with protected owner-only profiles and Linux resource observations. They are not a Windows desktop running remotely. Real Linux/Windows cross-network CPU/RAM and transfer recovery have been exercised in release acceptance. A Windows-targeted build does not prove an offline Windows 10 laptop passed, and Apple scaffolding is not tested macOS support. Customer installation, permissions and hardware remain explicit checks.

33. Troubleshoot the failing layer

Viewer works, execution does not: verify the deployed coordinator supports jobs, the correct routes are enabled, the node reports freshly, and both local consent and named-dispatcher permission are current. Never replace a viewer key with someone else's private node key.
Task queued with free GPU memory: inspect requested CPU slots, system RAM, handler availability, telemetry age and ownership state. Free GPU bytes do not satisfy every requirement.
409 conflict: preserve the original request and reconcile its attempt/revision. Do not create duplicate work to bypass the conflict.
Lease heartbeat or authentication failure: inspect the exact rejection time and stopped outcome. Do not prolong the lease locally or restart shared infrastructure simply to clear the screen.
Result exists but is not delivered: check scoped transfer status, destination space and verification. Resume missing chunks; do not rerun a completed workload merely because delivery was interrupted.
Old green status: compare sample time and expiry. Stale, unknown and snapshot-only do not mean idle or healthy now.

For a new installation, first run the small local CPU self-test, then a small described fleet job with verified output. Observe the readable title on both nodes, verify the returned digest, and confirm CPU/RAM commitments and any test GPU lease are released. Test a deliberately interrupted transfer using non-sensitive sample data before a valuable production job. Service installation/start-after-sign-out is a separate Windows approval and acceptance step.

Email support@autosecurelogin.com with product/node/coordinator versions, readable task title, first and most recent occurrence with timezone, exact visible error, and last successful stage. Review any export before sending it. Never email tokens, private signing keys, full journals or customer inputs/results merely to explain a status number.