# Portable scripts implementation note
Personal utilities are maintained as inlined YAML under a preferred jan directory
(canonical: `dotfiles/jan`). The `jan-cli` crate ships the engine, examples, and
`scripts/jan-install.sh` — not a nested copy of the personal 215+ script tree.
Current behavior:
- Select and persist a reviewed command tree with `jan use <DIR>`.
- Inspect active commands with `jan --help`, `jan list`, `jan search`, `jan show`.
- Export the preferred tree with `jan bundle`.
- Verify and extract a bundle with `scripts/jan-install.sh`, review its YAML, and
explicitly activate it with `jan use <INSTALL_DIR>`.
- Generate aliases from the preferred tree with `jan alias`.
- Query the SQLite audit log with `jan audit`.
See [README.md](README.md), [docs/PORTABLE_SCRIPTS.md](docs/PORTABLE_SCRIPTS.md),
and [SECURITY.md](SECURITY.md).
A jan tree is executable code. Manifest hashes verify archive integrity but do
not authenticate its publisher.