Under data, Nuclosian covers queries, evaluations, and realistic test data. Technically many evaluations sit on datasources: they define which business objects are considered, with conditions, joins, and parameters. Nuclosian creates these structures or removes test data again when the session is done.

Why to keep datasources and test data apart

Datasources feed reports and forms. Parameters such as a record id make them reusable. Syntax checks and preview validate the query before it runs in production. Test data, by contrast, lets you walk through screen and state without polluting real cases. Mixing both risks demo noise in reporting or missing samples in testing.

For business teams that means realistic scenarios before approval. For IT that means a clear split between query definition and temporary data in the Nuclet.

What Nuclosian takes on

Keep query, evaluation, and test data in the prompt. Nuclosian writes create or delete directly into the instance. There is no diff for that. A prompt may tell the model to ask before a delete. That is not a blocking dialog. Overview: First steps.

Technical reference in the wiki

Editor and parameters for reports and forms: Datasources (Report & Formular). The wiki describes the datasource editor. This page places queries and test data in Nuclosian work.

What to clarify next

• Which evaluations need their own datasource?
• Which test data may be deleted after the session?
• Who may edit SQL on datasources by hand?