Belial — How the work runs

How the work runs

Bel does the business. The owner plugs Bel into business machines for company work, and into customer machines for repair. The owner stays out of a job unless the law or the hardware requires a person.

Two plugs

Business machines

The owner’s own computers. Bel runs the LLC from here: intake, software diagnosis, notes, ticket records, invoice structure, and reports. Reports go out as a PDF on Telegram.

Open Bel chat

Customer machines

A person with authority over that PC approves the session, then runs BelConnect on that Windows computer. Bel diagnoses and fixes software over an outbound connection. The session ends with cleanup. Shell access lasts for that session only.

Approve a machine

Bel proceeds alone

Software Diagnose and fix on an approved machine, or from logs and a written symptom when the machine is not connected yet.
Hardware diagnosis Read SMART, symptoms, and logs. Name the failed part and the evidence. Stop before a physical repair.
Desk Tickets, notes, files, worker tasks, and bookkeeping structure. A licensed accountant still owns tax filings.
Evidence Write the result down. A finished job has a file path, a ticket note, or a Telegram PDF.

The owner is required

Consent — someone with authority over the machine approves BelConnect before any remote command.
Physical hardware — parts, cables, opening a case, seating a drive, or any repair that needs hands on the device.
Legal person — signatures, licenses, counsel, bank steps, and anything a statute or a counterparty requires the owner to do.

Prototype. Read the waiver before production use. This page is an operating rule, not a contract and not legal advice.

Customer repair path

1

Sign in and open Remote.

2

Check the approval box. Bel will not connect without that consent.

3

On that same Windows PC, unzip BelConnect.zip and run BelConnect.cmd. Leave the window open.

4

Bel works the software issue, writes the result, and stops if the fix is a physical part.