ASL AI Hub Master Suite help center
Support: support@autosecurelogin.com. Include the product version, the exact warning and its time, the last successful step, and a short description of what you expected. Never send passwords, viewer keys, dispatcher keys, private keys, provider tokens, whole private-state folders or customer files without reviewing the request and the material first. The app does not automatically upload a support bundle.
1. What the four products do
PC Steward inspects the computer, explains findings with available evidence and timing, and offers narrowly scoped, reviewed Windows actions. A health scan is not a repair. It is useful without a fleet or any other ASL purchase.
rBroker coordinates resource ownership and runs the local broker, canonical parallel worker, node reporting and approved execution components. It can also host a fleet coordinator. It is more than a monitor; hosting and remote execution are explicit controls, not consequences of opening a status page.
AI Hub Companion connects supported AI providers and lets you construct, approve and advance described fleet workflows. It does not grant resources on a remote PC itself. The remote node makes the final admission decision.
Master Suite embeds their shared native workspaces in one Windows application. It bundles its own engines and approved-action helpers and does not open the three other desktop programs. It remains useful by itself. You do not have to purchase or install the separate apps to use Suite's included functionality. Standalone apps remain independently usable and are not unlocked by running Suite.
Each product keeps its own local profiles and history. Suite does not silently copy a standalone app's credentials or take over a running node. A single machine must not run two competing authorities for the same GPU or parallel-worker port. An “already managed” warning means inspect the existing owner and deliberately select the appropriate connection or hosting components, not kill its process.
2. First launch and choosing a workspace
Opening Suite does not start a health scan, connect a provider, join a fleet, execute a task, change cooling, install a service or authorize cleanup.
- Work plan validates a readable description. Validation is not submission.
- This computer reads current local resource/health observations when requested.
- PC health opens the full diagnostic and guarded-action workspace.
- Fleet reads a customer fleet snapshot using a viewer key.
- AI providers opens the shared provider connection and pairing workspace.
- Workflows creates and advances approved multi-step work and file delivery.
- Resource hosting manages the local engines, node membership and executor.
- Help explains ownership, startup behavior, safety and support.
Status cards are observations, not allocations. Read their sample time and stale indicator. An old green snapshot does not mean a machine is still online. Optional monitor modes refresh while enabled; they are not required for background services or a coordinator to function, and are not AI conversations consuming tokens.
3. Connect computers on different networks
Use a fleet coordinator reachable by every participating computer over HTTPS with a valid public certificate. The server address is configurable; it is not restricted to autosecurelogin.com. A Linux server, a Windows server with a suitable public HTTPS front end, or your own managed host can provide this endpoint.
The coordinator holds membership, scoped job state and transfer receipts. Nodes make outbound connections, so the participating PCs do not need public GPU-broker ports or router forwarding to their local worker services. Do not expose the loopback GPU or parallel-worker ports to the internet. The coordinator and its HTTPS front end are separate from local resource admission.
On each participating Windows PC, open Resource hosting, review its name and local configuration, and connect to the intended fleet. Join fleet sends the public enrollment record; JSON export/import remains available for an administrator who prefers that workflow. A node's private signing key stays on the node.
Membership means the fleet recognizes this computer. It does not authorize remote execution. Review the permitted dispatcher, handlers, resource limits and authorization lifetime on that computer before starting the executor. Viewer, enrollment, management and dispatcher credentials have different roles. A viewer key cannot be used to execute work, and a node's signing key is not a viewer key.
If enrollment fails, retain the existing identity and retry the intended join. Do not generate a replacement identity to make a warning disappear. A changed fingerprint is a different node until explicitly reviewed and reconciled.
4. Build a workflow that people can understand
Connect the workflow workspace to the correct customer fleet using its dispatcher credential. Give the overall task and each step a clear title, project, purpose, stage and expected result. For example, “Prepare forest-scene data for episode 1” explains more than a session number. IDs remain available for exact correlation, but are not used as a substitute for meaningful descriptions.
Choose the actual node and supported handler for each step, the CPU-worker count, system-memory grant and any GPU-memory requirement. Add dependencies so a later step does not begin until the earlier result is verified. Select the intended input files and final output destination explicitly. Read and approve the exact saved plan before advancing it; editing a plan is not approval of different work.
The currently reviewed handler set includes bounded JSON work, hashing and the supported shape-animation/media workflow. A handler is a locally registered capability, not arbitrary remote shell access. The program does not install an AI model, purchase provider access or turn an unrestricted prompt into arbitrary code execution on every joined PC. Supported media work needs a reviewed local encoder and appropriate hardware/driver configuration. An encoder found on the development PC is not automatically redistributed or licensed for customers.
A practical distributed example is preparing scene data on a CPU/RAM-rich node, running supported media work on the GPU node, and verifying/delivering the result to the frequently used laptop. The workflow engine coordinates dependencies and receipts; it does not promise artistic quality or support for unregistered creative tools. Review the actual supported capabilities before assigning production work.
5. System RAM and GPU RAM are different budgets
System RAM is the computer's main memory used by CPU workers and applications. GPU RAM is the graphics card's dedicated memory. A free amount in one pool cannot be substituted for a shortage in the other. The parallel worker enforces its declared system-memory/worker commitments; GPU workloads additionally need an owned GPU lease from the local broker.
A lease is a time-limited reservation for a specific owner and attempt, not proof that the full reservation is currently allocated by the driver. Conversely, an unleased GPU process can consume real graphics memory. Compare leased commitments, observed processes and telemetry timestamps; do not add Windows allocation references as if they were all exclusive dedicated VRAM.
Local policy sets the system allowance and managed ceiling. The OMEN development configuration uses one 5,120 MiB Windows allowance, not two reserves. Customers must size their own policy for their hardware. A 28 GB lease is only possible on a node whose verified capacity and policy admit it; it is not promised on every graphics card. Missing or inconsistent telemetry is “unknown,” never free memory.
Heartbeats keep an admitted attempt alive only until the server-confirmed expiry. Authentication rejection is not a temporary networking stall and is not permission to continue using the GPU. Timeout-aware retry must fit inside the remaining confirmed deadline. The workload must stop safely when ownership is lost; it must not obtain another session's lease or keep running under an invented extension.
6. Files, dependencies and final destinations
Transfers are scoped to the approved fleet, workflow/job and artifact namespace. The sender uploads bounded chunks; the receiver verifies the completed content before publishing it to the chosen destination. A completed render is not the same as a file delivered to your laptop. Check the final delivery receipt.
If the connection breaks, resume the original transfer. Already confirmed chunks are reused and only missing chunks are sent. A lost acknowledgement is uncertain until reconciled with the original transfer, not an instruction to render again. A partial destination remains partial and is not labeled as the finished output. Existing unrelated destination files must not be silently overwritten.
Allow enough space on both the node and the coordinator for pending transfers. If you run the server yourself, its HTTPS proxy must permit the documented bounded request size. A 256 KiB binary chunk becomes roughly 342 KiB of JSON/base64 data; the documented 384 KiB proxy allowance covers the application's 360 KiB request limit. A proxy “request too large” error is not a GPU admission problem.
7. Recovery without duplicate jobs
After an interruption, reopen the same saved profile and original workflow. Keep its node fingerprint, plan hash, job/attempt IDs and receipts. Unknown means the final outcome has not been confirmed, not failed and safe to repeat.
An offer whose acknowledgement was lost is reconciled against the original job. The explicit exact-offer retry sends the same saved request; it does not create new work just because a status call was temporarily unavailable. A changed node identity, changed scope, damaged encrypted store or missing initialized ledger requires recovery. None is treated as an empty successful installation.
Cancellation is a request. Claimed ownership remains until the original node reports the stopped outcome. Do not stop shared brokers or kill a worker simply because one screen has stale information. Review the original owner and process creation time, not the PID alone.
Finished workflows can be archived explicitly when their requested destinations are verified. Archive history preserves readable plans and receipts in protected storage, prevents reuse of archived workflow IDs and does not delete your output files. Pending or uncertain work cannot be hidden by archiving it. See the bundled FLEET-WORKFLOW-ARCHIVES.md for retention and recovery details.
8. Always-running service versus an open desktop app
The optional Windows service is installed through the reviewed service controls and Windows administrator approval. It runs the selected resource/coordinator/ reporting components independently of the desktop window. It is not installed merely by downloading the Store package. The desktop remains usable without it.
Service storage and identity are separate from the interactive user's profile. Select only the components this machine should own. Service-hosted execution has its own explicit CPU-only consent and resource/dispatcher boundaries; it is not automatic permission to execute GPU media or renew an expired authorization. Interactive sensor and cooling controls are not moved into Windows Session 0.
Before upgrading a service, drain accepted work and stop only the owned components. The reviewed upgrade transaction retains the original identity and configuration, checks the stopped process identity, and keeps the replacement stopped until its payload/configuration are verified. It does not silently enable new components. If an upgrade stops partway through, retain the pending record and resume the intended upgrade; do not delete its evidence or point an older writer at newer data.
Closing an app requests safe shutdown of what that app owns. Switching tabs does not cancel work. An active service can continue without the desktop, while a desktop-owned executor must drain safely. An unconfirmed shutdown keeps the orderly-close guard visible rather than claiming that every job stopped.
9. Diagnostics, temperatures, fans and cleanup
Expand a health issue to see what was observed, available timing, affected target and the recommended next step. “Last checked,” “last ran” and “last failed” mean different things. Historical event evidence is not proof that a fault exists now.
The health score reflects current checks from its scan. Retained crash/update history and recovered, stale or unconfirmed evidence remain visible but do not deduct points. Many old incidents cannot alone turn a healthy current sample into an immediate emergency. This does not prove recovery; review exact dates and verify current behavior. Current resource pressure and actionable findings still affect the score. The score is not a performance guarantee or certification.
Temperature, hotspot, power and RPM values depend on the hardware/driver exposing them. Missing is not zero. A fan percentage is not a physical RPM measurement, and one GPU-wide RPM reading does not identify every physical fan. Cooling control is only offered when the documented adapter reports support.
A temporary cooling boost is bounded and restores the reviewed policy. NVIDIA automatic control and AMD's saved curve/Zero RPM settings are different restoration paths. Do not run competing fan tools or force-stop a restoring helper. The app does not bundle or install a replacement display driver; see AMD_COOLING.md.
Optional AMD component terms: in PC health → Temperatures & Cooling, choose Review AMD component terms. Read the full versioned text and use Save terms for a local copy. Saving or closing does not accept. Choose Accept AMD terms only if you agree and have authority to do so, or Decline AMD adapter to keep it disabled.
No acceptance is preselected or inferred from purchase/installation. The full text is also bundled as Help/AMD-COMPONENT-TERMS.md, version 2026-09-13.1. These terms concern only the AMD adapter, not your own work or the products' unrelated features. The app does not install the SDK or a display driver.
Your decision, time, terms version and fingerprint are kept in Suite's own local health profile. Standalone Steward keeps a separate record; neither app copies the other's consent. Missing, corrupted or outdated consent blocks new AMD reads and boosts. Review new terms explicitly; acceptance does not launch a scan or cooling action. Refresh deliberately after deciding. Unavailable sensors remain unknown, not zero. NVIDIA, Windows diagnostics, AI and resource hosting are usable if AMD is declined. No consent or sensor content is sent to a fleet server.
You can decline later through the same dialog. This does not stop restoration already underway, and the consent check does not block an explicit restore of previously saved AMD settings. Restoration still needs a supported exact device, a valid protected saved profile and normal Windows approval. It cannot start a new boost or invent a default profile. If recovery cannot be confirmed, preserve the evidence, use the manufacturer's controls and contact support.
Cleanup is off by default. Previewed deletion is permanent, not the Recycle Bin. The bounded categories, age limits and exact preview are shown before removal. The optional daily in-app schedule is separately authorized and stops when the app closes; it is not an invisible system-wide cleanup service. Project/model directories are not automatically chosen because a drive has low space.
Damaged action history is visible and blocks repetition of Windows actions. It is not skipped or treated as empty. Preserve the original file and reconcile any running helper before repair; see ACTION-HISTORY-RECOVERY.md.
10. Platform, privacy and purchasing expectations
Master Suite and PC Steward require supported 64-bit Windows 11 versions. rBroker and AI Hub Companion have separate Windows compatibility declarations. Linux headless nodes use the portable contracts and outbound HTTPS, not a Windows UI running remotely. Apple scaffolding is not a claim of tested macOS hardware support.
Fleet-server hosting, electricity, third-party models, encoders and provider/API usage may have their own costs or licenses. Purchasing an ASL desktop product does not include unlimited third-party AI usage. The requested Master Suite price is US $90; the Microsoft Store checkout is authoritative for your region and taxes. The software must not claim a price or public availability before its Store submission is actually approved and released.
Only deliberately configured participants receive scoped work and transfers. Readable descriptions should not contain private prompts, credentials or sensitive paths just to improve a label. Review exports and coordinator hosting policy for your organization. Back up private identity, consent and workflow storage securely; copying public enrollment JSON alone is not a private-key backup.
Content safety and reporting: open Help, expand Complete help center, and choose Report inappropriate content. The shared native control opens a draft to support@autosecurelogin.com identifying Master Suite, not a different product. Nothing is sent automatically. It reads or attaches no task, prompt, result, identity, key, file or log. Enter your own brief concern, app version and time; do not send harmful media or confidential material. If no email app is configured, use the displayed address yourself. Opening a draft is not a submitted report.
Use only authorized content and services. Do not use ASL tools for child sexual exploitation, non-consensual intimate content, threats, hateful abuse, fraud, malware or other illegal harm. Do not request or distribute pornography or graphic real-world violence. Respect privacy, intellectual property, provider policies and fleet-owner rules.
Review generated material before sharing it. There is no public feed or promise of automatic moderation. Also contact the private fleet's owner; stop automatic advancement and use supported cancellation or consent controls while preserving unresolved ownership and recovery state. ASL reviews concerns involving its products and operated services and can restrict access where it has control.
A report cannot silently delete another server operator's retained copies. No response-time guarantee is implied.
Reading diagnostic dates correctly
In This computer, an expanded finding uses the same explanation and timing rules as PC Steward. Recorded Windows events are converted to your computer's local time and show both the time-zone name and UTC offset. The time the scan checked history is separate from the first and last retained failure.
A historical crash is not a claim that an app is crashing now; incomplete history is labeled, and a future timestamp tells you to check the clock. The detail includes evidence, confidence, recommended next steps, guided checks and their impact. Reading these details does not run a repair, change drivers or stop a workload.