runtime-orchestrator-boundary
CommunityKeep workflow state safe across parallelism
Software Engineering#workflow-orchestration#state-machine#parallelism#safety-guardrails#architecture-boundary#retry-repair#notebook-commit
Authortransreal
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Prevents reliability bugs caused by putting workflow-lifetime state into the wrong layer when introducing parallelism, retries, approvals, or worker spawning.
Core Features & Use Cases
- Hard boundary rule (state lifetime): Routes turn-scoped, DAG-internal work to ClaudeRuntime and workflow-lifetime work to ClaudeOrchestrator.
- Parallelism decision table: Clarifies which patterns (tool parallel execution vs worker pools) belong to Runtime vs Orchestrator.
- Design-time enforcement checklist: Provides review questions that catch violations early (notebook writes, approval/pause/resume, retry loops, snapshot/restore, commit ordering).
Quick Start
When adding a new feature that involves parallel execution, ask which state survives across turns, and place workflow-lifetime state management into ClaudeOrchestrator instead of ClaudeRuntime.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: runtime-orchestrator-boundary Download link: https://github.com/transreal/claudecode/archive/main.zip#runtime-orchestrator-boundary Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.