SoherAgent · 4 of 5 · Deliver and review
Sanitized recreation · reviewed /yolo behavior
Scene 1 of 14 — Attach to V1-S1
Automatic delivery attaches to the exact authorized batch.
No ask_user dialogs inside a valid batch
authorityDigest and exact batch matchaccepted
leaseExact V1-S1 lease · one active owner acquiredV1-S1
outsideV1-S2 and destructive actionsfenced
›
Scene 2 of 14 — Map T01 sequentially
Wayfinder maps approved targets sequentially.
Maximum mapping concurrency = 1
mappingT01 Cited contract extraction1 active
waitingT02 Grounded summary + human reviewstarts after T01 map
excludedV1-S2 Engineering adoption kitnot authorized
›
Scene 3 of 14 — Save a runtime checkpoint
The parent records a runtime checkpoint before dispatch.
Resumable state does not widen authority
checkpoint: phase=implement
ticket=T01
authority=digest-bound
resume=exact target only
Mapping max · 1 observed
Lease owner · 1
Replay · completed work cannot re-enter
Next batch · off
›
Scene 4 of 14 — Reproduce the failure
The authorized Pi implementer loads implement-obsidian-ticket inside a restricted child.
Child may edit only its leased code scope
yolo-implementer · T01restricted writer
Loaded implement-obsidian-ticket for the exact leaseRan focused contract-citation testObserved: renewal notice date has no source span
$ node --test test/contract-citations.test.mjs
✗ expected source citation; received empty
›
Scene 5 of 14 — Apply a narrow fix
The implementer makes one narrow fix and proves it.
No speculative refactor
yolo-implementer · T01returning to parent
Updated the existing contract field mapper onlyRequired a source span before showing the extracted dateFocused test: PASS · related test: PASS
Child sessionChanged files and checks returned. No commit, push, deploy, vault mutation, or delegation.
›
Scene 6 of 14 — Validate and move the note
The parent inspects, tests, integrates, and updates workflow state.
Canonical Obsidian mutation is parent-only
inspectScope and diffpassed
testsFocused and required checkspassed
integrateCanonical workspace + same batch note implement → reviewparent-owned
obsidianT01 → review-readyparent-owned
›
Scene 7 of 14 — Run standards review
The authorized Pi reviewer loads review-obsidian-ticket in a fresh read-only child.
Read-only child role · same-agent limitation accepted
yolo-reviewer · standards passread-only reviewer
Loaded review-obsidian-ticket for this exact ticketChecked repository, security, scope, and maintainabilityNo unrelated files or authority changes
›
Scene 8 of 14 — Run specification review
The same review remains separate for specification fit.
Acceptance criteria checked independently
yolo-reviewer · specification passread-only reviewer
A1 key obligation includes a source citation: PASSA2 renewal date includes a source citation: PASSA3 weakly supported extracted field uses Needs review: mismatch
›
Scene 9 of 14 — Return changes required
Review returns CHANGES_REQUIRED with a bounded finding.
Not a general redesign request
BoundaryCHANGES_REQUIRED
The renewal notice date still appears when its source support is too weak instead of using the required Needs review fallback.
The renewal notice date still appears when its source support is too weak instead of using the required Needs review fallback.
In scope · guard the extracted field and show Needs review
Out of scope · grounded Q&A, model change, production connectors
Normal remediation · cycle 1 of 3
›
Scene 10 of 14 — Remediate cycle 1 of 3
Automatic remediation uses the same lease boundary.
Cycle 1 of 3 · normal CHANGES_REQUIRED path
yolo-implementer · T01 remediationrestricted remediation
Verified CHANGES_REQUIRED finding and same authorityGuarded the weakly supported extracted date and added Needs reviewFocused acceptance tests: PASS
parentDiff and tests revalidatedreview-ready
›
Scene 11 of 14 — Pass fresh review
Fresh phase-separated read-only review returns PASS.
Same-agent limitation accepted · both passes rerun
yolo-reviewer · fresh reviewread-only reviewer
Standards pass: PASSSpecification pass A1–A3: PASSNo scope or authority findings
SoherAgentPASS
›
Scene 12 of 14 — Move the note to T02
T01 completes; T02 follows in the same exact batch.
One story path · not two simultaneous batches
parentCanonical batch note: review T01 → implement T02canonical
mappingT02 mapped after T01max 1
implementGrounded summary + human review record + testsreturned
reviewStandards + specificationPASS
›
Scene 13 of 14 — Complete the batch note
The parent reconciles and archives the finished batch.
Completion must be proven
reconcileCanonical batch note → Completed after T01 and T02 passconsistent
archivePost-route archive and link checksfinished
leaseReleased after completionsettled
reasoncompletion-provenrecorded
›
Scene 14 of 14 — Stop before V1-S2
Automation stops at the next batch boundary.
Ready later ≠ authorized now
SoherAgentV1-S1 is complete. V1-S2 Engineering adoption kit is eligible for a new handoff and authorization decision, but automatic progression is not authorized.
Finished · T01 + T02
General cap · parallel targets ≤ 2 when explicitly eligible
V1-S2 · not started
Commit/push/deploy · not authorized
›