meerkat-platformlisted

# Meerkat Platform Guide Meerkat (`rkat`) is a library-first agent runtime exposed through multiple surfaces. One execution pipeline, realm-scoped state, runtime-backed semantics by default. This guide is task-oriented; deeper schemas live under `references/`. References: - `references/api_reference.md` — per-surface methods, schemas, examples (CLI, REST, RPC, MCP, Python/TS/Rust SDKs). - `references/mobs.md` — multi-agent orchestration in depth. - `references/migration_0_5.md` — only if you're upgrading from 0.5 (`host_mode` → `keep_alive`, etc.). ## Realm-first model `realm_id` is the sharing key across all surfaces. - Same `realm_id` => shared sessions/config/backend. - Different `realm_id` => strict STATE isolation (sessions, stores, event logs are realm-local). - Backend (`sqlite` or `jsonl`) is pinned per realm in `realm_manifest.json`. Config inheritance (state still never inherits): - A realm config doc may declare a parent (`[realm.<id>] parent = "<other>"`). Resolution walks head → parent chain → the implicit `global` tail (the universal default head; its config is the single HOME-rooted `~/.rkat/config.toml`). No flat sibling scan, no literal `default` realm. - CONFIG inherits down the chain: models, mcp servers, hooks, skills, limits, and auth bindings. Surfaces compose the effective config over the head realm on the agent-build path, so inheritance applies everywhere, not just to auth. - Credential READS inherit (a child resolves a binding defined in a pa