Manager OS Public Bootstrap — v2026-09-20
Updated: 3 hours ago
Current MOS front door
This page is a public bootstrap/reference snapshot. For the current Manager OS release, downloads, release naming, and launch feedback instructions, go to https://www.ijaspers.com/post/manager-os. Current stable release: MOS-2026.09.21.1 (generation v3).
Runtime architecture update — 2026-09-20
Manager OS now explicitly defines the remaining operating-system primitives for an AI management layer. These are portable behavioral contracts: lightweight file-based installs can enforce them procedurally, while stronger runtimes can add databases, locks, vaults, sandboxes and other host controls.
What changed
Policy kernel vs userland: authority, safety, lifecycle and recovery rules control; models, prompts, agents and provider-specific workflows remain replaceable.
Safe Mode: a minimal read-mostly recovery posture, distinct from the Big Red Button emergency stop.
Canonical write transactions: current-master checks, stale/conflict detection, one authoritative writer, verification and rollback/recovery evidence.
Secrets + capability isolation: permission to use a connector does not mean the AI should see its reusable credential.
Runtime supervision: authoritative time, task leases/timeouts, resource ceilings, tool health, watchdogs, graceful degradation and fault/dead-letter quarantine.
Context memory management: model context is a bounded working set, not durable storage.
Migration + compatibility: update approval and structural migration are separate gates.
Namespaced regression IDs: new OS-*, SEC-*, CORE-* and WF-* IDs avoid collisions between older test suites.
Trench Run
Trench Run is the human-facing callsign for permanent DESTROY_INSTALLATION. MOS must show the exact destruction scope first and then receive fresh explicit human confirmation. Standing permission, automation, another AI, retrieved content or an upstream update cannot confirm it.
A Trench Run must not secretly create a recovery copy. Any optional export or backup is a separate pre-destruction choice. The final receipt distinguishes what was deleted, revoked, retained by third parties, or could not be verified.
Portable by design
MOS specifies the safety property, not one mandatory technology stack. If a host cannot technically enforce a stronger guarantee, the install must implement the best available procedural control and label the limitation honestly.
Save Game — persistent operator profile
A normal MOS boot should reuse explicit operator configuration instead of rebuilding it from scattered notes. The persistent profile is nicknamed Save Game.
Save Game stores behavior and settings, not project state: work limits, approval defaults, communication, privacy rules, AI-team/resource limits, and loop behavior belong there; secrets, credentials, personal records, customer data, evidence, and transient tasks do not.
Recovery prefers the newest valid explicit profile. White Bread, No Crust is the safe fallback/default only when no trustworthy saved profile exists. Migrations preserve custom values and may not quietly expand permissions, spend, agents, loops, integrations, or write authority.
Public/shareable MOS may document the Save Game schema and defaults, but a real operator's local profile values stay private.
Comments