Canonical system-of-systems blueprint

Vahana Ecosystem Map

From intention to verified action. Machine IDs and legacy aliases remain backward compatible.
intentconversation and controlsgoalidentity and policyreasoningworker intelligencecapability requestdelegateexecuteworker actionsoutputs and evidenceverified resultimmutable artifactsdesired versionkeep alivekeep alivekeep alivekeep alivehealthhealthhealthhealthoperational evidenceUserentryChannelsWhatsApp · Slack · Web · Desktop · AROS · APIKakshaDeck · CockpitSaarthiHermes Core · Hermes AgentSoulSOUL.mdSutraSHRE · shreaiGanaMyClaw · OpenClawKriyaShivaPramanaSIA · SiaNirmanaGranthiModels & ComputeLLMs · APIs · Local computeService Supervisorlaunchd · systemd · Windows SCMRelease ControllerDeveloper · Beta · ProductionHealth & EvidenceLogs · Metrics · Crash reports

Canonical names and aliases

Vahana nameLegacy aliasesPlane
KakshaDeck, Cockpitexperience
SaarthiHermes Core, Hermes Agentintelligence
SoulSOUL.mdidentity
SutraSHRE, shreaicapability
GanaMyClaw, OpenClawworkforce
KriyaShivaexecution
PramanaSIA, Siaassurance
NirmanaGranthiengineering

System invariants

  • Display names may change; machine IDs, repository names, CLI commands, API paths, environment variables, and persisted identifiers remain backward compatible.
  • Every installed long-running service is owned by exactly one native supervisor.
  • Beta and production promote identical immutable artifacts by digest; production is never rebuilt from a moving branch.
  • A customer installer contains runtime artifacts only and never includes source repositories or forge administration services.
  • Readiness controls traffic, liveness controls restart, and dependency failure must degrade safely rather than trigger an unbounded restart storm.