specverb-gen: dispatch on transport, generate exec-dialect consumers #131
Labels
No labels
burndown-2026-06
sunday-sprint
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/umbra#131
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.Mountunder 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 coilyco-flight-deck/cli-guard#123.
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.