Initial runtime policy: reuse installed omp 18.3.2 and the existing relay unchanged. No globally installed packages or replacement harness.
Existing host runtimes observed 2026-09-27: Python 3.13.5, Node 22.23.1 and Google Chrome 142.0.7444.175. These are observed supplied runtimes, not a claim that they are the latest upstream releases.
Dependencies: prefer no new application packages. Any added dependency requires an exact stable version and dated upstream evidence.
Wiki: use the established shared publisher for the OmpOS wiki only, with its built-in global lock. Never edit publisher or engine. Serve the current release pointer.
Heavy work: serialize all installation/build operations under nice level 10.
Ingress: preserve own backups, validate nginx before every reload, request only own certificate names with the existing webroot.
Service (deployed 2026-09-27): systemd unit ompos.service runs server.py with Nice=10, ProtectSystem=strict, ProtectHome=read-only, writable only runtime/ and catalogs/; loopback TCP 51980 for shell/health, Unix socket for private API. Restart with sudo systemctl restart ompos.service; logs via journalctl -u ompos.service. The native seats adapter refuses to run unless the collab registry mount verifies read-only, so listing cannot prune shared state.
Authelia: use existing correct policy when possible. Otherwise require a clear writer window, one backed-up batched domain/path-only change, in-container validation and one compose restart. During the 2026-09-27 run no such window existed: zero shared edits, zero restarts, public app vhost intentionally 503.
Rollback: bootstrap source commit is 48223ce0f1178db37eb05b25f2bbf16daacca38d. Runtime rollback is separately scoped to OmpOS’s unit/vhosts and wiki current pointer; do not reset other repositories or alter shared services to undo application code.
Private receipts and runtime metadata do not belong in public wiki content or its search index.