Lending permission persists across reserved capacity use

Qualified reserved capacity can keep lending enabled across ordinary Start, Connect and Stop cycles. Owner use requests the original clean capacity back; ending that use permits lending again after qualification. Managed environments require acceptance of the continuing base reservation charge before retention begins.

Choosing No reclaims borrowed capacity while keeping the reservation. Release reserved capacity is a separate reviewed action. Optional availability settings reserve owner-use windows, a ready-by time or a minimum number of compatible machines. They do not stop running owner work.

Billing reports the current UTC month’s base charges, earned credits and corrections, actual credit applications, net reservation charges and remaining earned balance. Earnings remain 50% of eligible settled compute as noncash, nonexpiring Nodus credits. BYOC credits offset eligible Nodus charges.

Borrower recovery uses declared checkpoints or safe retries within the accepted budget and price ceiling. Runtime qualification still controls which capacity and configurations can lend.

Isolated Jobs prepare their working directory before command startup, including the default /workspace on images that run as root. Borrower images remain read-only outside their assigned writable paths.

Host enrollment also accepts locally staged release files with --artifact-dir. The installer retains release checksum and signature verification, allowing host preparation without downloading the same files again.