docs(backlog): B-0448 — Cloud Routines integration as 4th catch-43 defence layer#3039
Conversation
…fence layer
Aaron 2026-05-13 authorized this row ("yes that sounds good about the
backlog too") after the same-session research surfaced Cloud Routines as
a 4th catch-43 layer Anthropic ships:
- Scheduled triggers (hourly/daily/nightly/weekdays/weekly)
- API triggers (HTTP POST + bearer token per routine)
- GitHub event triggers (pull_request.opened, push, issues, releases, check_runs)
Usage caps: Pro 5/day, Max 15/day, Team/Enterprise 25/day.
Builds on PR #3034's tools/routines/ substrate (the canonical-source-of-truth
two-layer architecture established earlier today for Desktop routines).
Cloud Routines extend the same canonical pattern with a sibling
cloud-schedule.json file.
Killer use case identified: GitHub event triggers unlock per-PR review ticks
without any local cron infrastructure — cheap (uses GitHub event quota only,
not per-day cron quota) and zero local-process risk.
Decomposition hint included (B-0448.1 through B-0448.7) for the
implementing slice.
Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a new P1 backlog row (B-0448) documenting the future work to integrate Anthropic's Cloud Routines as a 4th layer of catch-43 defence, composing on PR #3034's tools/routines/ substrate. Docs-only — no code changes.
Changes:
- Adds
docs/backlog/P1/B-0448-...mddescribing motivation, scope, acceptance criteria, pre-start checklist, and 7-slice decomposition hint for Cloud Routines integration
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5709629319
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## Composes with | ||
|
|
||
| - [B-0440](docs/backlog/P*/B-0440-standing-by-failure-mode-detector-background-service-2026-05-13.md) — Standing-by failure mode detector — a Cloud Routine on GitHub events would catch this in real-time |
There was a problem hiding this comment.
The Markdown links in this section won’t resolve from docs/backlog/P1/... because they use repo-root-like paths and a glob segment (P*), which GitHub treats as literal relative paths; clicking these references returns 404 instead of opening the dependency rows. This breaks navigation for the row’s dependency/composition workflow, so these links should be rewritten to concrete relative file paths from the current document.
Useful? React with 👍 / 👎.
Summary
Files B-0448 — a P1 backlog row authorizing future implementation work to integrate Anthropic's Cloud Routines as a 4th catch-43 defence layer.
Why
Today the autonomous-loop substrate established three layers of catch-43 defence (PR #3034): CLI session cron, Desktop routine, repo canonical. The 2026-05-13 Claude Desktop feature research surfaced a 4th Anthropic ships — Cloud Routines (research preview) — that adds:
Usage caps: Pro 5/day, Max 15/day, Team/Enterprise 25/day.
Aaron 2026-05-13 explicitly authorized this row: "yes that sounds good about the backlog too" after the research synthesis.
Composition
B-0448 builds on PR #3034's `tools/routines/` two-layer architecture. The Cloud Routines integration is additive: `tools/routines//cloud-schedule.json` lives alongside `schedule.json`; a routine can have either, both, or neither.
Test plan
This PR is a docs-only backlog row — no code changes. The implementation slice (when picked up) will:
🤖 Generated with Claude Code