Add new machine rollout guide

README.md

@@ -24,6 +24,7 @@ The biggest issue was not a lack of raw stored data. It was that durable, reusab
 ## Repo Layout
 
 - `docs/research.md`
+- `docs/new-machine-setup.md`
 - `templates/global/AGENTS.md`
 - `templates/global/config.toml`
 - `memory/`
@@ -37,6 +38,14 @@ Install this kit into your current Codex home:
 bash scripts/install_codex_kit.sh
 ```
 
+Set up a fresh machine from this repo:
+
+```bash
+git clone https://github.com/slaguru666/codex-ops-kit.git
+cd codex-ops-kit
+bash scripts/install_codex_kit.sh
+```
+
 Create a portable export bundle you can move to another machine:
 
 ```bash
@@ -83,4 +92,8 @@ Run the audit script periodically. If session storage balloons again, archive th
 - `balanced`: everyday profile
 - `deep`: higher-effort work when architecture or debugging really needs it
 
-These profiles are defined in [templates/global/config.toml](/Users/timevans/Documents/New%20project/templates/global/config.toml). The installer preserves machine-specific plugin and trust settings while merging the managed cost and memory block into your live `~/.codex/config.toml`.
+These profiles are defined in `templates/global/config.toml`. The installer preserves machine-specific plugin and trust settings while merging the managed cost and memory block into your live `~/.codex/config.toml`.
+
+## New Machine Rollout
+
+Use the short guide in `docs/new-machine-setup.md` when bringing another Mac or workstation onto the same Codex setup.