Architecture

Anveld's architecture is built around one decision:

The core SDK defines protocols and infrastructure. Algorithms and integrations are plugins.

Core SDK

The core package includes:

• Protocols for policies, trainers, data sources, environments, and multi-agent environments
• Shared data primitives such as Observation, Action, and Batch
• Experiment tracking, callbacks, and trainer utilities
• Cluster management helpers
• Deployment packaging and optimization utilities
• Security and runtime validation
• Studio logging and streaming support

Why Only 7 Protocols

The architecture tries to standardize the minimum stable interface surface rather than freezing fast-moving algorithm design too early. That is why the SDK does not bundle every RL method or world model into the core.

Data Model Constraints

The SDK leans into immutability:

• Observation, Action, and Batch are frozen dataclasses with slots.
• Observation and Action use data={...} constructors.
• Mapping-style access is supported for observations and actions.

Those constraints are useful for safer distributed execution and clearer plugin interoperability.

Supporting Docs in the Repository

This docs app is the public-facing entry point. The repository also contains deeper architecture documents covering:

• System overview
• SDK internals
• Runtime internals
• Data flow
• Deployment pipeline
• Plugin architecture
• Studio visualization

Use Product Docs when you want to jump into those source documents directly.