aliveworld

# World This is Mission Control. When the human opens their world, it should feel like booting an operating system — everything they care about, at a glance, with clear paths to action. NOT a database dump. NOT a flat list. A living view of their world, grouped by what matters, showing relationships, surfacing what needs attention. --- ## Load Sequence 1. **Read `.alive/_index.yaml`** — one read, everything the dashboard needs: every walnut's type, goal, phase, rhythm, updated, people, links, tags, bundles, and parent relationships. The SessionStart hook injects `<WORLD_INDEX_BRIEF>` (names, paths, phases, people) which is enough to orient, but the dashboard's goal lines, rhythm warnings and bundle counts come from the full index file. Older plugin versions injected the full index as `<WORLD_INDEX>`; if that's in context, use it and skip the read. 2. **If no index exists at all** — generate it first (`python3 "$ALIVE_PLUGIN_ROOT/scripts/generate-index.py" "$WORLD_ROOT"`), then read the output. Fall back to manual scanning only on first-time setup before the index infrastructure exists. 3. **Freshness check** — read the `generated:` timestamp from the index. Display it in the dashboard header. If older than 10 minutes, show a warning. If older than 1 hour, suggest regeneration. This makes index staleness visible instead of invisible. 4. Build the tree from the index — parent/child relationships from `parent:` field 5. **Lightweight fresh checks** — one Bash call each, no ...