feat(workflows): dynamic sub-workflow command registration, tool projection & mutual exclusion #8
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
Reference
Ting/workflows#8
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?
Proposal
Register sub-workflows dynamically from their input schemas and project them consistently into agent tools while enforcing implementation binding and output contracts.
Design
Synthesize
--helpfrominput.schema, expose simultaneous agent tools aswf_<name>, bind execution context to<workflow>@<impl>with mutual exclusion, and validate every result against mandatory structuredoutput.schema.Tasks
wf <name>commands and synthesize help frominput.schema.wf_<name>tools, enforce<workflow>@<impl>mutual exclusion, and validate structuredoutput.schemaresults.Gherkin Specification Delta
must.contracts.ting-workflows.executor.subworkflow-dynamic-registration
Scenario: Register a sub-workflow from its input schema
input.schemawf <name>command and synthesized--helpdescribing the schemawf_<name>.must.contracts.ting-workflows.executor.subworkflow-implementation-binding
Scenario: Enforce implementation binding and output validation
<workflow>@<impl>output.schemaSuperseded by 1-feature deliverable decomposition per freeholder ruling (issues #11+).