Documents in Nuclosian are concepts and summaries as PDF, often with diagrams. They appear in the conversation, for example as a state-model overview or a short concept before the build. Files arrive as a download and in your file drawer next to the chat.

Why documents belong with configuration

Configuration without a shared picture creates misunderstandings. A PDF with a diagram makes the proposed process visible. That is alignment and documentation, not the ERP itself. The binding truth remains the Nuclet, screen, and state in the instance. Documents help alignment between business and IT. They do not replace the check in application mode.

Print outputs and reports in the ERP are a different topic. They sit on datasources and forms in Nuclos. Nuclosian documents are session artefacts of AI-assisted configuration.

What Nuclosian takes on

Keep document or summary in the prompt, plus what the PDF should contain. Nuclosian creates the file and stores it in the drawer. Function overview: First steps.

Wiki note

There is no dedicated wiki page for this Nuclosian feature yet. Technical report and form configuration lives under datasources in the Nuclos wiki. For getting started with Nuclosian, First steps and this page are enough.

What to clarify next

• Which concepts need a shared PDF before the build?
• Who reviews drawer files before they are shared on?
• Which lasting instructions belong in house rules?