Guida Control

Guida Control is a separate, proprietary alpha application for operating Guida Complete and Guida Node from a browser. It connects through the Remote Ops API; it does not read a node’s workspace files, queue database, workflow ledger, or operations database directly.

The public container image is available for evaluation and Guida operation under its accompanying license. Image availability does not make Guida Control open source.

What Control provides

• Overview and Command Center for attention, capabilities, active work, and bounded operator actions.
• Results for captured output, exports, and delivery records.
• Pipelines and Extractors for contract inspection, validation, certification planning, draft/diff, preflight, and gated execution.
• Workspace, Browser, and Workbench for focused node inspection and operations.
• Activity and Nodes for Control’s own connection history and node registry.
• An opt-in Advanced area for lower-level contracts.
• Remote View for streaming and, when allowed, controlling a browser tab.

Control is an operator overview, not a replacement for every native Guida console. Queue and workflow-ledger truth remains on the selected node.

Ownership boundaries

Data or decision	Owner
Workspace configuration, extractor catalog, pipelines	Guida node
Queues, workers, workflow runs, items, events, recovery	Guida node
Remote Ops capability, domain, policy, and confirmation checks	Guida node
Saved node registry and connection preferences	Guida Control
Control activity history and export/delivery records	Guida Control

Control keeps its own SQLite data under its configured data directory. That data is not a replica of Guida’s operational databases.

Read-only first

Monitoring and contract inspection work without enabling remote control. Mutating actions require both:

1. GUIDA_CONTROL_REMOTE_CONTROL=1 in Control; and
2. controlEnabled for the selected node.

The Guida node still makes the final decision. Its Remote Ops capability, domain, approval, confirmation, size, and timeout rules continue to apply. Enabling Control does not bypass them.

Remote Ops has no built-in client authentication in the current MVP. Put both applications on a trusted private channel protected with NetBird ACLs, firewall rules, reverse proxy policy, localhost tunnels, mTLS, or an equivalent external control. Do not publish a Guida Remote Ops port directly to the internet.

Typical local setup

Guida Node normally listens for Remote Ops on port 9631. Guida Control normally serves its browser UI on 127.0.0.1:9632. Add or import the node in Control, verify its health and compatibility, then keep remote control disabled until a workflow genuinely needs mutations.

For another machine, bind Guida to a private interface and register that private address in Control. Network reachability and authentication remain your infrastructure’s responsibility.

Extractor and pipeline operations

Control reads the compact Remote Ops schema and requests detailed contracts only for the methods it needs. Extractor catalog, verification history, statistics, anomalies, and certification plans are read operations; starting or cancelling certification is gated.

Pipeline authoring follows Guida’s explicit sequence: draft, diff, upsert or delete, validate, preflight, plan, and preview. Saving does not start a run. Execution, downstream work, recovery, and control actions require separate bounded requests.

See Extractors and Semantic Pipelines for the node-side contracts.

Alpha boundaries

Supervise operational workflows while the Control surfaces mature. This alpha does not promise built-in enterprise identity, role-based access control, or an installed fleet qualification service. Use external channel security and each node’s Guida policy today; treat broader Enterprise controls as future work until a shipped contract says otherwise.