Server components
Use the exact Linux amd64 image references for this release. Review the migration plan before applying it to your intended database.
SETUP / ENTERPRISE 0.1.0-alpha.1
A clear next step.
For your actual setup.
You can try the extraction exercise right away. Running it inside Studio also needs an Enterprise installation and a connected Windows draft runner.
01 / NO ENTERPRISE SETUP
Get the first useful record.
Download the synthetic careers exercise, extract it, and run it with Node.js 24. Then change the feed and repair the failure.
node run.mjsExpected result: one Compiler engineer record with the sentence explaining its Haskell match.
02 / PREPARED INSTALLATION
Take the example into Studio.
Open your Console and sign in.
Your operator supplies the URL and account. Confirm you can select the assigned workspace.
Help with sign-in →Create a disposable source.
Use the example's module and schemas. Keep the source's generated file references and choose the supported API / HTTP execution profile.
Exact Studio steps →Run and inspect the record.
The draft runner must be connected. Paste the supplied input, save and run. Check the record and its supporting sentence.
Help with the runner →Change, fail, repair.
Use the changed input, inspect the missing-field error, then correct the field setting and run again.
Expected failure and repair →
03 / INSTALLATION OPERATOR
Prepare a guided Enterprise evaluation.
Enterprise 0.1.0-alpha.1 has public Linux images and Windows packages. The current alpha requires operator configuration of identity, HTTPS, PostgreSQL, storage and the runner connection. A complete self-service installation bundle is in preparation.
Studio execution
Use the Windows draft runner for Test draft. It includes its .NET runtime. Headed browser work also needs WebView2 and an interactive desktop.
Download the draft runner →Agree on the installation and access.
Choose an isolated evaluation workspace and record the release, server origins, identity provider and support contact.
Configure and start the server.
Prepare persistent PostgreSQL and artifact storage, identity and HTTPS. Apply the reviewed migrations, then start the API and Console.
Connect the draft runner.
Configure a host address reachable from the API, certificate trust, its credential and exact workspace scope. A container's localhost is not the Windows host.
Hand over a working example.
Confirm sign-in, workspace access and the example's returned record. Give the tester the Console URL, workspace, sign-in method and support contact.
Keep the right host with the right task.
The draft runner executes saved Studio drafts. Enterprise Node runs enrolled jobs after signing and publication. Standalone Guida Node belongs to the separate Complete/Control workflow.
Component guide →