lda.chat/lda-wf
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

workflow ref

Browse Source
This commit is contained in:
lda
2026-05-25 03:27:30 +07:00 Verified
parent 16d5204fbc
commit 84b931f821
11 changed files with 227 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/authoring_sketch.md
+4 -2
View File
@@ -254,8 +254,10 @@ Today there are two different authoring paths:
native parent state.
- `subgraph_ref` builds a native `SubgraphNode` contract from a compiled
`Workflow`: child input schema, output schema, and workflow outcomes are
copied into the boundary. Runtime execution still raises until native
subgraph scopes are implemented.
copied into the boundary. The workflow reference is structural: local
workflows use `{"name": "child"}`, saved artifacts can use
`{"artifact_id": "child", "version": 1}`. Runtime execution still raises
until native subgraph scopes are implemented.
- `WorkflowBuilder.subgraph(...)` is the builder-facing version of
`subgraph_ref`: it appends the native boundary step and returns it as a
`StepRef` for `connect()` / `set_entry_point()`.
docs/superpowers/specs/2026-05-24-native-subgraphs-design.md
+9 -6
View File
@@ -64,8 +64,11 @@ class SubgraphNode(BaseModel):
```
Current implementation status: `wf_core` has a first placeholder
`SubgraphNode`, but `workflow` is still a plain string reference. The placeholder
also carries `input_schema` and `output_schema` so validation can check parent
`SubgraphNode`. Its `workflow` field is a structural `WorkflowRef`: local
compiled workflows use `{"name": "child"}`, while saved artifacts can use
`{"artifact_id": "child", "version": 1}`. Legacy strings still parse as input,
but saved graphs should persist the structural shape. The placeholder also
carries `input_schema` and `output_schema` so validation can check parent
bindings before native execution exists. Runtime execution intentionally raises
until a later slice adds child scope/frame execution.
@@ -316,10 +319,10 @@ child = parent.subgraph(
This copies the compiled child workflow contract into a core `SubgraphNode`,
appends it to the builder, and returns the step for normal routing. It does not
make the child executable yet. `workflow` is still a string reference inside the
core model; higher layers need a structural workflow reference before
saved/deployed workflow dependencies become stable. The lower-level
`subgraph_ref(...)` helper exists for code that wants only the core step object.
make the child executable yet. The core `workflow` field is structural, but
higher layers still need dependency resolution before saved/deployed workflow
refs can run. The lower-level `subgraph_ref(...)` helper exists for code that
wants only the core step object.
Possible API: