Install section: pip install klev

README.md

@@ -237,6 +237,40 @@ so it has to enter as a score, not as a perturbation.
 Probe hyperparameters (in `stitch/probe-*.pt`): TweetEval `T = 105.19`, `beta = 16.0`,
 `ext_weight = 1.0`; RumourEval `T = 1305.8`, `beta = 16.0`, `ext_weight = 1.0`.
 
+## Install
+
+```bash
+pip install klev
+```
+
+`klev` is the library: it carries the loader, the pointer readout, the record format and both
+usage paths, so a consumer does not clone this repo to use a checkpoint. Two version floors
+matter and pip does not know they are related to the architecture:
+
+| | why |
+|---|---|
+| `transformers >= 5.5.0` | the `qwen3_5` and `gemma4` architectures do not exist before it. On 5.3.0 `AutoConfig` raises "Transformers does not recognize this architecture", which unsloth then **misreports** as a generic "not supported yet" ValueError — it reads like a missing model, not a version. |
+| `unsloth >= 2026.9.11` | first release carrying gemma4 support. |
+
+Install unsloth with `--no-deps` if you are on ROCm, so its CUDA `xformers` dependency does not
+replace your ROCm torch build.
+
+On AMD/ROCm also `source scripts/rocm_env.sh` from the repo (shipped in the wheel as
+`klev.scripts`) **before** importing — it sets the arch override, `TORCH_ROCM_AOTRITON_ENABLE_BF16=0`,
+`UNSLOTH_COMPILE_DISABLE=1` and the rest. All of it is load-bearing; see
+`docs/m11-qwen35-08b.md`.
+
+Two console scripts come with it:
+
+```bash
+klev-system-one --ckpt lumierenoir/klev-0.8b --request my_request.json   # no server
+klev-serve       --ckpt lumierenoir/klev-0.8b --port 8090                # optional HTTP
+```
+
+`load_klev()` reads the base model from the checkpoint's own `adapter_config.json` and picks the
+matching delimiters, so you do not have to pass `base=` or `preset=`. Pairing a checkpoint with
+another model's weights would otherwise be silent nonsense rather than an error.
+
 ## Usage
 
 klev is a **library first**. A decision model is small and stateless, so the normal way to use