Automatic rules as triggers for Codex Cloud workflows

Hi everyone, I would like to test whether it is possible to use Codex Cloud as part of an autonomous development loop. The idea would be to have automatic rules pointing to specific repositories or Codex Cloud environments, so that those rules can act as triggers for the process. For example, a rule could periodically trigger tasks such as: - build a product/technical scorecard - detect regressions or issues - generate a backlog with evidence and suggested prompts - run validation scripts/tests - optionally prepare changes against a specific branch My goal is to understand whether Codex Cloud currently supports this kind of automation model, where rules can trigger work against a repository or a predefined Codex Cloud environment. Has anyone tested something similar? Thanks.