-
Notifications
You must be signed in to change notification settings - Fork 2
Extension Guide
weich97 edited this page May 17, 2026
·
1 revision
The easiest way to contribute is to add one small module behind an existing interface.
- A new CSV-compatible data adapter.
- A simple analyst that emits standard
Signalobjects. - A risk gate that clips or blocks decisions under a new constraint.
- An execution simulator variant.
- A new evaluator that reads a completed
Trajectory. - A small visual demo under
examples/.
Start with:
python examples/extension_walkthrough_demo.pyThis demo swaps in:
GapVolumeAnalystVolatilityCircuitBreakerRiskExtensionCoverageEvaluator
The rest of the stack stays fixed: data provider, strategy, execution simulator, memory, reproducibility state, trajectory logger, and report generation.
- Keep the module narrow and testable.
- Add a small example script when the behavior is user-facing.
- Add or update tests if the module changes core behavior.
- Do not commit raw model prompt/response caches or credentials.
- Keep live API use optional.