VIBEPACKR · SETUP & PROVISIONING

Client provisioning

For users installing PackrGUI and for operators installing Enterprise Pack Builder. Your organization server must be provisioned first.

1. Choose the exact OS and CPU package in Downloads. Check its version, checksum, signature instructions and server compatibility.
2. Install or extract to the location specified by that platform package. Keep previous installers and organization profiles until your administrator confirms the change.
3. Use the organization-provided connection procedure for the exact release. The local AI endpoint in Settings is not the appliance mTLS endpoint. Use the supplied customer-access client and private configuration when that release requires them.
4. Verify the organization, installation, release compatibility and authenticated connection separately. A visible window or successful download is not connection proof.
5. Use only Work and Packs granted to your role. Builder produces candidates; Pack approval and governed execution use the appliance authority path.
6. Open the installed Manuals/Start_Setup.html and Client_Setup.html before connecting. The client package keeps the manuals, examples and common agent kit together. Use the OS installer; Linux server install.sh and setup.sh run on the appliance VM.
7. The setup agent registers the matching local MCP adapter in a fresh private output, imports its descriptor and Skills through the AI runtime, and verifies initialize, all 13 tool IDs, setup.status and actual Skill loading. Ordinary workers do not edit the common kit.