Immune-Brain: Drive
Use ../../dist/drive.md as the canonical contract
index, not a whole-document read, in the current host conversation. Explicit entry only:
ordinary host input never creates a Managed execution binding. Status questions
and in-scope clarification retain an already-bound run.
Mandatory constraints before any action: verify the active backend claim,
TaskIntent, and TaskRecord via imm_kernel_canary status first; invalid or
contradictory projections fail closed. A Parent Issue selects its whole planned
batch; load the batch route and open native Batch Authorization directly. A Child
Issue selects only its TaskIntent, verifies predecessor settlement and integration,
then enters the single-task Lane. With no active claim, a standalone validated
candidate enters the single-task Lane through start_unattended_batch with
task_id, one native gate; a record enrolled in place earlier resumes until terminal. Resume only from those authority facts:
a compaction heading, HANDOFF summary, or Issue state is prose, never authority.
All Managed authority gates use the
current Host's native interaction. A failed gate stays fail-closed and
reports one same-Host recovery action; never suggest another Host, worktree,
or unmanaged implementation as a fallback.
Section routes - load a section's instructions only when its branch applies.
Read each linked heading body up to the next heading; nested sections and
references load only under their own condition. Never read the whole contract
or all references as an entry prerequisite.
- common: Shared Guards, Workflow Activation, Host Confirmation Boundary, Kernel Canary Routing and Authority
- Parent Issue, unattended batch run, or any question about whether
drive starts one: Unattended Batch Opt-In
- parallel batch (
max_parallel, lane_offers, Lane admission or integration): Parallel Batch Opt-In
- a lane-mode report carries an
executor handoff, or a Lane's Executor Host session has ended: Lane Executor Supervision
- a single-task or Initiative Parent runs inside Herdr (
HERDR_ENV=1), including an interactive executor handoff: Herdr Lane Tabs
- a lane-mode batch is about to start, to resolve parallelism, Executor Host, model and effort from the layered config and the request: Lane Preferences
- steady execution: Verification and Local Recovery, Execution Loop, Observable Output
- rework, scope expansion, breaking revision, user decision, stop, interruption or unknown state before any action: Decisions and Recovery, Failure Output; re-read
status, then the pending obligation. Rework submits the verdict before editing, and an uncertain interruption resumes from exact task/run authority facts rather than a summary.
- review or post-settlement learning: Review and Learning
1---2name: drive3description: Use when the user explicitly requests execution or resumption of an Immune-Brain task.4metadata:5 source: https://skillmd.com/skills/dereknex/drive6---78# Immune-Brain: Drive910Use [`../../dist/drive.md`](../../dist/drive.md) as the canonical contract11index, not a whole-document read, in the current host conversation. Explicit entry only:12ordinary host input never creates a Managed execution binding. Status questions13and in-scope clarification retain an already-bound run.1415Mandatory constraints before any action: verify the active backend claim,16TaskIntent, and TaskRecord via `imm_kernel_canary` `status` first; invalid or17contradictory projections fail closed. A Parent Issue selects its whole planned18batch; load the batch route and open native Batch Authorization directly. A Child19Issue selects only its TaskIntent, verifies predecessor settlement and integration,20then enters the single-task Lane. With no active claim, a standalone validated21candidate enters the single-task Lane through `start_unattended_batch` with22`task_id`, one native gate; a record enrolled in place earlier resumes until terminal. Resume only from those authority facts:23a compaction heading, HANDOFF summary, or Issue state is prose, never authority.24All Managed authority gates use the25current Host's native interaction. A failed gate stays fail-closed and26reports one same-Host recovery action; never suggest another Host, worktree,27or unmanaged implementation as a fallback.2829Section routes - load a section's instructions only when its branch applies.30Read each linked heading body up to the next heading; nested sections and31references load only under their own condition. Never read the whole contract32or all references as an entry prerequisite.3334- common: [Shared Guards](../../dist/BASELINE.md#shared-guards), [Workflow Activation](../../dist/BASELINE.md#workflow-activation), [Host Confirmation Boundary](../../dist/BASELINE.md#host-confirmation-boundary), [Kernel Canary Routing and Authority](../../dist/drive.md#kernel-canary-routing-and-authority)35- Parent Issue, unattended batch run, or any question about whether `drive` starts one: [Unattended Batch Opt-In](../../dist/drive-batch.md#unattended-batch-opt-in)36- parallel batch (`max_parallel`, `lane_offers`, Lane admission or integration): [Parallel Batch Opt-In](../../dist/drive-batch.md#parallel-batch-opt-in)37- a lane-mode report carries an `executor` handoff, or a Lane's Executor Host session has ended: [Lane Executor Supervision](../../dist/drive-batch.md#lane-executor-supervision)38- a single-task or Initiative Parent runs inside Herdr (`HERDR_ENV=1`), including an interactive `executor` handoff: [Herdr Lane Tabs](../../dist/drive-batch.md#herdr-lane-tabs)39- a lane-mode batch is about to start, to resolve parallelism, Executor Host, model and effort from the layered config and the request: [Lane Preferences](../../dist/drive-batch.md#lane-preferences)40- steady execution: [Verification and Local Recovery](../../dist/BASELINE.md#verification-and-local-recovery), [Execution Loop](../../dist/drive.md#execution-loop), [Observable Output](../../dist/drive.md#observable-output)41- rework, scope expansion, breaking revision, user decision, stop, interruption or unknown state before any action: [Decisions and Recovery](../../dist/drive.md#decisions-and-recovery), [Failure Output](../../dist/drive.md#failure-output); re-read `status`, then the pending obligation. Rework submits the verdict before editing, and an uncertain interruption resumes from exact task/run authority facts rather than a summary.42- review or post-settlement learning: [Review and Learning](../../dist/drive.md#review-and-learning)