Some requests need several steps in a fixed order before Academica can answer. Each step takes the result of the one before it and either continues or stops. This ordered work is what turns a single request into a report, a generated image, or a saved document.
Transport and work are separate
| Part | Responsibility |
|---|---|
| The connection | Receives your request, checks who you are, and returns the result |
| The ordered work | Runs named steps in order, with checks that can stop early |
| Simple lookups | Return a single value with no ordered steps |
The path a request takes
Work that runs in ordered steps
- Starting a research session, with checks for reuse and capacity.
- Producing a report, from gathering evidence to writing and assembly.
- Long-running work that reports its progress as it goes.
- Any task where a failure part-way through must stop cleanly.
Everyday examples
Producing a report
A report request loads its inputs, gathers evidence, writes each section, and assembles the finished document. Each step waits for the one before it, so a report only reaches you when every stage has completed.
Generating an image or video
A generation request is checked, sent to the model, verified, stored, and returned. If a step fails, the work stops there rather than returning a broken result.
Starting a research session
A new session first checks whether an existing one can be reused and whether there is room to start another. Only then does it open a fresh session and begin reporting its state.