DELIVERIES & SHARING
Take the facts with you.
Recorded in the Specstream frontend · Example data
A moment you can return to.
Start a questionSave the right set.
Keep a full collection or a selected subset as a delivery. Preserve the rows, facts, evidence, and originating context.
Let the work move on.
Later research leaves that delivery intact. Return to what was known at the time, even as the collection develops.
Compare the next chapter.
Use fixed deliveries as stable points of comparison. Inspect new observations and changed qualification with their provenance.
Use it where it matters.
Build with the APIChoose the format.
Export as CSV, Excel, JSON, or HTML. Use a spreadsheet for analysis, a structured record for software, or a readable report for people.
Share deliberately.
Share a delivery with clear access and expiry. Revoke a share when it has served its purpose.
Share the question, too.
A saved spec describes the instructions. A delivery contains the output. Share the one that fits the conversation, with its revision intact.
A few useful answers.
Does exporting trigger more research?
No. Exporting and sharing owned deliveries use retained work.
Can a share change when new results arrive?
A fixed delivery share refers to that snapshot. New research produces new work rather than silently changing the shared record.
What travels in a structured export?
Rows and their available facts can travel with qualification, provenance, observation times, and lineage. The selected format determines how that information is represented.