feat(workflows): dynamic sub-workflow command registration, tool projection & mutual exclusion #8

Closed
opened 2026-09-09 10:08:48 +00:00 by larandar · 1 comment
Owner

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 --help from input.schema, expose simultaneous agent tools as wf_<name>, bind execution context to <workflow>@<impl> with mutual exclusion, and validate every result against mandatory structured output.schema.

Tasks

  • 4.1 Register dynamic wf <name> commands and synthesize help from input.schema.
  • 4.2 Project wf_<name> tools, enforce <workflow>@<impl> mutual exclusion, and validate structured output.schema results.

Gherkin Specification Delta

must.contracts.ting-workflows.executor.subworkflow-dynamic-registration

Scenario: Register a sub-workflow from its input schema

  • GIVEN a sub-workflow with an input.schema
  • WHEN the executor loads the catalog
  • THEN it exposes a wf <name> command and synthesized --help describing the schema
  • AND it projects the command as the simultaneous agent tool wf_<name>.

must.contracts.ting-workflows.executor.subworkflow-implementation-binding

Scenario: Enforce implementation binding and output validation

  • GIVEN a workflow selected as <workflow>@<impl>
  • WHEN another implementation is requested concurrently or output violates output.schema
  • THEN the executor rejects the request with a structured validation failure.
## 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 `--help` from `input.schema`, expose simultaneous agent tools as `wf_<name>`, bind execution context to `<workflow>@<impl>` with mutual exclusion, and validate every result against mandatory structured `output.schema`. ## Tasks - 4.1 Register dynamic `wf <name>` commands and synthesize help from `input.schema`. - 4.2 Project `wf_<name>` tools, enforce `<workflow>@<impl>` mutual exclusion, and validate structured `output.schema` results. ## Gherkin Specification Delta ### must.contracts.ting-workflows.executor.subworkflow-dynamic-registration **Scenario: Register a sub-workflow from its input schema** - **GIVEN** a sub-workflow with an `input.schema` - **WHEN** the executor loads the catalog - **THEN** it exposes a `wf <name>` command and synthesized `--help` describing the schema - **AND** it projects the command as the simultaneous agent tool `wf_<name>`. ### must.contracts.ting-workflows.executor.subworkflow-implementation-binding **Scenario: Enforce implementation binding and output validation** - **GIVEN** a workflow selected as `<workflow>@<impl>` - **WHEN** another implementation is requested concurrently or output violates `output.schema` - **THEN** the executor rejects the request with a structured validation failure.
Author
Owner

Superseded by 1-feature deliverable decomposition per freeholder ruling (issues #11+).

Superseded by 1-feature deliverable decomposition per freeholder ruling (issues #11+).
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.

Reference
Ting/workflows#8
No description provided.