Skip to content

Document registry resolution paths for agent readers #52

Description

@adohe

Spec candidate: #3.

Scope

  • Explain how algorithm registration and model adapter registration work.
  • Show how an agent can discover built-in algorithms and model adapters.
  • Explain why AReno keeps registries and self-contained runtime ownership instead of copying pith-train's direct instantiation style.

Acceptance

  • Preserves the existing "register, don't branch" AReno extension rule.
  • Cites current registry files and public discovery helpers.
  • No public API changes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/apiIssues or PRs related to the SDK/Trainer public APIarea/dxIssues or PRs related to developer experience (error messages, ergonomics, onboarding)area/modelsIssues or PRs related to model adapters (llama, qwen3, bailing, gemma4, etc.)kind/documentationCategorizes issue or PR as related to documentation

    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