How Anthropic's new cloud automation platform integrates with the Process Classification Framework, Workflow Orchestrator, and self-annealing agent architecture to create truly autonomous AI pipelines.
A Routine is a saved Claude Code configuration — prompt + repositories + connectors + triggers — that executes on Anthropic-managed cloud infrastructure. Your laptop can be closed. The work keeps running.
Define a recurring cadence — hourly, nightly, weekly, or a custom cron expression. Runs start a few minutes after scheduled time due to stagger. Minimum interval is one hour.
Each routine gets its own HTTPS endpoint and bearer token. POST a message, receive a session URL. Integrates with alerting tools, deployment hooks, and internal dashboards.
React to repository events — PR opened, release published, labels applied. Rich filter system: author, branch, labels, draft state, fork status, regex. Each event starts a fresh session.
Routines execute as full Claude Code cloud sessions — with no permission prompts,
full shell access, MCP connectors, and the ability to push to claude/-prefixed branches.
The BACON-AI PCF organises all work into a 5-level hierarchy. A Claude Code Routine maps cleanly onto this structure — it is a workflow run triggered externally rather than manually.
Authentication, repo cloning, and branch push are deterministic safety layers. Claude cannot skip or reorder these — they are the safety envelope from Baby AI wake-up instruction #3.
The core execution block where Claude reasons, calls tools, reads files. Step order is elastic — Claude decides which tools to call and in what order based on the prompt and observed state.
Each trigger type maps to a variant: .V01 schedule (high-autonomy,
no human feedback), .V02 API (context-driven, fast SLO),
.V03 GitHub (event-scoped, PR-aware).
In the BACON-AI engine, a Routine execution maps directly to a
workflow.run — with blocks, steps, logs, and topology fingerprints.
This makes Routines auditable, self-annealing, and governance-aware.
draft → validated. Variant selected from trigger type.Formal BPMN 2.0 models of the Routine Execution lifecycle and the PCF integration pattern — rendered live in your browser.
Every Routine run produces a topology fingerprint. When routines consistently deviate from the canonical flow — skipping steps, adding tool calls — the engine automatically proposes new variants and fills capability gaps.
Every execution hashes its realized step sequence:
T:a3f2c91e. When this diverges from canonical,
the engine knows the workflow is self-annealing in practice.
When a Routine encounters a missing capability (a tool, block, or skill),
it creates a workflow.gap.record. Three identical gaps auto-escalate
to Medium priority — the system tells you what to build next.
Three identical topology drifts trigger variant candidacy.
A human approves, and the new pattern becomes .V04 —
a permanent, named execution context learned from real Routine behaviour.
Self-annealing only affects elastic blocks. The rigid trigger validation and output push blocks never drift — the safety layer is structurally separate.
Creating routines from the CLI, triggering via API, and integrating with the BACON-AI workflow orchestrator.
Concrete combinations of Claude Code Routines and PCF workflow patterns that demonstrate the power of autonomous AI pipelines.