# How to add a `/proc/bare_os` node

This guide covers adding a new booter-backed proc file under `/proc/bare_os`.

## 1) Add a VFS proc handler

- Implement a `procBareOs...Text()`/`...JsonText()` builder in `packages/bare-os-booter/index.js` options passed to `createVfs(...)`.
- Keep output deterministic and non-secret; include a `schema` field in JSON payloads.

## 2) Register the path

- Add the path in booter proc routing (and aliases if needed) in `packages/bare-os-booter/lib/vfs.js`.
- Include it in `/proc/bare_os/index.json` generation metadata.

## 3) Keep baretop snapshot lists aligned

- Update `packages/bare-os-coreutils/lib/baretop-snapshot.js` proc entry list if the node is relevant for dashboards.
- Keep booter-side snapshot entry sets in sync where required.

## 4) Test coverage

- Add/extend booter tests in `packages/bare-os-booter/test.js` for payload schema/shape.
- Add coreutils `baretop` fixture checks when panel/snapshot behavior changes.

## 5) Document and version

- Update handbook/reference docs mentioning proc surfaces and schema versions.
- If this changes a tracked schema contract, update `docs/reference/posix-compliance-matrix.json` or related contract docs.
- Ensure `scripts/verify-doc-contracts.mjs` and other relevant verifiers stay green.