- Stock kernel: boot.policy v2 (maxExecLineDepth, denyEnvKeys, requireProcNodes);
richer BARE_OS_KERNEL_SELFTEST; example policy and timer drop-in samples
- Protocol: feature bits 28–30, seed RPCs (manifest_hints, peer_health, staging_slot)
- Booter: /proc mirrors, provenance, metrics_live, pear IPC registry, initd DAG,
suspend/resume wiring, exec budget, shell ${var} expansion, delegate limits,
telemetry v3 / OTel JSONL, ctx API 1.11.0
- Coreutils: /bin/timeout; seeder Pear/Bare: avoid bare process.env (globalThis.process?.env)
- CI: verify-ctx-api-feature-bits; docs: handbook, developer-guide, kernel-extensions,
capabilities index, environment appendix, READMEs
/lib/bare (system image)
Self-contained ctx.bare support on the system Hyperdrive:
bare-module-manifest.json— copy of the booter manifest (same keys and packages as host resolution).manifest.json— drive loader index:bundleslists IIFE paths that assign intoglobalThis.__bare_os_stdlib__;bundleStatssummarizes esbuild success vs stub-only placeholders.bundles/*.js— one file per manifest row. Successful builds are full IIFE bundles; failures are no-op stubs (see file header). Regenerate withnpm run build -w bare-os-bare-libs.
At boot the booter runs drive bundles first, then (unless BARE_OS_BARE_HOST_IMPORTS=0) fills any missing keys via host import().
Trusted image only: executing these bundles is equivalent to running seeded /bin utilities.