Sirius A product of
Documentation Contact

Build

Studio

Studio is the transformation workbench. A mapping is a project, not a single anonymous script.

Anatomy

  • A workspace has a runtime pack, files (one entrypoint), and samples.
  • The active sample arrives as msg (msg.raw, msg.content_type, and a parsed tree when the format is recognized).
  • Your script must assign result. Forgetting that is the usual first-run error.
result = { message: msg.message };

The same workbench opens from a transform node on the Build canvas.

Languages

JavaScript, TypeScript, Python, Lua, Go, Tcl, Java, Rust, C, C++, and WASM share one sirius.* catalog. Autocomplete and hover docs come from that catalog, so the help you see in the editor is the API you can call.

Compiled packs build to WASM with a local toolchain — nothing leaves your network.

Samples and tests

Import a payload; Sirius detects common content types (JSON, HL7, X12, FHIR, and others). Attach a golden expectation to turn a sample into a regression test. Run the suite before you promote a milestone (a content-hashed snapshot). Promotion can require a green suite.

Collaboration

Workspaces support live presence, an optional project terminal, and a SQL console against a configured database connector. Writes in that console commit for real — treat them as production operations.

Walkthrough: Write a transform. Every sirius.* call: Host API. Programmable surface: Studio API.