# Sovereign AI Complete Best-Practices Kit

Updated October 13, 2026.

Start with [Sovereign AI Made Simple](https://jwatte.com/blog/sovereign-ai-made-simple/). This checklist brings together the seven detailed workstation articles, their eleven Markdown downloads, and the latest copy, paste, subscription and Drive lessons. Tick an item only after checking it on your own system. Each line explains why it matters and links to its detailed guide.

Use one section at a time. Read the linked guide before changing access, deleting data or replacing a service. Recommendations are not claims that every integration is active or every test has passed on your machine. No prices or guaranteed savings are assumed.

## Setup and first boot

- [ ] Keep website hosting separate from workstation migration decisions; why: moving development tools does not require moving every production site. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Distinguish local storage, local execution and hosted inference; why: a client running on your machine may still send prompts elsewhere. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Choose one useful task before installing tools; why: a small pilot shows whether the workstation helps. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Inventory the old machine, accounts, scheduled tasks and Windows-only dependencies; why: copying files alone does not finish a migration. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Compare exact CPU, usable memory, mirrored storage and network terms; why: marketing labels hide important differences. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Size for the browser, builds, databases, backups and models together; why: individual tools passing does not prove the combined workload fits. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Use a supported operating system and explicit runtime versions; why: predictable dependencies make repair easier. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Keep the administrator account separate from ordinary agent work; why: a mistaken task should have limited reach. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Record the intended device, project, deployment account and authoritative repository; why: a successful command on the wrong target is still a failure. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Transfer with a manifest, hashes and a final delta; why: files changed during migration must not be missed. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Review every excluded or unreadable source file; why: silent omissions can remove required history. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Verify databases, worker bindings, schedules, webhooks and secrets separately; why: a website build cannot prove those services moved. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Deploy a new site before checking its certificate and confirm registrar delegation; why: a configured DNS zone alone cannot answer for the domain. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Add optional tools only for a documented need; why: unused integrations create maintenance work. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Test a restart from an independent remote connection; why: the office computer must not remain a hidden dependency. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).
- [ ] Keep the old environment until restores and replacement workflows pass and the owner approves retirement; why: early shutdown can destroy the recovery route. [Detailed guide](https://jwatte.com/blog/sovereign-ai-playbook-remote-desktop-commander/).

## Security and hardening

- [ ] Confirm console or rescue access before changing SSH or firewalls; why: a recovery route prevents a remote lockout. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Maintain security updates and a reviewed reboot schedule; why: patched packages may still need a restart. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Test a fresh key-based SSH login before disabling password or root login; why: an existing session cannot prove new access works. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Keep the original SSH session open during access changes; why: it provides a short recovery window. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Inspect effective SSH settings and the active socket listener after changes; why: editing a configuration file does not prove the live service uses it. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Treat an alternate SSH port as optional noise reduction; why: it does not replace keys and patching. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Allow only required ports at the host and provider boundaries; why: two reviewed layers reduce unintended exposure. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Test the actual boundary from another network; why: local connectivity does not prove public ports are closed. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Review published container ports separately from host firewall rules; why: container networking can expose an unexpected route. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Keep model, database, browser debugging and desktop administration endpoints private; why: these services can reveal data or allow powerful actions. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Verify that unauthenticated and unauthorized identities are refused; why: a successful owner login is only half the access test. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Use Fail2ban with reviewed jail settings and confirm the jail is active; why: installation alone does not establish protection. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Use private tunnels or approved private networking with explicit identity policies; why: knowing a link must not grant access. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Separate agent privileges from administrative privileges; why: routine work rarely needs full host control. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Review vulnerability and secret scanner findings instead of suppressing them broadly; why: a clean-looking dashboard can conceal real risks. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Keep browser sandboxing and container isolation enabled; why: a rendering problem is not a reason to remove protection. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Change one measured setting at a time with a rollback plan; why: broad tuning makes regressions hard to explain. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).

## Persistent desktop and launchers

- [ ] Declare the storage that keeps profiles, settings, project files and keyrings; why: a container replacement discards unmounted state. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Keep operating-system packages in a reproducible image or installation recipe; why: manual fixes inside a running container disappear on rebuild. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Mount customizations over the startup source that actually gets copied; why: editing the final copied file can be undone on next boot. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Give the desktop container a stable hostname without publishing its value; why: browser profile locks can reject a recreated container with a different identity. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Preserve the intended user IDs and file ownership; why: persistent files can survive while becoming unusable. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Use a real persistent keyring on the application's session bus; why: a temporary secret collection cannot retain sign-in reliably. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Avoid plaintext password-store fallbacks; why: suppressing a warning can weaken credential protection. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Test locked and unlocked keyring behavior with synthetic data; why: persistence and access control are separate requirements. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Check app relaunch, desktop restart, container recreation and host reboot separately; why: passing one boundary does not prove the others. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Let the owner set up and unlock the real keyring privately; why: a synthetic test cannot prove owner authentication. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Test the shortcut the owner clicks under the ordinary desktop account; why: an SSH command may use a different environment. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Use stable wrapper names and explicit working directories; why: launchers should select the intended project and executable. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Check the active runtime version after an update; why: a downloaded installer or staged package is not an active upgrade. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Update through the installation's supported channel; why: different clients require different maintenance paths. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Keep the previous image, compatible profile backup and configuration; why: rollback needs both software and usable state. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Stage against a copied live profile with matching ownership; why: an empty test profile misses real startup problems. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Validate generated health-check commands, then close the browser gracefully before snapshotting; why: quoting errors and open profile writes undermine acceptance. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Promote a proved image digest, check after start and a second restart, and cap retries; why: repeated restarts must not become an endless repair loop. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).
- [ ] Record probation, health, restart counts and rollback readiness; why: one successful exit code does not prove a stable release. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-best-practices/).

## Browsers and remote access

- [ ] Verify each application sees its authorized uploads through an explicit route; why: shared hardware does not merge storage or permissions. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Test native account approval and expired authorization without losing task context; why: authentication renewal is a normal workflow dependency. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Test the actual rendered screen as well as the network connection; why: a connected stream can still be blank or unreadable. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Let the client choose a readable desktop size; why: a fixed large desktop makes phone work awkward. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Keep zoom, cursor movement and window framing usable on a phone; why: a tiny monitor is not effective remote control. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Handle stream touch gestures inside the remote surface; why: page scrolling must not steal cursor control. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Open the phone keyboard through a real top-level input and send keyboard events; why: clipboard substitution loses key behavior. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Allow one controlling tab and explicitly revoke the old controller; why: two tabs can otherwise silently discard or duplicate input. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Test orientation, app switching, phone lock and reconnect; why: mobile interruptions are normal operating conditions. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Show disconnected or unauthorized state and bound reconnection attempts; why: stale controls must not imply a live session. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Never replay keystrokes automatically after reconnect; why: replay can send text into an unexpected field. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Verify file destinations and transferred bytes; why: a download button does not prove the file reached the right place. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Keep an independent recovery access route; why: failure of the main doorway must not strand the owner. [Detailed guide](https://jwatte.com/blog/mobile-ai-workspace-lessons/).
- [ ] Check the correct browser profile and extension connection at every run; why: a prior successful session does not establish current readiness. [Detailed guide](https://jwatte.com/blog/desktop-commander-cowork-browser-agents-small-business/).
- [ ] Separate terminal tools, desktop applications and browser extensions; why: their permissions and platform support differ. [Detailed guide](https://jwatte.com/blog/desktop-commander-cowork-browser-agents-small-business/).
- [ ] Verify current provider eligibility and operating-system support; why: an installed CLI does not prove a related desktop feature exists. [Detailed guide](https://jwatte.com/blog/desktop-commander-cowork-browser-agents-small-business/).
- [ ] Give scheduled work its own browser and serialize control of an interactive browser; why: automation should not collide with the owner. [Detailed guide](https://jwatte.com/blog/desktop-commander-cowork-browser-agents-small-business/).
- [ ] Batch signed-in work from one authorized tab at a shared polite rate; why: fewer navigations save time without increasing request pressure. [Detailed guide](https://jwatte.com/blog/desktop-commander-cowork-browser-agents-small-business/).
- [ ] Use a supported API or narrow connector when it performs the required action; why: general browser control is a broader permission. [Detailed guide](https://jwatte.com/blog/desktop-commander-cowork-browser-agents-small-business/).
- [ ] Prepare the exact DNS or certificate changes for the owner when the platform refuses them; why: authorization does not guarantee an agent can make every click. [Detailed guide](https://jwatte.com/blog/desktop-commander-cowork-browser-agents-small-business/).
- [ ] Use only authenticated, explicitly authorized spawnable remote-control tools; why: a reusable remote process must not become a public command channel. [Detailed guide](https://jwatte.com/blog/desktop-commander-cowork-browser-agents-small-business/).
- [ ] Start with one read, one saved draft and one reversible edit to a copy; why: small checks expose connection and permission mistakes. [Detailed guide](https://jwatte.com/blog/desktop-commander-cowork-browser-agents-small-business/).
- [ ] Keep personal accounts, payment details and access instructions out of a pilot profile; why: the task needs limited business context. [Detailed guide](https://jwatte.com/blog/desktop-commander-cowork-browser-agents-small-business/).
- [ ] Review outward messages, purchases, deletions and commitments before executing them; why: a draft should not silently become a business action. [Detailed guide](https://jwatte.com/blog/desktop-commander-cowork-browser-agents-small-business/).

## Copy and paste

- [ ] Test select-to-copy in the terminal or desktop that supports it; why: selection copying differs between applications. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Use Ctrl+Shift+C to copy from a terminal and Ctrl+V where the destination supports paste; why: common shortcuts differ between terminals and ordinary apps. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Use middle-click paste only after checking the selection buffer; why: it can contain older text than the regular clipboard. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Provide a phone paste box with an explicit user action; why: phones need a practical way to transfer multiline text. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Test punctuation, newlines and repeated pastes with synthetic text; why: visually plausible input can still have changed bytes. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Do not add an implicit Enter when pasting; why: pasted text must not execute before review. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Confirm the focused field before typing or pasting a secret; why: an address bar can send it into history or a search request. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Check a pasted credential's expected length, prefix and character shape without showing its value; why: a paste can silently double the secret. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/). [Latest lesson](https://jwatte.com/blog/sovereign-ai-made-simple/#the-rules-that-save-you-the-most-trouble).
- [ ] Clear sensitive clipboard contents after the intended use; why: clipboard history and later pastes can expose them. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Never print clipboard contents in tests or logs; why: a debugging check must not become a secret disclosure. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/). [Latest lesson](https://jwatte.com/blog/sovereign-ai-made-simple/#the-rules-that-save-you-the-most-trouble).

## Agent jobs and concurrency

- [ ] Check logical CPU count, load and available RAM before admission; why: spare CPU alone does not establish safe capacity. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Choose a shared admission budget and lower it under memory or load pressure; why: independent worker limits must not add up to overload. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Keep one writer per target, repository branch and deployment destination; why: concurrent edits can invalidate each other's work. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Give each job its own brief, files, scripts, build output and result; why: isolation makes failures and ownership clear. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Parallelize genuinely independent work and wait for every exit status; why: a fast batch must still report each failed check. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Chain dependencies on successful exit records instead of delays; why: elapsed time is not proof that earlier work finished. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Save a checkpoint after each unit and verify input freshness on resume; why: interrupted jobs should continue without reusing stale results. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Serialize production deployment per site and push per repository; why: shared shipping operations need one owner. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Fetch current main and merge without rewriting shared history before pushing; why: published source must include other completed work. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Use worktrees for file separation while keeping tool permissions narrow; why: a worktree is not an operating-system sandbox. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Choose permissions by research, build, preview or shipping role; why: every job should receive only its required actions. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Separate approval rules, available tools and operating-system isolation; why: an allowlist does not establish a sandbox. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Respect explicit deny rules and report refused actions; why: missing permission must not trigger a global bypass. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Amend queued briefs before start and restart running jobs with a revised brief when required; why: a running unattended process may not read later instructions. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Stop and requeue work before a change makes its measurements stale; why: old evidence can misdescribe the new system. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Write remote launch scripts as files and syntax-check them; why: nested shell quoting can alter their meaning. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Record exact worker process IDs and use exit records to determine completion; why: pattern matching can match the command doing the search. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Treat remote detachment as a supervised launch with redirected input and output; why: a shell background operator can leave the connection open. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] End a supervising session only after required children finish and their results are recorded; why: unfinished background work cannot substantiate a handoff. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Measure hosted-model waiting separately from local model computation; why: these workloads need different capacity budgets. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Set local model context and concurrency limits deliberately and verify the effective runner; why: a large memory allowance does not configure parallelism. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Measure aggregate throughput and individual latency together; why: more completed work can still mean slower individual replies. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Do not add all category maxima as guaranteed capacity; why: browser, build and model jobs share the same host. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Raise descriptor or file-watch limits only after observing exhaustion; why: speculative tuning creates risk without measured benefit. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).

## Splitting work across AI subscriptions

- [ ] Use each provider's supported subscription sign-in for eligible work; why: subscription sessions and API keys can bill differently. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Verify the actual account's usage limits before dividing a batch; why: two subscriptions do not create unlimited capacity. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Split independent tasks between subscriptions you already use; why: a second available allowance can reduce waiting on one provider. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Keep separate task ownership and explicit handoffs between providers; why: splitting work must not create conflicting edits. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Track allowance exhaustion, waiting time and completed output per provider; why: the useful split depends on the workload. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Preserve shared project notes and source references at each handoff; why: a new model should not have to guess earlier decisions. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Never place subscription session tokens in an API gateway; why: supported account access is not permission to manufacture an API. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Choose API routes and budgets explicitly when work needs them; why: an unnoticed key can turn included work into metered spending. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Require explicit approval for a provider fallback's data destination and cost; why: a failure must not silently move private material or spend money. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).
- [ ] Respect provider retry timing and account restrictions; why: load sharing must not become limit evasion. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/).

## Backups and Google Drive

- [ ] Back up source, configuration, databases, profiles and workflow encryption keys; why: restoring only project files may not restore the workstation. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Keep an independent encrypted off-site copy; why: mirrored disks and local snapshots share the machine's failure risk. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Keep recovery credentials accessible without the workstation; why: a backup locked inside the failed host cannot help. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Use recoverable snapshots as well as any mirror; why: synchronization can faithfully copy accidental deletions. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Test a file and database restore into an isolated location; why: archive listings do not prove usable recovery. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Verify backup recurrence, retention and failure alerts; why: a successful first copy does not establish ongoing protection. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Use available space in a cloud drive plan you already have when suitable; why: existing storage can avoid a second service while retaining its limits. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Create and authorize your own Google OAuth client for rclone; why: a shared client can become a request-quota bottleneck. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Create a Google Cloud project you control and enable the Drive API; why: a private client needs its own approved API setup. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/#the-rules-that-save-you-the-most-trouble).
- [ ] Configure the OAuth consent audience and test users where required; why: the account that authorizes the backup must be eligible to use the client. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/#the-rules-that-save-you-the-most-trouble).
- [ ] Create the documented desktop OAuth client and keep its credentials private; why: rclone needs the right client type and the keys must not enter a public kit. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/#the-rules-that-save-you-the-most-trouble).
- [ ] Enter the private client details into the intended rclone remote and let the owner authorize it; why: application credentials alone do not grant access to Drive files. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/#the-rules-that-save-you-the-most-trouble).
- [ ] Check the selected config file and reload that exact file in a new rclone process; why: a successful save must be proved by the next process that reads it. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/#the-rules-that-save-you-the-most-trouble).
- [ ] Test a small approved copy and an isolated restore before scheduling the full backup; why: authorization and listing alone do not prove recovery works. [Detailed guide](https://jwatte.com/blog/sovereign-ai-made-simple/#the-rules-that-save-you-the-most-trouble).
- [ ] Review the OAuth consent setup and requested scopes with the account owner; why: backup access must have an understood permission boundary. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Keep rclone credentials protected and pass the intended configuration with --config; why: atomic config saves replace a symlinked file instead of preserving that link. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/). [Latest lesson](https://jwatte.com/blog/sovereign-ai-made-simple/#the-rules-that-save-you-the-most-trouble).
- [ ] Avoid an arbitrary one-request-per-second rclone cap for bulk Drive backups; why: unnecessary throttling can turn a healthy transfer into a slow one. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Honor actual Drive quotas, retry timing and adaptive backoff; why: a private OAuth client still has service limits. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Measure throughput and elapsed time before and after a client change; why: transfer settings need evidence from the real upload. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Start with conservative transfer and chunk settings, then measure resource use; why: aggressive settings consume RAM and shared bandwidth. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Prefer reviewed copy or snapshot operations before considering sync; why: sync can delete destination files and needs extra care. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Verify transferred content and exclusions with an explicit manifest; why: a completed process can still omit required data. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Leave an active shared backup undisturbed while planning improvements; why: changing its credentials or process mid-copy risks interruption. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Keep encrypted recovery copies, database exports and compatible rollback snapshots distinct; why: each protects against a different failure. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).

## Monitoring and watchdogs

- [ ] Give current operational records precedence for current-state questions; why: an authentic old note can still answer the wrong question. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Check vector database collection aliases and embedding identity after migration; why: a reachable database can point to the wrong knowledge set. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Test workflow replay and retained encryption keys; why: a restored automation must not duplicate actions or lose its credentials. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Test proxy health, unauthorized refusal, expected body and client integration separately; why: a healthy endpoint does not prove the intended transport works. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Supervise durable work with a service manager; why: an open terminal is an unreliable service owner. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Enable and test the intended units and timers; why: installed unit files alone do not start recurring work. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Use user-service lingering deliberately where needed; why: survival after logout does not create a graphical session or unlock a keyring. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Record queued, started and terminal states with timestamps for every run; why: no work and failed prerequisites must be distinguishable. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Check heartbeat freshness, log age and useful checkpoints separately; why: a live supervisor can accompany a stuck worker. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Check failed exits and queues that stop draining; why: liveness is broader than a matching process name. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Use bounded retries, timeouts and visible failure reasons; why: repeated failures should not create endless restart loops. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Alert on state changes and keep failed delivery in a durable outbox; why: noisy alerts and silently lost alerts both weaken monitoring. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Report a recovery once and keep the incident history; why: corrected failures still matter for diagnosis. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Use durable operation IDs and reject duplicates; why: reconnects and retries must not repeat side effects. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Record source versions and keep older notes separate from current state; why: yesterday's success cannot prove today's readiness. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Combine exact keyword search with semantic retrieval and preserve provenance; why: similarity search alone can miss a precise rule. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Test embeddings, vector dimensions, indexing coverage and stale-source behavior; why: installing a vector database does not prove useful memory. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Keep source documents, hashes, extraction details and reviewed redactions; why: a summary alone cannot substantiate an answer. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Try every planned public URL directly and through the approved proxy chain, then passively render persistent blocks; why: a failed first request is not the end of measurement. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Detect challenges from the page itself and keep blocked content out of the usable cache; why: normal scripts and interstitial pages must not be misclassified. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Never solve a CAPTCHA, bypass a login or paywall, or impersonate a search crawler; why: retrieval must respect access boundaries. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Share rate limits across workers for each origin and proxy service; why: parallel jobs must remain polite together. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Keep every attempt's time, status, final public URL and retrieval tier; why: page coverage and access failures need traceable evidence. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Report planned, measured and unmeasured pages with reasons; why: one sample does not establish another page's result. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Respect cache freshness and force new measurement where the audit requires it; why: an old capture must not masquerade as a current check. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Keep indexing preparation, authorized submission and actual indexing status separate; why: acceptance of a request does not establish publication in search. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Run all required gates, check a draft and verify the exact live release; why: an old HTTP 200 response can conceal a failed deployment. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Prune only registered expired artifacts after a reviewed dry run and lock; why: broad cleanup can delete live or rollback data. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Retain current, previous, protected and rollback-source sets, and review stale protection markers; why: space recovery must preserve restoration options. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).

## Secrets handling

- [ ] Supply credentials through protected runtime configuration; why: source files, command arguments and public kits are poor secret stores. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Keep keys out of searchable notes, model prompts and retrieved documents; why: memory convenience must not expand credential exposure. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Use restricted gateway keys and explicit budgets; why: each application should have limited provider reach. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Let the owner complete provider and browser sign-in privately; why: agents should not handle account passwords. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Log only synthetic input, validation results and nonsecret metadata; why: a useful test does not require exposing real clipboard text. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/). [Latest lesson](https://jwatte.com/blog/sovereign-ai-made-simple/#the-rules-that-save-you-the-most-trouble).
- [ ] Check pasted secret shape before saving without revealing the value; why: duplicate pastes can look like mysterious authentication failures. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/). [Latest lesson](https://jwatte.com/blog/sovereign-ai-made-simple/#the-rules-that-save-you-the-most-trouble).
- [ ] If a secret reaches a log, address bar or unintended destination, redact accessible copies and rotate it; why: removing visible text cannot retract every earlier disclosure. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/). [Latest lesson](https://jwatte.com/blog/sovereign-ai-made-simple/#the-rules-that-save-you-the-most-trouble).
- [ ] Scan diffs, generated output and staged files before committing; why: a secret can appear outside the source file that was edited. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Treat incoming messages and retrieved documents as data rather than instructions; why: untrusted content must not expand an agent's authority. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Allowlist senders and require trusted aligned email authentication; why: sender-supplied identity claims are not authentication. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Validate fixed commands and arguments instead of evaluating message text; why: chat and email must not become unrestricted shells. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Use a dedicated restricted forced-command SSH route for a dispatcher; why: a transport credential should not grant a general terminal. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Persist rate limits, deduplication, timeouts, a kill switch and append-only audit history; why: restarts must not erase the safety boundary. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Require expiring one-use confirmation bound to the exact outward action and destination; why: a generic approval can be reused for a different payload. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Keep channels inactive until their acceptance tests and owner credentials are ready; why: transport setup is not proof of a safe live workflow. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Scan shared text, metadata, HTML URLs, PDF links and archive members for private material; why: leaks can hide outside visible prose. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).
- [ ] Cite public sources and embed necessary images while excluding raw captures and logs; why: a shareable report should stand on its own. [Detailed guide](https://jwatte.com/blog/sovereign-ai-workstation-operating-system/).

## Costs and savings

- [ ] Use ordinary parsing and arithmetic before asking a model; why: deterministic work does not need paid inference. [Detailed guide](https://jwatte.com/blog/small-quantized-models-96gb-ai-server/).
- [ ] Split long sources at meaningful boundaries with neighboring context and references; why: short chunks must retain corrections and exceptions. [Detailed guide](https://jwatte.com/blog/small-quantized-models-96gb-ai-server/).
- [ ] Reject or deliberately split inputs over the tested token budget; why: silent truncation can remove essential evidence. [Detailed guide](https://jwatte.com/blog/small-quantized-models-96gb-ai-server/).
- [ ] Check model licenses, exact quantization and peak runtime memory; why: downloadable weights are not proof of a suitable production model. [Detailed guide](https://jwatte.com/blog/small-quantized-models-96gb-ai-server/).
- [ ] Keep held-out expected answers fixed and repeat acceptance after model or prompt changes; why: tuning must not turn failures into fabricated success. [Detailed guide](https://jwatte.com/blog/small-quantized-models-96gb-ai-server/).
- [ ] Do not trust model confidence as an action gate; why: required evidence and external validation are inspectable. [Detailed guide](https://jwatte.com/blog/small-quantized-models-96gb-ai-server/).
- [ ] Compare the same workload and billing period across local, virtual and dedicated hardware; why: unlike-for-like comparisons manufacture savings. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] Include power, cooling, internet, setup fees, tax, backup, model usage and administration; why: the server invoice is only part of the cost. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] Label estimates and list their assumptions; why: private expenses and illustrative numbers are not universal facts. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] Use provider prices and limits only with official sources and read dates; why: changing plans can invalidate a savings claim. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] Measure completed work and review time rather than tool count; why: business value comes from usable outputs. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] Count retries, human corrections and failure recovery in the budget; why: cheap model calls can create expensive rework. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] Use subscriptions you already pay for where the supported route fits; why: avoiding additional API charges depends on real eligibility and limits. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] Run server-side browser work when it replaces a separate desktop you no longer need; why: savings require actually retiring the duplicate expense. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] Keep persistent launchers, profiles and notes; why: avoiding repeated setup saves operator time. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] Use short, bounded local tasks and validate outputs outside the model; why: local inference can reduce paid input without sacrificing checks. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] Keep context only as long as the task needs; why: oversized context consumes memory and slows work. [Detailed guide](https://jwatte.com/blog/small-quantized-models-96gb-ai-server/).
- [ ] Validate fields, types, dates, references and arithmetic with code; why: a valid-looking response can still be wrong. [Detailed guide](https://jwatte.com/blog/small-quantized-models-96gb-ai-server/).
- [ ] Include missing, contradictory, hostile and held-out cases in model tests; why: tidy synthetic examples do not establish production accuracy. [Detailed guide](https://jwatte.com/blog/small-quantized-models-96gb-ai-server/).
- [ ] Record model, quantization, context, warm or cold state and combined load; why: model size and disk footprint do not predict real response time. [Detailed guide](https://jwatte.com/blog/small-quantized-models-96gb-ai-server/).
- [ ] Send compact verified facts with source references to the next step; why: removing unnecessary material helps while evidence remains available. [Detailed guide](https://jwatte.com/blog/small-quantized-models-96gb-ai-server/).
- [ ] Keep explicit unknowns and a manual fallback; why: confident invention can erase the apparent savings. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] Treat concurrency observations as workload-specific; why: hosted-model waiting and local inference have different limits. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] Invest in security, restores and recovery access; why: preventing downtime and data loss is a risk saving, not a guaranteed cash rebate. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).
- [ ] For generated brand art, request a meaningful mark without letters and redraw it as a vector; why: small icons and business names need dependable rendering. [Detailed guide](https://jwatte.com/blog/desktop-commander-cowork-browser-agents-small-business/).
- [ ] Keep a named owner for review and a tested failure path; why: automation saves time only while someone can maintain it. [Detailed guide](https://jwatte.com/blog/sovereign-advantage-dedicated-ai-workstation/).

The dated fact-check sections in the linked articles retain the official sources, test conditions and observation dates for technical claims. The companion downloads supply the longer commands and acceptance matrices. Use those reviewed instructions rather than turning this checklist into an unattended installer.

Source note: [rclone Google Drive setup](https://rclone.org/drive/) and [rclone configuration and rate limits](https://rclone.org/docs/) were read October 13, 2026 at 22:36:46 to 22:36:48 UTC. The current Drive guide requires a client you create and documents retirement of the shared client in 2026. The configuration guide documents explicit --config selection and a default --tpslimit of 0, meaning no fixed transactions-per-second cap. The symlink replacement and doubled-paste lessons are operational observations explained in the new article, not guarantees drawn from those documentation pages.