Bound the investigation
Provide a reproducible symptom, the relevant environment and useful logs. Separate reading, testing and modification permissions. Start in a demonstration workspace.
Select the engine and access
Use the internal runtime or a configured Task harness with suitable capabilities. Console provides SSH sessions or an available embedded executor; SFTP and file tools expose authorised resources.
Require a reproducible diagnosis
Ask for commands, results, the retained hypothesis and the limits of the diagnosis. Long-running commands have durable tracking. Browser screenshots or generated files can support the observations.
Review changes separately
Review the proposal before an operation modifies a service. Recovery guarantees depend on the harness and tools: internal checkpoints do not establish safe replay of every external engine’s effects.
Check the outcome and cost
Repeat the reproducer and inspect the traces. In Activity, connect the Task, calls and deliverable. Use versioned Laboratory cases when comparing configurations.
Check a long command before repeating it
Start long builds or tests with console_start and track the returned identifier with console_poll. If a response is lost, look for the same operation’s receipt on the compatible Console. A launch receipt does not prove tests completed; record the exit code and actual results.
Deliver a tool inside a document
A calculator, form or visualisation can be delivered directly in a Galaris HTML document, using shared Datasets for data. Specify inputs, expected calculations and edge cases; verify the result before use.
Required resources are embedded, Dataset access requires reader rights and consent, and write conflicts must be handled. The PDF is a static copy of the display. Create a document application.