Verify your installation

Goal

Confirm installation succeeded and that your own tools can use the saved context. Installer validation and a working AI session test different things.

Run the edition validator

For Community, from the extracted Starter Kit folder:

./install.ps1 -Target 'PATH-TO-VAULT' -Operation validate

For Pro, using the installed vault and original package:

If reviewed adoption preserved a legacy validator, use scripts/KOS-Pro-validate-kos.ps1 for Pro checks. Otherwise use the unprefixed validator below. Check the conditional command mapping and installer report first.

$Vault = 'D:\Vaults\KOS-Learning'
pwsh -NoProfile -File "$Vault/scripts/validate-kos.ps1"
pwsh -NoProfile -File ./Install-KOS.ps1 -RepositoryRoot $Vault -Operation Verify

Inspect the workspace

• Confirm the edition/version matches the package you intended to install.
• Check root instructions and the adapters you selected.
• Open representative notes and attachments. Confirm links still resolve.
• For Community, inspect 00 - System/Installation/Runs/<run-id>/report.md and the installation state.
• For Pro, retain the transaction/control records and inspect the verify output.

Verify a real session

Start an agent in the correct vault. Ask it to identify the router, relevant project files and exact next action, with file evidence. Then complete the quickstart’s fresh-session check.

Expected result and recovery

You should have a readable vault, a successful relevant validator result, and evidence that your chosen agent loads the intended project. If any part fails, retain the output and stop before moving real work into the vault. Use troubleshooting; do not label an untested session as verified.