Python runtime
pandas, plotting, and analytical code in the same workspace as the research.
Compute that lives inside the research, not beside it.
When a workflow needs a model, a chart, or a data transformation, Sibel runs it in a sandboxed Python environment and attaches the output directly to the research thread. No export, no context switch, no separate tool.

pandas, plotting, and analytical code in the same workspace as the research.
Charts, tables, processed datasets, and files as first-class objects.
Results and logs stay with the workflow that created them.
Compute is part of the research loop, not a separate step.
In most workflows, the moment you open a notebook or a spreadsheet, you leave the research behind. Sibel keeps compute inside the same structure. The chart, the table, the processed dataset are not attachments. They are nodes in the same graph, with the same provenance as everything else.