Use this theme when ota should run repo tasks through a backend boundary instead of only on the local host. It is the right fit when local setup drifts, shared infrastructure is already available, or you want the execution environment to be part of the contract instead of an assumption.

• shows when execution boundaries matter more than local convenience
• keeps task intent stable while the runner changes
• gives humans and agents one place to learn backend-backed execution patterns
• makes the same repo feel predictable whether it runs in a container or on a remote host

• how to keep container execution explicit
• how to keep remote execution explicit
• how to preserve one repo contract across multiple execution locations
• how mode-specific dependencies keep host-only preparation out of container execution

• container/ - container execution-context examples
• local-topology/ - task target-binding and helper-app targeting patterns
• remote/ - remote execution-context examples
• os-aware/ - OS-specific launcher examples

1. container/README.md
2. local-topology/README.md
3. local-topology/task-target-binding/README.md
4. local-topology/shared-local-backend/README.md
5. local-topology/shared-local-backend-fulfillment/README.md
6. local-topology/shared-local-backend-environment/README.md
7. container/template/README.md
8. container/node-service/README.md for mode-specific dependency and selected-graph behavior
9. remote/README.md
10. remote/template/README.md
11. remote/ssh-node-service/README.md
12. os-aware/README.md
13. os-aware/python-service/README.md

Keep the backend thin and put repo truth in ota.yaml.