Collector
Reads allowed repository roots, status metadata and source files.
XvX Systems
Architecture
XvX separates orchestration, skills, local execution, data access, monitoring and deployment. Public documentation is generated from filtered metadata.
Reads allowed repository roots, status metadata and source files.
Collects, filters and stores module, stack, status, version and LOC metadata persistently in MySQL.
Renders technical pages without accessing private runtime state.
The Stats Layer collects, filters, and stores technical system metadata including module, technology stack, operational status, version and Lines of Code (LOC). Filtered statistics are persisted in the MySQL database and can be reused during the next analysis or development cycle, enabling historical tracking and automated system insights.
MySQL is persistent state across cycles, not temporary runtime information.
XvX agents can exchange and reuse knowledge across the agent network. Knowledge is exchanged through MQTT for machine-to-machine communication between agents and infrastructure components. Shared information is additionally persisted in the Agent Wiki as a human-readable knowledge layer for decisions, documentation and operational context.
This allows knowledge generated by one agent to become available to other agents while remaining transparent and understandable for humans.
MQTT is the exchange layer. The Agent Wiki is an additional persistence and documentation layer, not a replacement for MQTT.
magnetix-cgn/XvX · commit 6984df2
The XvX Agent System is developed by Picologic GmbH.
No secrets, settings values, logs, runtime output, cache data or private brain content are exported. Only module names, public status metadata, code-line counts, stack labels and last commit dates are exported.