Leonardo (Beta preview)

Leonardo is part of Railbase: the AI agent for preparing processes inside Workflow Studio. Describe the people involved, the information they need and the outcome you want. Leonardo helps prepare a separate draft using the forms, participants, conditions and actions available in Railbase.

Leonardo drafts. People review and authorise publication.

What Leonardo helps you prepare

Create a process. Turn a description into a supported coordination or approval draft, including its request form, participants, steps and conditions. If an essential requirement is unclear or unavailable, it needs clarification or a reported capability gap, not an invented action.

Adapt a process. Prepare changes within the extension points permitted by an existing process. Leonardo is not a way to rewrite supplied business logic or unlock a capability outside the company's entitlements.

Check a process. Prepare scenarios and use supported Studio checks for forms and routes. A proposed test is not an executed test. Passing a route check is not proof that every role completed the business process.

The same boundaries apply to other requests, not only demonstration scenarios. What can be prepared depends on the installation's supported capabilities, company context, permissions and available participants. Leonardo is not a general-purpose application builder.

From your description to a reviewed draft

1. Identify the role starting the process, its goal and the required end result.
2. Describe the information, documents, participants and decision rules. State the rules you know; do not ask Leonardo to invent company policy.
3. Select creation, adaptation or testing in the supported Railbase preview environment. Resolve questions and missing capabilities before proceeding.
4. Review the resulting draft in Workflow Studio, including the form, participant selections, conditions and any protected requirements.
5. Inspect what checks actually ran, what passed or failed and what was not exercised.
6. Have authorised people complete the applicable approval and publication path. Then accept the complete process with the affected roles.

A draft, a model response or a successful check does not by itself authorise publication or establish production readiness.

Railbase modules and updates

Leonardo is part of Railbase, not a separate product or subscription. It does not add modules, override their licensing requirements or change the company's Railbase subscription.

Adaptations must stay separate from supplied workflow definitions and use permitted extension points. Protected business actions remain protected. Running requests retain their pinned effective revision.

Compatibility must be checked against the actual Railbase release and installed modules. A conflict needs an explicit revision, review and approval; Leonardo is not a guarantee that any customisation will survive every future update without work.

Stopping, cancelling and continuing

Stopping a Leonardo job is different from reversing its effects. During preview evaluation or a pilot, review the job's saved state and recorded operations before deciding what to do next.

• Stop one job: request that its current work stops. Do not treat a closed window or a pressed stop button as confirmation; wait for the recorded job status. A completed operation is not automatically undone.
• Stop Leonardo for the company: a separate administrator control is intended to block current and new Leonardo work in that company. It is not an instruction to cancel the company's running business processes.
• Discard draft work: use the permitted draft-cancellation path and inspect what will be removed. Stopping alone is not deletion, and deleting a draft is not rollback of published revisions or completed business actions.
• Continue saved work: resume through the available job controls after reviewing the saved position, requirements and company context. Continuation may require clarification or a fresh check when permissions, dependencies or the source revision have changed.
• Clarify the task: state which requirement changed before continuing. Do not assume a paused job has adopted a new instruction or should repeat already completed actions.

The availability and behaviour of these controls must be confirmed for the evaluated Railbase build. Recovery, company-wide stopping and rollback scenarios remain part of production acceptance, not an unconditional promise of the Beta preview.

Access, provider and data

Access to Leonardo depends on the supported build, the company's permissions and an approved AI-provider connection. An account or subscription with an AI service does not by itself activate Leonardo or guarantee compatibility.

Leonardo is not activated through a separate website request. It is used inside Railbase when the supported build, company permissions and provider configuration allow it.

Before any customer pilot, agree the supported provider and authentication method, which context may be sent, the provider's data-handling terms, applicable costs and limits, responsible administrators and acceptance criteria. Keep credentials out of requests and conversations. Use synthetic data for the current preview.

Questions about Leonardo in Railbase

Use Railbase support for questions about the supported build, Workflow Studio or provider configuration. Leonardo has no separate demo request or activation form.

Include the Railbase version, the affected workflow step and a sanitised example. Do not attach customer records, passwords, API keys or confidential business documents.

Before production use

Production use requires an accepted release and evidence from the actual intended environment: complete role-based business journeys, access and company isolation, failure and recovery behaviour, stop and continuation controls, provider operation, and compatibility with supplied workflows and updates.

Preview evaluation does not replace that acceptance. Read the workflow lifecycle and plan implementation with the responsible team.