Develop and extend AxonX
Keep research algorithms in plugins and reuse the framework's extension points for execution, records, and interfaces. Choose the layer you need to extend before changing code.
Choose an extension path
| Goal | Start here | Contract to consult |
|---|---|---|
| Prepare a source checkout and run checks | Contributing | Repository contribution rules |
| Implement a research Task | Development and operations guide | Task inputs, outputs, identity, and lifecycle |
| Package and register a plugin | Plugin management | Plugin manifest |
| Extend components, Jobs, or asynchronous steps | Framework extensions | Architecture |
| Build Studio features and artifact views | Studio development | Research artifacts |
| Integrate a service client | Python reference | HTTP API and events |
The development and operations guide is also bundled for optional built-in Agent loading. Its canonical dev_guide.md path remains available to external Skills and source links; focused pages own the deeper explanations and field references.
Validate the research change
Discover the registered Task's schema, exercise a minimal execution in a temporary workspace, and inspect its output metadata and declared artifacts. Changes to feature timing, fields, or upstream requirements need compatibility checks before reusing earlier records.
Use experiment design for algorithm comparisons and external agents for agent-driven development. The Alpha158 Enhanced plugin demonstrates a separate implementation with feature-group switches and independent confirmation.
Maintain the documentation
Update English and Chinese pages together. Keep algorithm details with plugins, general workflows in guides, and field definitions in references. The documentation source guide and site maintenance guide explain navigation ownership, generation, and build checks.