Status
Machines, advertisement freshness, persona fence/host/model/health, streams, lifecycle events.
HUB & DASHBOARD
The current hub runtime operates the pinned FalkorDB/Redis store. The dashboard and complete hub surface for messages, fences, channel adapters, status, and guided setup are approved designs being implemented in stages. The hub is infrastructure used by AI sessions, not an AI session itself.
CURRENT RUNTIME
The first hub runtime is a release-labeled FalkorDB/Redis container with Redis Streams, graph storage, AOF, and RDB persistence. It binds to loopback and keeps generated ACL, password, and data under one private state directory.
virgo hub start --config /absolute/path/to/hub.json
virgo hub status --config /absolute/path/to/hub.json
virgo hub stop --config /absolute/path/to/hub.jsonStatus reports unhealthy, stopped, absent, and specification mismatch instead of calling them running. Stop preserves the container and data.
DESIGNED DASHBOARD
Machines, advertisement freshness, persona fence/host/model/health, streams, lifecycle events.
Non-secret display, notification, and pacing settings through mechanized paths.
Channel credentials, bindings, integrations, and persona settings deferred from onboarding.
Character, voice, path, repository, channel binding, records, and retirement.
Search typed records, inspect provenance, and follow graph edges.
Personal edits and receipt-bound proposals for shared class/workspace behavior.
BOUNDARIES
RECORDS
Records are typed content-addressed nodes with provenance and directed edges. Markdown is a verified materialization, while one reusable viewer powers Explorer, Persona records, and Status detail.
See persona graph lineage →