SoherAgent · 3 of 5 · Authorize one batch
Sanitized recreation · reviewed /yolo behavior
Scene 1 of 14 — Enter /yolo on
The final planning route is committed; now open session controls.
Planning route is not execution authority
SoherAgentRoute saved: standalone. No handoff or batch authority exists.
You/yolo on
›/yolo on
Scene 2 of 14 — Select capabilities
Select session capabilities in the native /yolo selector.
Native selector · not ask_user
Select YOLO capabilities for this session
[x]Permission auto-approvalAutomatically approves permission results marked “ask”. Explicit deny rules and tool safety rails remain active.
[x]Obsidian auto-writeCommits non-destructive Obsidian changes without prompting. Auto-destroy remains a separate capability.
[ ]Obsidian auto-destroy — DANGERSkips per-operation destructive prompts for permanent note/folder deletion, full-note replacement, and empty-trash actions. Session-only, still safety-checked, and never selected by Full YOLO.
[x]Wayfinder auto-route optimizationUses metadata-first selective hydration for explicit manual workflow commands and Full YOLO delivery. Ordinary agent chat remains unchanged.
[x]Session auto-continuityEnables 85% checkpoint-before-compaction with exact Wayfinder recap, records supported manual workflow checkpoints, and resumes recorded inactive sessions during Full YOLO delivery.
> [x]Full YOLO deliverySelects every non-destructive supporting capability and automatically processes only explicitly authorized YOLO batches. Auto-destroy is never selected. No commits, pushes, deployments, destructive actions, or next-batch progression.
↑↓ navigate · Space toggle · Enter apply · Esc cancel
Scene 3 of 14 — Start a new batch
Full delivery is on, with persistent boundaries visible.
Capabilities still do not authorize a batch
Choose Full YOLO delivery work
>Start a new batchDiscover eligible unhanded batches; existing resumable batches remain paused.
CancelLeave Full YOLO delivery paused.
↑↓ navigate · Enter select · Esc leave paused
Scene 4 of 14 — Select one-batch discovery
Move from safe-default Cancel to one-batch discovery.
Discovery prepares work · it does not authorize it
Safe default was Cancel · user pressed ↓ to review the bounded discovery choice
Confirm new-batch discovery
CancelLeave all delivery paused and queue no handoff command.
>Discover exactly one new batchDiscover and prepare one eligible batch only; do not authorize parallel batches.
↑↓ navigate · Enter select · Esc cancel
Scene 5 of 14 — Load the handoff workflow
The control extension loads the handoff skill automatically.
Injected skill · not typed by the user
Discovery submitted · exactly one new-batch discovery requested · no authority yet
Extension-loaded workflow: prepare-obsidian-handoff
Discover eligible approved work; prepare exactly one bounded batch.
loadedprepare-obsidian-handoffextension-injected
discoverApproved, dependency-ready frontierone batch only
›
Scene 6 of 14 — Discover V1-S1
Discovery finds exactly one eligible frontier.
V1-S2 remains later and ineligible
Discovery started · existing resumables remain paused · selection/discovery is not authority
eligibleV1-S1 · Contract insight MVPone batch
laterV1-S2 · Engineering adoption kitnot eligible
authorityNo batch authorized yetoff
›
Scene 7 of 14 — Choose the exact batch
Select the exact batch to prepare.
ask_user is separate from native /yolo controls
Scene 8 of 14 — Assign Pi to implement
Choose the compatible internal delivery worker; the planning preference was advisory.
Explicit handoff role · one leased batch
Scene 9 of 14 — Resolve reviewer availability
Preferred reviewer Hermes did not pass this batch’s immediate availability/access check, so choose a one-batch fallback or stop.
One-time override only · sticky preference stays Hermes
Scene 10 of 14 — Set post-block attempts
Set the separate post-block diagnosis policy.
Ticket-bound post-block authority · separate from normal review cycles
Scene 11 of 14 — Review the envelope
Build the exact authority envelope.
A digest-bound contract gates dispatch
Authorization envelope
typeexecution-batch-handoffexact contract
batchV1-S1 · cited extraction → grounded reviewonly scope
agentsPi (pi) implementer + Pi (pi) reviewerV1-S1 override
limitsnormal remediation ≤3 cycles; post-block attempts 2bounded
One-batch override · Pi reviews V1-S1; Hermes remains preferred
Independence warning · accepted for Pi in both assignments
Excluded · commit, push, deploy, publish, delete
automatic_next_batch · false; V1-S2 excluded
›
Scene 12 of 14 — Authorize V1-S1
Authorize only the envelope shown.
ask_user final authority decision
Scene 13 of 14 — Write the canonical note
The parent writes and validates canonical authority.
Workers never mutate Obsidian workflow state
parent writeOne canonical batch handoff note containing the authority envelope, then graph linkssequential writes
validateProvenance, digest, exact V1-S1 batch, Pi assignments, accepted independence warning, limits, and linkspassed
frontierT01 dependency-readypassed
outsideV1-S2 and destructive scopelocked
›
Scene 14 of 14 — Arm only V1-S1
Arm the exact batch and nothing else.
Later work still needs a new authorization
yolo_arm_new_batch
✓ authority digest accepted
✓ exact batch V1-S1 armed
✓ automatic delivery may begin
Authorized · V1-S1 only
Remediation · normal ≤3 cycles; post-block attempts 2
Auto-destroy · off
Next batch · not authorized
›