Skip to main content
A Workflow draft has five authored parts: intent, Rune Program source, an entrypoint, resource bindings, and input/output schemas. The source is canonical. The outline and topology are compiler-derived projections for review.

​
Choose an authoring mode

​
Intent-first

Use Generate from intent for a new Workflow, or the Intent section to change an existing draft. Describe the outcome and constraints. Noorle generates or patches the Program against the draft’s current bound surface and can repair compiler diagnostics within a bounded attempt loop. Generation changes the draft only. Inspect the source, schemas, bindings, topology, and diff before publishing.

​
Advanced source

Use Blank advanced draft or the Advanced section when you want to edit Rune directly. A Program has a public async entrypoint, normally main, and returns a JSON-compatible value. The Declarations / help panel is the source of truth for the host functions and resource handles available to that draft. Copy handles from there; do not invent them from display names.

​
Bind resources

The Bindings section supports: The server derives opaque handles from immutable resource identity. A resource rename therefore does not redirect a call. Removing or deactivating a required binding makes validation or execution fail closed rather than targeting a different resource. Self-binding and child-Workflow cycles are rejected. A child Workflow must be active when selected.

​
Define schemas

Use Schemas for input and output JSON Schema. Input is checked before a run is committed. The output schema is compiled into the published artifact and documents the Program’s return contract. Keep schemas with the draft: changing a schema and publishing creates a new version, while existing runs retain the schema and artifact they started with.

​
Validate before publishing

The Overview section renders the compiler-derived topology and effect manifest. Use it to review what the source can call and where it can wait. It is not an editable graph.

​
Publish

Publish compiles the saved draft and seals a new immutable version. The version records the Program artifact, source identity, schemas, bound resource identities, execution outline, policy, topology, and validation evidence. Publishing does not automatically alter an in-flight run. Select Activate on the version that should become the default for new starts. You can later activate an older published version without rewriting it.

​
Current authoring boundaries

  • There is no visual graph editor and no node palette.
  • Program calls must use bound resources; ambient network, filesystem, and secret access are unavailable.
  • Use a connector for credentialed external APIs. Do not embed secrets in source or default input.
  • Await async resource calls and durable waits exactly as shown by the declarations panel.
  • The current Rune surface has no general parallel-join helper; awaited calls execute in source order.
  • Only a published Workflow can use durable waits. A transient Agent-authored procedure cannot sleep, wait for approval, receive a signal, or receive a callback.

​
Next