This is the shortest practical guide for adding or improving an adapter in Codette.
For a new adapter, document:
- the adapter name
- the reasoning role it fills
- what kinds of prompts should route to it
- how it should differ from base behavior
Key files:
inference/codette_orchestrator.pyinference/adapter_router.pyconfigs/adapter_registry.yaml- training scripts under
training/
- Add or update the adapter entry in the registry/config.
- Add or adjust routing logic so the adapter is reachable.
- Update prompts or mode instructions if needed.
- Add tests for:
- routing selection
- response shape
- any failure modes or constraints
- Add benchmark or transcript evidence if the adapter changes major behavior.
If you train or update a behavioral adapter:
- record the dataset source
- record the training objective
- document what permanent or semi-permanent behavior it is meant to stabilize
- add at least one reproducible validation artifact
At minimum:
python3 -m unittest tests.test_adapters
python3 -m unittest tests.test_phase7_executive_controllerThen add a benchmark or demo artifact if the adapter meaningfully changes public behavior.