specverb-gen: dispatch on transport, generate exec-dialect consumers #131

Closed
opened 2026-06-10 18:22:16 +00:00 by coilysiren · 1 comment
Owner

What

Teach the no-code driver (specverb-gen / specdrv) the exec transport: dispatch on the Guardfile's body (spec+auth -> specverb, exec -> execverb) so an exec-dialect consumer gets the same uv-style gen/lock/build/run surface ward-kdl has - no hand-written Go, no go.mod in the consumer.

Differences from the HTTP path: no swagger lock (the binary embeds only the guardfile), no SSM resolver requirement (auth is the wrapped binary's own), and the generated main.go mounts execverb.Mount under the audit Wrap.

Why

ward's exec surfaces (git, admin/doctor remote-exec, later brew/docker/systemctl) should be authored as committed guardfiles exactly like the HTTP surface, with the reference doc emitted at build time. Follow-up named in docs/execverb.md; consumer ask in coilyco-flight-deck/ward#81.

Part of #123.

## What Teach the no-code driver (`specverb-gen` / specdrv) the exec transport: dispatch on the Guardfile's body (`spec`+`auth` -> specverb, `exec` -> execverb) so an exec-dialect consumer gets the same uv-style gen/lock/build/run surface ward-kdl has - no hand-written Go, no go.mod in the consumer. Differences from the HTTP path: no swagger lock (the binary embeds only the guardfile), no SSM resolver requirement (auth is the wrapped binary's own), and the generated main.go mounts `execverb.Mount` under the audit Wrap. ## Why ward's exec surfaces (git, admin/doctor remote-exec, later brew/docker/systemctl) should be authored as committed guardfiles exactly like the HTTP surface, with the reference doc emitted at build time. Follow-up named in docs/execverb.md; consumer ask in https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/81. Part of https://forgejo.coilysiren.me/coilyco-flight-deck/cli-guard/issues/123.
Author
Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.
coilysiren 2026-06-17 08:23:17 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/cli-guard#131
No description provided.