XynAGI
Architecture explorer
Owner onlyD
THE SYSTEM, AT A GLANCE

Intelligence, connected.

Explore implemented services, prototypes and the connections still planned.

System mapAll layers
/
Interactive architecture
100%
FOLLOW THE SIGNAL

One request. Many moving parts.

Walk through repository paths or earlier design examples.

Illustrative walkthroughs. No live requests or actions are executed.
MODEL CONTEXT

A working view of XynAGI.

This snapshot refreshes the earlier design using repository code and dated engineering records reviewed on 7 October 2026. Source links are pinned to the exact commits inspected. It does not monitor live services.

How to read the evidence

Released means release records and code establish the service contract. Implemented means code exists; current production operation is not implied. Documented identifies a repository-described relationship. Prototype, Planned and Unverified retain their explicit limits. Mixed has implemented and incomplete parts, explained per component.

Separate service boundaries

The hosted Convex Platform and Fastify HQ control plane are different services even though both use /v1. The service SDK is distinct from the XovoX UI framework. The interview Runtime is distinct from the OpenClaw-derived XoS harness. Intelligence HQ is a knowledge component, not the HQ desktop.

Latest increments

Published service SDK: 0.8.0. Documents, PDF/DOCX rendering and evidence summary are implemented on Platform create-documents and SDK sdk-0.9.0 branches; engineering records report shared-dev verification on 7 October. A production rollout or published 0.9.0 package was not established. HQ PRODUCT.md records Drop 8.1 endurance acceptance on 5 September; older README introductions still describe a stub.

Sources take precedence over old diagrams

Engineering’s architecture diagram and some module descriptions lag newer dated increments. This snapshot reconciles them against implementation and specific release/acceptance records. Foundation is retired; standalone module repos are canonical. A retired marketing site or historical plan does not establish implemented capability.

What remains unverified

No production API, VM, deployment inventory or client records were queried. No backend tests or live acceptance exercises were rerun. End-user identity, real Composio OAuth, universal policy, HQ docking, hosted-service agent tools, routines and learning retain their documented limits. AVS, Veloce and DCLearnX are retained as earlier illustrative journeys; their consumer/provider repositories were not audited.

Inspected repository revisions

A private repository snapshot

The explorer contains no live client records and makes no calls to business, messaging, AI providers or repository APIs. This is a manual snapshot, not an automatic sync. Hosting access is controlled by Sites.