Review results¶

A report presents experiment output as a diagram, explorer, research page, or cross-experiment synthesis.

Open a report¶

Open Reports for the experiment's synthesized answer. A report can contain text, figures, interactive elements, and source links.

Trace the source¶

Follow source links when you need the exact code or data behind a claim. The experiment views answer different kinds of questions:

Timeline for progress, decisions, and deviations
Plan for approved intent and expected outputs
Code for the complete set of changed files
Compute for jobs and runtime
Metrics for connected training or evaluation measurements
Worker for detailed execution context

Use source links to open the corresponding experiment view. Code shows the complete experiment worktree.

Silico experiment Code tab showing changed files and a code diff

Refine a report¶

Ask Silico to explain a section, inspect a metric, add a comparison, or change the presentation. Request new evidence through a follow-up experiment in the parent thread.

Ask for a new report¶

Ask the planner for a report and specify its format and intended audience. For example:

Create a short report for the model-training team. Include the main metric, its control, and the untested assumptions.

Report links open the report. Thread links open the read-only thread record. Private source references in a public report remain restricted.

Public report links can be opened by anyone with the link. Organization reports require organization access. See Share reports.

Push the code to GitHub¶

When an experiment produces software you want to keep using, ask Silico to push the code to GitHub. It creates a branch and draft pull request; it does not push to the default branch.

Name the target repository, or ask Silico to create a private one. Connect GitHub if needed.