Buzz + Hermes: A Governed Capability Bridge

A stable capability request lets the Buzz employee remain accountable while the executor changes underneath it.

The Buzz owner issues a bounded request, Hermes or another provider executes it, the provider returns an artifact and receipt, and the Buzz owner continues the job. Provider failure does not become false completion.

1. 1Define capability, inputs, outputs, allowed tools, side effects, timeout, and receipt fields.
2. 2Keep the parent job in Buzz.
3. 3Send the same contract to one provider.
4. 4On evidenced failure, reroute the unchanged request.
5. 5Return the artifact to the parent before any approval state changes.

• The Buzz parent remains named as owner.
• The external executor produces the declared artifact and receipt.
• Provider identity and failure state are recorded.
• Independent inspection evaluates the actual returned artifact.

• Provider accepts work but times out without artifact or receipt.
• Fallback changes the request and makes results incomparable.
• The orchestrator creates the content instead of returning execution to the owner.

Reuse the bridge for another bounded job before calling the capability broadly proven.

• How Buzz Agents collaborate
• Buzz Agent harnesses
• What Is Buzz?
• Buzz Agent troubleshooting
• Run Buzz Agents reliably