Connect execution hosts

The Console can be available even when no execution host is connected. First identify the action you need: Test draft, managed Enterprise execution, or retained-document processing.

Studio draft runner

For Test draft, the operator supplies the Windows Guida.Workspace.TestRunner package matching the installation. This runner executes trusted saved drafts; it is separate from Enterprise Node.

The connection requires:

• The runner’s HTTPS address as reachable from the API container.
• A credential delivered privately to the API and runner.
• The runner certificate’s public trust chain, with the correct hostname.
• Matching exact tenant/workspace scopes on both sides.
• A Windows interactive desktop and WebView2 for headed-browser tests.

localhost inside a container means that container, not the Windows machine. The development setup uses a host-reachable address; a different topology needs its own explicit address and certificate configuration.

After configuration, open the assigned implementation in Workspace Studio, choose Test draft, and select Refresh. Run the synthetic tutorial and check its returned record. Do not replace certificate verification with an insecure connection when diagnosing a failure.

There is not yet a public, versioned runner-setup bundle for an independent new installation. The current guided evaluation uses operator-prepared configuration.

Enterprise Node

For enrolled, signed API/browser work, use Guida.Enterprise.Node, not generic Guida Node. The operator must prepare identity, enrollment policy, public revision-signing trust, execution family and capabilities together.

1. Obtain a matching Windows Node package and a launch configuration for the exact tenant and node identity.
2. Supply the bearer credential through its configured secret reference. Keep raw tokens out of launch commands and shared setup bundles.
3. Configure the public revision trust document separately. TLS trust establishes the connection; revision trust establishes which signed code can be accepted.
4. Start the host in the agreed API or headed-browser execution mode.
5. Confirm connected/enrollment posture in the Node shell and Console fleet view.
6. Execute only the reviewed evaluation job, then inspect its terminal outcome.

A heartbeat proves a connection, not that every execution capability is ready. An enrolled Node still needs compatible protocol, policy, revision trust and capacity for the assigned job. These requirements do not apply automatically to the separate Studio runner.

Retained-document worker

The Linux document worker needs its own configured identity, authorized retained input and signed work. The local credential helper is tied to the development identity setup; it is not a generic adapter for an arbitrary identity provider.

Keep the first Studio exercise independent of document-worker enrollment. Add this execution path when it is part of the agreed evaluation.

If availability or enrollment fails, follow troubleshooting.