Answers from the current source

Kingdom Core is the Discord runtime and service layer behind Kingdom Carries. Kingdom Nexus is the authenticated web control plane served by the same production stack.

No. This is the public product and install site. Its dashboard links now open the production Kingdom Nexus, which handles Discord sign-in and authenticated operations.

The current deployment registers four top-level slash commands: /setup3, /uipgrade, /mod and /value. The Documentation page lists their current behavior and subcommands.

Yes. Run /setup3 preview:true before applying /setup3. Preview mode analyses the live channels without moving or creating anything.

The current /setup3 and /uipgrade commands are restricted to Discord server administrators. They also check that the bot has the channel/message permissions each operation needs.

The current /setup3 implementation does not delete channels. It preserves channel permission overwrites when moving channels and leaves ambiguous channels where they are.

There is no guaranteed setup time published by the current source. Server size and the amount of organization required can change how long the operation takes.

Vault is the Kingdom state backup and disaster-recovery system. It creates and verifies snapshots and supports retention and explicit restore actions; it is not advertised here as a password manager.

They should not. The public website configuration contains public URLs and the Discord application ID; bot tokens, OAuth secrets, session secrets and the private HQ bridge token belong in server-side configuration.

Yes. Kingdom Nexus exposes an authenticated HTTP API, an OpenAPI document, a live Server-Sent Events stream and a JavaScript SDK. The Developers page lists the current route contract.

The current Kingdom Network domain has a tenant registry and combines registered tenants with Discord guilds connected to the runtime. Guild state is keyed by Discord guild ID; actual access still depends on the authenticated Nexus authorization rules.