docs(SKILL): HTTP-only agent contract + the cargo data channel; local client -> cyberware_dev - #227
Merged
Merged
Conversation
… move to cyberware_dev; document the cargo data channel
The ouroboros pass on the agent-facing contract. The root SKILL.md now describes ONE
method — the pure wire protocol: GET /catalog -> POST /govern -> per-run WebSocket, with
exod running each step confined server-side (intent in, status out; you run nothing). Two
gaps that caused real confusion are now documented:
- var_values: a delegated run's VALUES ride the per-run WS step_request (the claim plane
stays KEYS-only), re-gated on the actor's params ACL axis; secrets stay *_FILE.
- the cargo data channel: the wire is status-only, so a step that returns DATA writes it
under the /cyberware_cargo bind (claim carries cargo:ro|rw) and the caller reads the
artifact off the shared mount. Verified end-to-end (delegated fleetbook/retrieve OUT).
The cooperative grant/step_result run-from-your-own-registry method + the ./govd-client
CLI live entirely in cyberware_dev/SKILL.md — the local-dev path an external agent never
needs.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The root SKILL.md (the agent-facing govd/exod contract) now describes one method — the pure wire protocol:
GET /catalog->POST /govern-> per-run WebSocket, exod executing each step confined server-side (intent in, status out; the agent runs nothing).Two things that caused real confusion are now documented:
var_values— a delegated run's VALUES ride the per-run WSstep_request(the/governclaim stays KEYS-only), re-gated on the actor'sparamsACL axis; secrets stay*_FILE./cyberware_cargobind ("cargo":"ro"|"rw"on the claim) and the caller reads the artifact off the shared mount. Verified end-to-end (delegatedfleetbook/retrievewithOUT).The cooperative (
grant/step_result, run-from-your-own-registry) method and the./govd-clientCLI now live entirely incyberware_dev/SKILL.md— the local-dev path an external agent never needs.🤖 Generated with Claude Code