alivesettings

# Tune Adjust how the ALIVE Context System works. Two levels: world-wide preferences and per-walnut config. For creating new skills, rules, and hooks — that's `alive:build-extensions`. --- ## The Spectrum | Level | What it is | Example | Where it lives | |-------|-----------|---------|---------------| | **Preference** | Toggle on/off | "Turn off sparks" | `.alive/preferences.yaml` | | **Config** | Walnut-level setting | "Nova Station should have a technical voice" | `_kernel/config.yaml` in the walnut | **The line:** Toggle = preference. Setting = config. Process or capability = `alive:build-extensions`. ## How It Routes When the human says "I want X": 1. **Is it a toggle?** → Write to `preferences.yaml`. Takes effect immediately. 2. **Is it walnut-specific?** → Write YAML config to that walnut's `_kernel/config.yaml`. Different walnuts, different settings. 3. **Is it a repeatable process or new capability?** → Route to `alive:build-extensions`. If unclear, ask once: ``` ╭─ 🐿️ that sounds like a preference (toggle). │ Add to preferences.yaml? │ Or is this walnut-specific config? ╰─ ``` --- ## Preferences `.alive/preferences.yaml` — read by session-start hook via `alive-resolve-preferences.sh`. ### Toggle Keys (default: all ON) ```yaml # Squirrel behavior spark: true # The Spark observation at walnut open show_reads: true # Show ▸ indicators when loading files stash_checkpoint: true # Shadow-write stash to squirrel YA...