Organize documents, scripts, and outputs

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.

Try it · Open the file panel and use 返回上级 to reach the root; highlight the three folders.

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

Try it · Enter /docs, select 新建文件夹, name it academy, then upload brief.md and faq.md.

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.

Try it · Rename note.md to process.md, then use 发送到… to move it into /docs/academy.

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.

Try it · Open /scripts and /generated in turn to inspect a teaching script and its example report.

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.

Try it · Edit the Service in My services, open the document permissions picker, and verify that only academy is selected. Then browse the generated output folder.

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.

Try it · Compare /docs/academy/brief.md with this run’s archived file under generated/runtime.

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.

Try it · Create the teaching folder, open its instructions, then compare them with a generated output.