Review delegated work across agent runtimes.
The problem
A delegation practice tied to one assistant breaks when the lead changes runtime. Child reports also need a review step before their suggestions become guidance.
An explanatory exhibit
A report returns to the captain
Synthetic task and report flow. No real panes, workers or sessions are displayed.
- 01
Captain
Assign a bounded investigation
- 02
Worker
Return findings and supporting evidence
- 03
Review
Accept result; assess guidance proposal
Inspect the consequence
Evidence supports the proposal
Review and accept
The captain can adopt a useful change after checking its basis.
The proposal overgeneralizes
Decline the rule change
A successful task does not automatically establish a general instruction for future work.
What this makes possible
I built a shared captain protocol for evidence, worker reports, handoffs and reviewed feedback, while keeping each runtime’s coordination tools.
Source information sheet
Evidence, implementation & history Implementation inspected
What I checked
The two artifact-rule corrections are in v1.0.0, commit 666911e (18 September 2026). The archived independent review and follow-up source check support this historical example. Captain review is not necessarily human approval; no live screenshot-path test or current fleet installation is claimed.
Research cut: 15 October 2026. Source areas below are from forge/helm. Private conversation references are retained in the research ledger and are not published here.
Implementation decisions
Helm separates the shared reporting and learning protocol from the runtime mechanics. Claude/Bosun and native Codex coordination can use their own tools while following the same evidence and handoff expectations.
An independent review of the first stable protocol exposed conflicting report paths and a screenshot-staging rule that assumed all tools behaved alike. The captain corrected the guidance; a second source check verified both changes.
A path through the feature
- Give a worker a bounded task
Specify its scope and the evidence needed in its report.
- Review before accepting
Check the report and proposed guidance changes. A captain can accept useful feedback or decline a change that is unsupported.
Source areas
helm/README.mdhelm/protocol.mdhelm/rules/retro-loop.mdhelm/rules/handoff-lifecycle.mdhelm/riders/output-file.md
The small explanatory exhibit uses invented records to describe the mechanism. Separate recordings and working examples carry their own evidence notes.
Recorded history
Dates describe the researched record, rather than today’s deployment.
Sharing a captain learning loop across runtimes