root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

FN-5769: clarify workflow IR v1 agent-call semantics

Browse Source 
Document that workflow IR v1 keeps agent-call and typed-edge semantics as conventions rather than a 1.1 schema bump.

- replace the deferred-v1.1 note with the FN-5769 evaluation outcome
- record that prompt config and edge.condition remain the canonical v1 representation for parity rollout

Files changed:
 docs/workflow-steps.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Fusion-Task-Id: FN-5769

Fusion-Task-Lineage: 341ce4fe-d87d-4c25-a1fc-652ccfbc2e94
This commit is contained in:
gsxdsm
2026-06-02 13:37:33 -07:00
parent dab1569ac3
commit bd3190ba19
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/workflow-steps.md
View File

@@ -55,7 +55,7 @@ Current reconciliation in v1:
- `agent-call` semantics are represented using existing `prompt` nodes with `config` fields (for example stage/role metadata). - `agent-call` semantics are represented using existing `prompt` nodes with `config` fields (for example stage/role metadata).
- Typed-edge semantics are represented using `condition` token conventions. - Typed-edge semantics are represented using `condition` token conventions.
Potential first-class schema support for `agent-call`/typed edges is deferred to a follow-up IR extension task (v1.1 candidate), not part of v1 contract changes. FN-5769 evaluated whether those conventions required a `1.1.0` schema bump and recorded the answer as **no**: the current `prompt` + `config` and canonical `edge.condition` token conventions are sufficient for the parity-critical interpreter rollout, so they remain the canonical v1 contract until a future consumer needs stronger schema-level validation or discoverability.
## What They Are ## What They Are