Access a Package
From any report:1
Open a finding
Click a hypothesis card to expand its drawer.
2
Review evidence
Scroll past the narrative until you reach the evidence attachments section.
3
Download
Choose Download Evidence Package to grab a zip of everything created for that hypothesis.
What’s Inside
| Item | Description |
|---|---|
notebooks/analysis.py | Generated Python notebook or script used to validate the hypothesis. |
charts/*.png | High-resolution PNG exports for every visualization referenced in the report. |
summary.md | Markdown description of the finding, metrics, and confidence level. |
data-samples.csv | Anonymized sample rows that back up the insight. |
APIs for Automation
- Charts API –
/api/charts/...streams chart images for embedding elsewhere. - Evidence Files API –
/api/workspace-files/...lists the generated notebooks or scripts. - Evidence Package API –
/api/evidence-package/...zips and serves the entire artifact set.
X-User-ID headers for ownership checks, so only the creator (or an explicitly shared account) can fetch these assets.
When It Helps
Audit & Compliance
Keep the evidence zip as proof of how the KPI or report was produced.
Data Team Handoffs
Share the notebook/SQL so engineers can productionize the logic.
Manual Deep-Dives
Pull everything locally if you want to rerun or extend the experiment.
Tips
- Each hypothesis has its own package—download only what your workflow needs.
- Files stick around for the lifetime of the analysis; deleting the report removes the associated evidence immediately.
- Use the APIs above if you want to mirror packages into your own storage bucket.