1.4 KiB
1.4 KiB
Operator Repositories
This directory is the single local home for built-in operator repositories.
Each built-in operator has a directory under backend/operators/builtin/<operator-slug>/.
Executable operator code should live in that operator directory when a handler is migrated
out of the legacy backend/operator-runner/main.py runner. The runner remains the stable
container entrypoint and delegates to migrated operator modules.
Repository contract:
operator.pyis the executable module for that operator.operator.jsonis the platform catalog/runtime metadata for that operator.repository.jsonis the local repository manifest for that operator directory. It records repository identity, entrypoint, runtime dependencies, external acceptance requirements, and the no-mock/no-simulation/no-hardcoded-output acceptance policy.- Regenerate manifests with
python3 scripts/generate_operator_repository_manifests.py --writeand verify drift withpython3 scripts/generate_operator_repository_manifests.py --check.
Acceptance requirements:
- Use real input files, JSON payloads, command execution, or storage clients in tests.
- Do not add mock-only, simulation-only, hard-coded, or shallow-only acceptance paths.
- Keep catalog metadata in
internal/api/builtin_operators_catalog.jsonaligned with the operator directory metadata. - Keep public operator docs in
docs/operators/aligned with runtime handlers.