Concept · Set of pages
Where a result lives after the job finishes
This piece is that path, what reads from it, and what is deliberately not kept. organisation: whose data it is. solution: which piece of work.
Page 1 of 4
By Marcus Teale · Product, storage and outputs · 8 July 2026 · 6 min read
When a job finishes, the worker that ran it writes what it produced into an object store and the job's status becomes terminal. The polling response tells you the job succeeded; it does not carry the output.
That separation is deliberate. A close pack is a document, a reconciliation is a table with a hundred thousand rows, and a forecast is a set of files. None of those belongs in a JSON body that a caller has to hold in memory to find out whether the job worked, and putting them there would make the size of your analysis a property of your HTTP client.
The path
Everything is written under a path shaped by the tenancy spine, in this order:
- environment — which deployment this is. The same application in two environments writes to two places that never see each other.
- organisation — whose data it is. This is the boundary that matters.
- application and instance — which application produced it, and which of your instances of it.
- solution — the piece of work: one period, one run, one question.
Read from the outside in, that path is a sentence: this environment's copy of your organisation's instance of the close application, for August. Nothing is stored outside a path shaped like that, and nothing resolves a path a caller's verified identity does not reach.