Skip to content

OpenUdon

UWS logo

OpenUdon is the public UWS workflow authoring, review, package, and executor-handoff tool. It turns reviewed project briefs into deterministic workflow packages and hands approved packages to a trusted executor boundary.

OpenUdon can be used directly by an operator or under optional Symphony-managed orchestration. In both modes, generated artifacts stay untrusted until validation, review, approval, and package digest checks pass.

What OpenUdon Owns

  • Project briefs, templates, guided iCoT authoring, and eval fixtures.
  • OpenAPI-backed UWS artifact generation from reviewed inputs.
  • Review evidence, quality reports, approval templates, package digests, and handoff manifests.
  • Local trusted-runner enforcement before invoking an external executor.

OpenUdon does not own public workflow semantics, generic OpenAPI/UWS execution, Symphony workflow state, or concrete infrastructure authoring. Those boundaries are summarized on the Related page.

Basic Flow

project.md
  -> workflows/intent.hcl
  -> workflows/workflow.hcl and workflows/workflow.uws.yaml
  -> expected plan, quality, review, and handoff artifacts
  -> approval JSON with package digest
  -> openudon run trusted executor handoff

Operator Commands

go run ./cmd/icot --example ./examples/<name>
go run ./cmd/openudon synthesize --example ./examples/<name>
go run ./cmd/openudon build --example ./examples/<name>
go run ./cmd/openudon assess --example ./examples/<name>
go run ./cmd/openudon approval-template --example ./examples/<name> --state approved_for_sandbox --reviewer "Reviewer Name"
go run ./cmd/openudon run --example ./examples/<name> --tier sandbox --approval approvals/<name>.json --dry-run

Use Authoring for the two authoring paths, Tutorial for fixture-based walkthroughs, and Handoff for the review and execution boundary.