Build reports
Difficulty: Beginner. Time: about 20 minutes. Needs: a browser with a fleet loaded (demo fleet works); guest queries apply.
You will turn console analyses into a document that survives contact with a reviewer: capture an insight card losslessly, edit around the evidence, run a parameterized workflow template, and export a PDF. The premise of the reports workspace is that a conclusion is only worth its evidence trail.
1. Produce something worth capturing
Ask the assistant an analytical question:
What is fleet utilization by constellation over the last hour?
The answer arrives as an insight card carrying its scope, method, exact calculation, sample sizes, and exclusions.
2. Capture it
Capture the analysis into a new report (or append to an open one). Capture is lossless by design: because the card already carries scope, window, and assumptions, the report holds the same evidence the transcript showed, organized as a summary, findings, supporting charts, the method (which tools ran, with what windows, steps, masks), and provenance (what data, at what sim time, under which filters).
Expected outcome: a report whose blocks are typed, not freeform: markdown, chart, table, metric, calculation, and asset-reference blocks. The calculation block separates method from arithmetic from assumptions so a reviewer can attack each independently.
3. Edit it into a document
- Add markdown blocks between the evidence with your operator narrative.
- Reorder blocks within a section; retitle sections.
- Delete what you do not need; deleting a chart block keeps the chart in the library.
- Use fullscreen mode over the globe for sustained writing.
Charts deserve a note: a chart in a report is a reference into the shared chart library, not a pasted image. Each library entry keeps its origin (the tool and prompt that produced it, which reports use it) and its regen metadata (the exact tool call and arguments), so it can be re-run as-is or with a different window. A chart is never a picture whose provenance has been lost.
4. Run a workflow template
For recurring reporting, skip manual assembly. Ten operator-grade templates each name the deterministic tools to execute, so two people running the same workflow get structurally identical reports. Try Daily fleet health (parameters: date, fleet): it assembles posture, degraded assets, and utilization and latency trends for shift handover.
Required parameters are prompted before the run; optional ones default sensibly, and the report states which default was chosen. Reports record the workflow and parameters that generated them, so this week's run is diffable against last week's. The full template table (coverage comparison, gateway proposal, link budget validation, launch readiness, anomaly investigation, executive dashboard, regulatory coverage, orbital trade study, weekly capacity) is in Reports.
Expected outcome: a complete multi-section report generated end to end, every number traceable to the tool run that produced it.
5. Export
Three formats, one honest caveat each:
| Format | Behavior |
|---|---|
| Markdown | Portable text with tables; charts export as their data |
| HTML | Standalone styled document |
| Print-based: a print-optimized rendering opens in the browser's native print-to-PDF path, with charts rendered as data tables for archival fidelity |
For PDF, use your browser's print dialog when it opens and choose "Save as PDF".
- PDF shows tables where charts were: intentional; the print path renders charts as data tables so the archived numbers are exact rather than rasterized.
- A captured analysis looks thinner than the chat answer: capture from the insight card itself; plain prose replies without a card have no structured evidence to capture.
- Reports disappeared on another machine: reports persist in the browser alongside your sessions; they are per-browser today, so export what needs to travel.
- A regenerated chart changed: regeneration re-runs the tool against current data; that is the feature. Keep the original report block if you need the historical snapshot narrative alongside.
Where next
- Reports for the complete workspace reference.
- Run simulations to generate scenario evidence worth reporting.