Mahrai

Context for LLMs

Mahrai is a control-plane registry and reconciler for the Sylveste/Interverse ecosystem, designated GSV-X5 in the infrastructure-tooling domain, pace-layer X. It does not replace the systems it sits over -- Hermes (runtime shell and operator cockpit), Sylveste (semantic operating layer and ecosystem world model), Ockham (dispatch, policy, routing, escalation), beads (task and planning state), Clavain (procedural know-how), and Zaka/Alwe (steering and observability) -- but functions as the adapter and housing that lets that stack of independently-evolving agent systems compose into one coherent environment instead of a bag of loosely related tools. The concrete mechanism is state reconciliation: Mahrai holds an intended state in repo-native control-plane records (config/control-plane/projects.json and sessions.json) and reads actual runtime state from the operator server, either as JSON or by reading live tmux sessions on zklw directly. A Python reconciler diffs intended against actual and emits snapshots and drift reports categorizing sessions as matching plan, drifted, or unknown, and a public-safe projection step renders those snapshots for downstream surfaces without exposing internal detail -- a deliberate architectural separation between the raw operational truth and what gets shown externally. The stated ambition goes beyond orchestration convenience: the canon frames the goal as a "garden-salon" of systems thinkers, a memory-rich, governable, cultivated environment where many synthetic intelligences can deliberate and act within a shared project ecology, with Hermes as cockpit and Sylveste supplying the semantic substrate. This makes Mahrai the connective/integration layer for essentially the whole named agent-infrastructure cluster (Hermes, Sylveste, Ockham, beads, Clavain, Zaka, Alwe) rather than a peer to any single one of them. Status: in-flight as of April 2026, tracked as a real, actively-developed control-plane registry rather than a design-stage concept -- the reconciliation loop (intended-state files, runtime read, diff, drift report, public projection) is the built mechanism as described, though the full garden-salon ambition remains a longer-horizon framing rather than a completed capability.