Components and terminology
You work in Studio, which is part of the Enterprise Console. The API stores and coordinates authorized work. Execution happens in separately configured hosts, not in your web browser.
Which component do I need?
Section titled “Which component do I need?”| Component | What it does | When you need it |
|---|---|---|
| Console | Browser interface and sign-in session. | Every interactive Enterprise evaluation. |
| API | Authoring, persistence, authorization, execution coordination and product APIs. | Every Enterprise installation. |
| Migrations | Plans and applies the server database schema. | Installation and reviewed upgrades. It is a one-shot command. |
| Recovery | Operator tooling for database/artifact recovery and consistency checks. | Maintenance, with a matching recovery procedure. |
| Windows development draft runner | Runs saved, trusted Studio drafts before publication. | The first-draft tutorial and HTTP/browser draft iteration. |
| Windows Enterprise Node | Enrolls with Enterprise and executes authorized signed work. | Managed API/browser jobs after release and enrollment. |
| Linux document worker | Processes retained documents through its configured execution path. | A retained-document workflow. |
The local seed and local document credential images are development helpers. They are not general account provisioning or identity-provider integrations. See published images for the complete inventory.
Source, draft, product and campaign
Section titled “Source, draft, product and campaign”| Term | Practical meaning |
|---|---|
| Tenant / workspace | The exact scope your identity is allowed to access. A broad role alone is not enough. |
| Source / extractor | The code and contract for collecting data, including its input, output and execution requirements. |
| Draft | Saved authoring work that you can edit and test before a release. |
| Record structure | Field names, types and keys for the records you want to keep or expose. |
| Mapping | How source output supplies those record fields. |
| Data product | A record definition and API prepared for review, publication and activation. |
| Campaign | Managed execution work whose progress and outcomes appear in operations. |
| Signed revision | A reviewed, immutable source snapshot delivered to authorized execution hosts. |
Draft tests and managed execution are different steps
Section titled “Draft tests and managed execution are different steps”The draft runner executes trusted saved code so you can correct it quickly. Testing does not publish a revision, enroll a Node or activate a product. Enterprise Node follows a separate enrollment and signed-work path. Installing one does not automatically make the other available.
The runner is not a sandbox for arbitrary untrusted scripts. Use an evaluation workspace with code and target access agreed for the task.
Document processing
Section titled “Document processing”The document worker processes retained inputs on Linux. Configure it for a retained-document workflow with the appropriate identity, source revision and storage access. Use the Windows draft runner for Studio tests and Enterprise Node for headed browser jobs.
How this relates to the other Guida products
Section titled “How this relates to the other Guida products”Complete is the standalone Windows desktop application. Guida Node is its standalone execution host; Control operates those hosts through Remote Ops. Enterprise Node is a separately deployed Enterprise execution host. Enterprise has its own Console, identity and authorization model.
You do not need to install all of these products to evaluate Studio. Choose your starting point, then follow that product’s setup instructions.