Install KOS Pro 1.1.0
Use the guided Windows installer to inspect your vault, review the plan, and apply a supported setup.
Goal and prerequisites
Install the owner-approved KOS Pro 1.1.0 stable package on Windows with PowerShell 7.2 or newer. Keep a full independent backup of any existing vault. Close Obsidian and pause sync before apply or recovery.
Pro is currently private-access-only. Use the kos-pro-1.1.0.zip supplied through your authorized delivery channel. Academy plan access is the intended delivery channel; this guide does not announce an available Academy subscription or public download. Do not substitute another archive with the same filename.
1. Check the package
These instructions bind to the approved October 19 build. Its ZIP SHA-256 is:
682be1bf7f8d75d76bd9855ef0dfe050b808cbb26b4dfda404ca5f8d38d0df03Get-FileHash -LiteralPath './kos-pro-1.1.0.zip' -Algorithm SHA256Extract the archive outside the target vault. The package’s edition and installer are 1.1.0, with Core 1.0.0 and compatibility contract 1.
2. Start the guided installer
From the extracted package directory:
pwsh -NoProfile -File ./Install-KOS.ps1 -InteractiveOr name the destination explicitly:
$Vault = 'D:\Vaults\KOS-Learning'
pwsh -NoProfile -File ./Install-KOS.ps1 -RepositoryRoot $Vault -InteractiveDo not combine -Interactive with -Apply, -AcceptLicense, planner overrides or a prepared plan file. Follow the guided questions instead.
3. Review each decision
Review the detected vault type, resolved role folders, proposed changes, and any conflicts. Saved source evidence is revalidated under the installer lock before writing; if the source changed, review a new plan instead of reusing the old approval. The flow asks separately for plan approval, License acceptance, adoption, an applicable Community-to-Pro transition, and final readiness.
Acceptance is local and records document versions and hashes. The public grant flow does not require your name, email, payment or remote activation. Read the supplied License and Plan Terms before accepting.
Supported starting points
| Starting point | Guided 1.1.0 behavior |
|---|---|
| Empty vault | Supported |
| Supported Pro 1.0.0 | Upgrade supported |
| Pro 1.1.0 | Verify/repair supported |
| Recognized legacy KOS without competing installer authority | Supported subject to inspection |
| Ordinary Obsidian with supported role folders | Supported subject to inspection |
| Fresh Starter Kit 1.2.0 / Community 1.0.0 | Supported transition |
| Starter 1.2.0 created by enhancing ordinary Obsidian | Supported transition |
| Starter 1.0.0 or direct 1.1.0 | Blocked |
| Completed Starter 1.1.0 upgraded to 1.2.0, with validated retained history | Supported reviewed transition |
| Incomplete, corrupt or unknown historical Starter authority | Blocked |
| Unknown/newer/corrupt identity or incompatible role layout | Blocked |
The actual inspection result is authoritative for your vault. Linux/macOS and arbitrary plugin compatibility are not qualified for this guided release.
Historical Starter transitions
A completed Starter 1.1.0 installation must first be upgraded by the released Starter Kit 1.2.0 installer and pass its validation. The Pro installer checks the completed historical state and current Community identity together. It archives the original legacy state byte for byte, retires the Starter writer and uses Pro transactions for recovery.
After transition, use Pro maintenance. Do not run the old Starter installer, resume its legacy run, delete historical records or rewrite receipts to bypass inspection. Direct Starter 1.0.0/1.1.0 installations remain blocked. See upgrade and recovery.
4. Verify the result
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.
pwsh -NoProfile -File "$Vault/scripts/validate-kos.ps1"
pwsh -NoProfile -File ./Install-KOS.ps1 -RepositoryRoot $Vault -Operation VerifyIf you entered the target interactively, set $Vault to that same resolved directory before running these commands. Review the result, open existing notes, and complete the fresh-session exercise.
If installation stops
Keep the exact package and sibling .kos-installer-<id> control folder. Do not delete identity or receipt files to bypass a block. Review the report and use backup and recovery for interrupted transactions. Transaction backups are not full-vault backups.
Preserved legacy commands
Reviewed adoption can preserve customized legacy commands and install Pro counterparts beside them. Before verification, check the installer report and use the conditional command mapping. In that case, the validator is scripts/KOS-Pro-validate-kos.ps1; the original scripts/validate-kos.ps1 retains its prior behavior.
Package-copy advisory
This exact archive retains release-candidate wording in its bundled notes and a narrower legacy support summary in its manifest. The approved build is stable; those copy defects do not change its bytes or grant. This guide records the inspected October 19 behavior. Public availability remains separate from approval.
Versions, sources & verification
Reviewed against: KOS Pro 1.1.0 / Core 1.0.0.
Agent runtime behavior has not been tested for this article. Run the verification steps with your selected agent.
- KOS Pro 1.1.0 supplied release notes, installer reference and scripts
Source review confirms the documented interface. It does not replace testing your vault, tools, or recovery copy.