leeway-parallel-workplane
Governed foreground-conversation and delegated-execution orchestration for LeeWay agents. Keeps the parent conversational/control plane responsive while independent workers/subagents execute bounded j
SKILL.mdskills/leeway-parallel-workplane/SKILL.md
GitHubLeeWay Parallel Workplane
Core law
The parent Agent Lee control plane remains available to the Creator. Long or parallel work belongs on bounded execution lanes when the harness supports them.
conversation/control plane != execution workplane
Do not fake concurrency. If the current harness cannot sustain background workers across turns, classify that capability UNAVAILABLE and use bounded in-turn parallel tool execution or an authorized external worker/runtime.
Planes
Conversation Control Plane
Owns Creator dialogue, intent changes, acceptance gate, priority, authority, worker dispatch, interruption, retooling, evidence review, and final merge.
Execution Workplane
Owns bounded delegated jobs. A worker receives only the authority/capabilities needed for its assignment and never becomes the parent Agent Lee identity.
Worker contract
Every delegated job carries: workId, parentObjectiveId, objective, acceptanceCriteria, authorityScope, capabilityWeave, focalExecutionSet, verificationSet, recoverySet, dependencies, mutationScope, checkpointPolicy, interruptPolicy, evidenceDestination, status, and returnContract.
Worker states
PROPOSED → DISPATCHED → RUNNING → CHECKPOINTED → COMPLETED. Alternate states: PAUSE_REQUESTED, PAUSED, CANCEL_REQUESTED, CANCELLED, RETOOL_REQUIRED, FAILED, BLOCKED, SUPERSEDED.
Interrupt and retool law
A Creator change must be evaluated against active work. The parent may CONTINUE, PAUSE, CANCEL, SUPERSEDE, or RETOOL a worker. Retooling creates a new explicit work revision; it does not silently rewrite what the worker was previously authorized to do.
Parallelism law
Parallelize only work units that are independent or whose shared state is read-only/partitioned. Serialize conflicting mutations. Never allow two workers to mutate the same canonical target without an explicit merge/locking strategy.
Reporting law
Workers report checkpoints/evidence to the parent; they do not directly promote their own result to completion. Parent orchestration + Veritas determines acceptance.
Capability-gap law
If a worker discovers a missing skill/tool/provider, it reports the exact gap to Capability Resilience. The parent may dispatch a separate capability-development lane while unaffected lanes continue.
Conversation availability
For accessible conversation during a job, use spoken and written labels when requested: "Side question" before an incidental answer, "Main task update" for execution progress, and "Back to the main task" on resumption. A side question preserves the original objective unless the Creator explicitly changes it. These labels do not create separate chats or prove concurrency. State when a worker is actually running, and disclose when execution pauses while the parent answers.
Do not make the Creator wait for a long explanation before work begins. Dispatch eligible lanes first, then report concise checkpoints while work continues where the harness genuinely supports continued execution.
Harness boundary
This skill is portable governance. Actual background persistence, subagent spawning, cancellation, messaging, and concurrency require a runtime/harness that exposes those controls. configured != running; dispatched != executing; executing != verified.
Canonical persistent-execution binding
When persistent execution is requested, use config/persistent-workplane-runtime-binding-v1.json as the binding authority. The existing execution owner is 4citeB4U/Leeway-Runtime-Fabric at the verified source baseline recorded by that binding. Do not create a second Runtime Fabric, Parallel Workplane, Agent Lee identity, persistent job queue, worker registry, supervisor, or event bus for this purpose while the canonical owners are recoverable.
The canonical path is:
Parent Agent Lee control plane → leeway-parallel-workplane → LeeWay Runtime Fabric → automation-runtime durable job state → LeeWay Runtime Supervisor → existing Agent Lee Runtime / Bridge Runtime adapter → Veritas → receipt → Learning Ledger.
A host may claim persistent execution only after it proves the configured adapter can authenticate to the canonical Runtime Fabric, the runtime accepted a stable workId, and inspectable runtime state shows the work actually advanced. Repository presence, a configured endpoint, a returned queue object, or source-level CI is insufficient by itself.
If the active host cannot reach/authenticate to the bound Runtime Fabric, classify persistent execution UNAVAILABLE or BLOCKED at that adapter boundary and retain ordinary conversation plus real in-turn parallelism. Never simulate a background worker.
Creator controls map to the canonical runtime transitions PAUSE, CANCEL, RETOOL, CONTINUE/RESUME, and SUPERSEDE. A side question preserves the parent objective and current workId; it does not silently cancel or rewrite the job.
Formula/context probes
For each parallel plan ask: What are we not discovering? What needs enhancement? Which jobs are truly independent? What shared state can conflict? What can be delegated? What must remain with the parent? How can the Creator interrupt safely? What evidence lets the parent retool or merge correctly?
Final route
Creator conversation ↔ Parent Agent Lee control plane → Skill Orchestrator → Parallel Workplane → bounded workers/providers → checkpoints → Veritas → merge → receipt → learning.