Getting started

Begin at the capability boundary.

Runic Artifex is not one mandatory stack. Choose an independent product, then add integrations owned by that product when your application needs them.

01 · Choose

Pick the owner

Need a desktop browser host? Start with CsWebUi.
Need application composition? Start with Runic Toolkit.
Need deterministic backend operations? Start with Runic Flow.
Need localization contracts and builds? Start with Runic Translations.
Need a translator-facing workspace? Use Runic Translations Editor.

02 · Inspect

Use the candidate status, not an old version list

CsWebUi is already public. Other package families are refreshing candidates from their final source commits. The catalog names package ownership now and will show installable versions only after matching public artifacts are ready.

03 · Integrate

Let adapters point inward

Runic Flow remains headless and frontend-neutral. RunicFlow.ApplicationBridge depends on Flow and Toolkit Application Bridge and is released by Flow.

04 · Verify

Keep the application in control

Pin exact product versions during the preview.
Publish the final application with trimming and NativeAOT when supported.
Do not add NuGet packages.lock.json; application package managers own resolution.
Keep ordinary npm package-lock.json files for applications.

Public launch is gated

Source visibility can precede registry publication. Package commands will be published only after fresh candidates, downstream consumers, trusted publishers, and the documentation review all pass.

Continue with the Application Bridge guide, the package catalog, or the dependency rules.