Open the file panel and return to its root. Keep reference documents in docs, scripts in scripts, and outputs in generated. Separate inputs from produced results.

Inside docs, create an academy folder for goals, procedures, and references. Clear names make files easier to reference and later select for service access.

Rename unclear files, or use Send to when moving them into another folder. Folder upload preserves a collection’s organization. Check the destination after the operation.

A script is reusable method; a report is the result of a particular run. Keep the checker in scripts and its report in generated, separate from lasting rules.

In Service permissions, select only the documents and scripts it needs. Consumer outputs are stored per conversation. Organizing files does not publish the entire workspace.

CLI imports a document copy. Changed files are archived under generated in a run-specific folder. Review the result before deciding whether to update the original document manually.

Create a topic folder containing an instruction file and a reference. Then inspect an output and identify it as a result, not an automatically updated shared rule.