flemming-it
f411e7abf0
All checks were successful
CI / Linux x86_64 (Forgejo) (push) Successful in 2m1s
The previous workflow was a copy of the pre-SDK template — it did the own-repo checkout but had no provision for fetching fai-module-sdk from git.flemming.ws/fai/module-sdk. After the v0.3.0 SDK migration, every CI run failed at the cargo fetch stage because the runner had no credential for the cross-org private repo. Adopt the same pattern that text-extract and llm-chat already use: a MODULE_SDK_PAT actions secret, CARGO_NET_GIT_FETCH_WITH_CLI=true, and a 'git config url.X.insteadOf Y' that injects the token into any outgoing git.flemming.ws URL transparently. Bumps the module to 0.3.2 (patch — CI infrastructure only, behaviour unchanged). Signed-off-by: flemming-it <sf@flemming.it> |
||
|---|---|---|
| .forgejo/workflows | ||
| src | ||
| tests | ||
| .gitignore | ||
| Cargo.toml | ||
| LICENSE | ||
| module.yaml | ||
| README.md | ||
| rust-toolchain.toml | ||
orchestrator-llm
F∆I orchestrator module — turns natural-language goals into
structured execution plans (fai_hub::plan::Plan JSON).
Status
v0.1.0 — deterministic stub. Always returns a structurally
valid plan that creates a single debug.echo flow regardless of
the goal. Useful as a smoke test for the full module → plan →
fai plan apply path.
v0.2.0 (next) — replaces the stub with an actual LLM call to a
configured endpoint (Ollama or OpenAI-compatible) once the F∆I
platform exposes outbound HTTP to permitted modules via wasi-http.
Capability
orchestrator.plan@0.1.0
Inputs
| Name | Type | Description |
|---|---|---|
goal |
text | Natural-language goal |
available_capabilities |
text (JSON list) | Optional. Capabilities currently installed in the hub. |
store_capabilities |
text (JSON list) | Optional. All capabilities the hub knows about. |
Outputs
| Name | Type | Description |
|---|---|---|
plan |
json | Plan JSON deserializable by fai_hub::plan::Plan |
Permissions
None. The deterministic stub does not call out. v0.2.0 will
declare net: <llm-endpoint> once the platform supports it.
Build
cargo build --release --target wasm32-wasip2
The built WASM lands at
target/wasm32-wasip2/release/orchestrator_llm.wasm.
Test
Host-side unit and integration tests exercise the pure plan-building logic (no WASM build required for tests):
cargo test
Use from a flow
schema_version: 1
name: plan-from-goal
inputs:
goal: text
steps:
- id: orchestrate
use: orchestrator.plan@^0
with:
goal: $inputs.goal
outputs:
plan: $orchestrate.plan
The plan output is JSON — pipe it through fai plan apply -
to execute it.
License
Apache-2.0. See LICENSE.