Owner deployment reference.
Find the separate Mac mini setup and acceptance records without mistaking them for user instructions.
The Mac mini is the intended bot/API/database target; the owner setup procedure has not established public production readiness.
For the deployment owner
Ordinary users do not need to run the bot, configure signers or install a database. Use the hosted website and supported private Telegram account flows. The deployment procedures live in docs/MAC_MINI_SETUP.md, docs/TELEGRAM_PUBLIC_READINESS.md and docs/PRODUCT_ENGINEERING.md in the project repository. These are owner/operator references.
The website remains on Vercel; the intended bot/API/Postgres target is a Mac mini, with Linux later. The Windows development computer is not a production host.
Setup is not enablement
Target-host builds, provider configuration, restart/recovery, native sessions and bounded funded acceptance remain separate evidence requirements. Keep existing admission, custody, risk and execution interlocks in place. Publishing a guide or passing a development build does not complete those requirements.
Public help never exposes private account records, credentials, wallet diagnostics, service ports or per-owner incident details.