Skip to content

Record the current AReno backend topology #58

Description

@adohe

Spec candidate: #9.

Scope

  • Add a short architecture note describing Trainer -> Backend -> ArenoBackend -> ArenoEngine.
  • State that the current runtime path is AReno-owned CUDA/NVIDIA code.
  • State that ArenoBackend currently owns both rollout and train calls through one colocated engine.

Acceptance

  • Cites the current files/symbols.
  • Does not promise MLX, TPU, vLLM, SGLang, Megatron, or Ray integration.
  • Verification: docs file renders as plain Markdown or RST.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/apiIssues or PRs related to the SDK/Trainer public APIarea/engineIssues or PRs related to the engine runtime (workers, TP, rollout, training)good first issueDenotes an issue ready for a new contributorkind/documentationCategorizes issue or PR as related to documentationpriority/important-soonMust be staffed and worked on either currently, or very soon

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions