When an analysis has results worth keeping, the agent publishes them as a report to the project your folder is linked to, without waiting to be asked. It then tells you in a line or two what it published and gives you the link. When later work changes the results, it publishes the same report again as a new revision. Small questions and coding work get no report. You can also ask for a report in your own words, and say where else it should go:
For numbers you check again, such as weekly KPIs, the agent suggests a dashboard: a report built from one script it reruns, so each update is a new revision. It asks first before it publishes to any other project or organisation, before it uploads raw data or a file from outside output/, and before it creates a share link or deletes anything. When your folder is not linked to a project, it starts one first (see Projects) and publishes there. The agent then:
  1. Reads the report guide from AIUS Light, so the report follows the current format.
  2. Picks the destination. It uses the project your folder is linked to, the one it started for this work, or the one you named, and creates the project if you asked for a new one.
  3. Attaches the evidence. It uploads the scripts, notebooks, charts and result files under output/ that the report rests on, and keeps everything else on your computer.
  4. Reviews the draft. The platform checks the report’s structure, numbers and evidence links before anything is saved. The agent fixes what the review flags.
  5. Publishes and reads it back, then gives you the link and what it shows. It cannot see the page itself, so tell it about anything that looks wrong and it fixes it.
The agent's five-point summary for the marketing team with the link to the published report

The agent's summary after publishing

Updating a report

The agent publishes the report again when follow-up work changes its results, and you can ask it to revise the report at any time, for example after new data arrives. Publishing again with the same report creates a new revision; readers of the project see the latest, and every earlier revision and share link stays as it was.

What is shared, and with whom

A published report is visible to members of its organisation. The attached files go with it; your raw data, other files and the session itself stay local unless you approve them. To show a report to someone outside the organisation, create a share link. If the platform is unreachable, the agent finishes the analysis and saves the report locally, and tells you what it could not publish.