Sybot Forge

Sybot Forge is the contextual design assistant available in the Project Designer. It helps you understand existing objects and, when authorised, can perform the operations available in the Portal, User View, Semantic Model, Workflow and BPMN editors without leaving the Workbench.

Forge is optional. Its panel is shown only when an administrator enables the module and the user's role meets the access requirements.

Where to find it

1. Open Designer.
2. Open a Project in the Project Workspace.
3. Select the Forge icon in the tab bar.

The panel opens on the right-hand side of the existing Designer interface. Drag its edge to resize it, collapse it to a narrow rail, and reopen it without closing any editor. Forge is not available in the global Workbench: each conversation belongs to the open Project.

Conversations and memory

Each conversation retains its history, plans, results and approvals. Use the header menu to switch sessions, create a new one or archive the current session.

A session can be resumed after refreshing the page. If a task is still running or waiting for approval, its status is restored in the panel. If the worker is interrupted, Forge resumes from persisted steps without duplicating a completed change.

During a browser editing session, Forge keeps a separate conversation for the Workbench and each open object. The first visit to a Workflow, Portal or another object creates a dedicated chat; returning to that tab restores the chat previously used for it. Manually selecting another conversation from the menu explicitly associates it with the current object.

How context is selected

Forge always uses the open Project as its boundary. When an editor tab is active, the panel also shows that object as the active context. You can therefore ask:

• “Explain what this Workflow does.”
• “Check whether this User View uses objects outside the Project.”
• “Prepare a home page for this Portal.”

Unsaved editor changes are reported. When the plan changes the object in the active tab, Approve plan asks the editor to finish saving and switches that same tab to read-only before execution. The conversation remains associated with the object. If the editor cannot save, approval does not start; if the object is open in another window or session, save or close it there and then repeat the request.

Supported objects

Object	Available assistance
Workflow	Perform Workflow Designer operations, including structure, tasks, configuration, conditions, packages, runs, results and assets.
BPMN	Perform BPMN Designer operations, including the XML model, variables, packages, deployment and execution.
User View	Perform editor operations, including pages, widgets, sources, queries, versions, sharing, packages and exports.
Semantic Model	Perform editor operations, including entities, relationships, measures, queries, refreshes, versions, sharing and packages.
Working Dataset	Create a typed operational store in the Project, append and query records, calculate aggregates and export CSV or XLSX.
Portal	Perform editor operations, including repositories, pages, widgets, data, access, packages, builds, releases, deployments and supported integrations.

Available operations depend on Project permissions and administrator settings.

For example, Forge can create a Portal that collects typed form data, stores it, displays it in a table, calculates chart metrics and provides an export. It shows the plan before execution; the server manages keys, revisions, bindings and validation. Widgets connected to data, Workflows, User Views, BPMN or BI systems require dedicated configuration and validation and are not created as incomplete standalone components.

When a new draft requires a Role, Forge uses the Role name shown in the product and applies the authorised default when the request does not specify one. It does not ask for numeric identifiers; objects that do not use Roles, such as Portals, do not require this choice.

End-to-end processes

Forge translates the objective into a blueprint of artifacts and behaviours, then checks that an available action covers every part. One plan can create several Sybot objects and pass typed outputs from one step to the next.

When a request needs persistent operational data but does not name a source, Forge proposes the Project’s governed Working Dataset. Its data contract is reused to generate and verify the form, table, aggregates, chart and export. If part of the outcome is unsupported, Solution coverage identifies it and the plan is not executed as though it were complete.

The same plan can connect an already published User View, one of its widgets, an executable Workflow or a deployed BPMN to the Portal. Forge selects only authorised objects from the same Project and pins the available version in the binding; publishing and deployment remain separate operations.

Project knowledge

Forge can combine:

• the inventory and definitions of objects belonging to the Project;
• the object open in the active tab;
• the current conversation;
• public Sybot documentation;
• LightHouse collections linked to the Project, when available.

Answers separate evidence found in objects and documentation from generated proposals. Forge asks for clarification only when a functional choice is genuinely required, using a question that users can understand. If the choice is already present in the request or conversation, it is reused without asking again. Identifiers, revisions and omissions in the plan are resolved internally or cause the turn to be replanned; they are not information requested from the user.

Assistant answers support Markdown: headings, lists, tables, links and code blocks are formatted directly in the panel. Content is sanitised before display. Common mathematical notation is shown with Unicode symbols; for example, a flow arrow is rendered as → without exposing LaTeX delimiters.

Forge replies in the language of the current request. For a short or ambiguous follow-up, it keeps the conversation language and falls back to the interface language when detection is not possible. You can explicitly request a different response language.

Plans and approvals

A request may require several steps. The panel displays the current state and the planned steps.

While Forge is working, Operational progress shows observable phases: capturing the request, collecting context, analysing the goal and dependencies, compiling the plan, approval or execution, and result validation. It is not a transcript of the model’s internal reasoning; it reflects the turn’s actual state.

If Forge receives a solution that is incomplete or incompatible with the available operations, it attempts to correct it before approval. A missing technical detail is not turned into a question for the user. If the plan still cannot be verified, Forge shows the interrupted step, cause, impact and required action; no object is created or changed.

The Approval selector applies to the current conversation. Its default is Require approval. When an administrator makes Auto-approval available, you can explicitly enable it for future turns: Forge runs without confirmation only the actions marked as eligible. Plans containing ineligible actions or changes to the object currently open still require manual approval.

Read-only analysis runs directly. Before creating or changing anything, Forge presents a plan that names the object, action and reason. Select:

• Approve plan to execute exactly the displayed steps;
• Reject to finish without applying changes;
• Cancel to request interruption of a running turn.

The selected mode never extends user permissions: ACLs, Project membership, revisions, audit records and editor contracts still apply. High-impact operations, such as deletion, publication, deployment or access changes, remain separate and require the approval specified by the plan.

After a successful change, the read-only tab is refreshed with the result. To continue editing manually, reopen the object for editing from the Designer.

Recommended workflow

1. Open the Project and, when useful, the target object.
2. Describe the objective and constraints, not only a technical command.
3. Check the context shown in the panel.
4. Review the plan, object names and mutating actions.
5. Approve only when the plan matches your intent.
6. Open created or modified objects from the final message and validate them in their editor.

Troubleshooting

• The panel is missing: open a Project and ask the administrator whether the module and your role are enabled.
• Forge cannot prepare the tab: fix or save the changes reported by the editor, then select Approve plan again.
• The object is open in another session: save or close its tab in the other window or session, then repeat the request.
• A change is denied: check your Project role and the object's specific permissions.
• The turn does not complete: read the interrupted step, cause and required action shown in the panel; contact the administrator only when the diagnostics identify a platform issue.
• The answer lacks information: name the object, expected result and constraints; open its tab to provide a more precise context.