Overview¶
Silico organizes work into four related objects:
Thread → plan → experiment → report
The thread is the continuing investigation. A plan describes proposed work. Launching a plan creates an experiment. Reports present experiment outputs.
Follow one question through the system¶
Suppose you want to know why a model hallucinates on a particular class of prompts.
You start a thread with the question, the model, and a representative dataset. Silico proposes a plan for a baseline, an internal measurement, and a held-out evaluation. Launching that plan creates an experiment. Its Timeline records the work and its Report explains what the evidence supports.
Follow-up work in the same thread creates another plan and experiment. The thread retains the relationship between them.
Know when to make something new¶
| Keep using… | When… |
|---|---|
| the same thread | the next question depends on the reasoning or evidence already there |
| a new plan | the thread is ready for another concrete piece of work |
| a new experiment | a rerun or changed condition deserves its own execution record |
| a new report | the output answers a distinct question or needs to serve a different audience |
Start a new thread when the question can stand on its own. Put related independent threads in a folder rather than forcing them into one research history.
Context attachments¶
Files, repositories, papers, data, models, and earlier work stay attached to the thread message where they were added.
An attachment added for a follow-up does not change earlier experiments or become available in another thread automatically.
Personal and organization settings hold the things that really are reusable: credentials, integrations, runtime variables, compute, and standing instructions.
Read the layer that answers your question¶
- Open Summary to learn where a thread stands now.
- Open Timeline to reconstruct how it got there.
- Open an experiment to inspect its Plan, Report, Code, Compute, or Metrics.
Continue with Start a thread.