Reports & exports
The agent writes the report. Mizura embeds the real tables and figures, checks the numbers and citations, and compiles it. Styles, formats, editing, and exports below.
Generate a report
Before generating, inspect the analysis results and open any sources the report should cite. A report with a Results section requires a successful analysis run; a literature review without data can instead describe the sources. Ask in chat. /report works too. The agent writes the full document: an abstract paragraph before the first section, an introduction, body sections by theme with Methods and Results first, a discussion or conclusion, and limitations. Tables and figures come from the runs that produced them. The model never retypes a table. Citations get checked against the sources. See Evidence & literature.
- Ask for a report and specify the research question, audience, language, and reporting style.
- Wait for the report check and compilation to finish. If it is rejected, read the named problems and ask Mizura to correct them, or fix the missing analysis/source and retry.
- Open the report link in the reply or choose it under Outputs → Reports. The document viewer opens the Draft; choose PDF when that preview is available.
- Confirm the report appears in the document viewer with available formats listed. Check its sections, citations, tables, figures, and limitations, then download a listed format. If PDF is disabled or absent, use the Draft or another available format and check the PDF setup below.
Styles and formats
| Citation styles | Formats |
|---|---|
| APA 7 (default), Harvard, Vancouver, Chicago, IEEE, MLA. In Settings the choices are APA 7th, Nature, Chicago, Harvard, and IEEE. Nature maps to Vancouver. | Markdown, PDF, DOCX, and TeX when listed as available in the Outputs report menu. |
The reporting style also sets the prose format and the default figure preset. Report and figures agree with each other. One caution on TeX: the file references bundled fonts and figures by absolute path. It is a build artifact, not a portable source file.
PDF depends on the local Tectonic/TeX setup. On a first build while offline, PDF may be unavailable until the TeX bundle is cached; the other formats can still be produced. Check which formats the report viewer marks available before relying on a download.
Checks: why a report is rejected
A failed check rejects the document. The problems get named. The agent fixes them and resubmits. Common ones:
- A number in the prose with no executed result behind it. See Evidence & literature.
- A citation whose reference was never opened. Titles, surnames, years, and quotes get verified against the opened text.
- A table or figure with no real run behind it. A Results section with no executed analysis fails here.
- Structure problems. Fewer than three main sections. A citation in a heading. More than two URLs in the prose.
- Language mismatch. The report must be in the language of the request. Source titles and quotes keep their original language.
Editing sections, safely
Open the report, press Edit, and change the section you want. Each section has its own Save button; save writes that section only. A “Saved” note confirms the save.
Two protections matter. Sections you edited are yours. Regenerating the report never replaces or drops them. If the report changed since you opened the editor, Mizura refreshes the sections and asks you to reapply the edit. Copy a long edit before saving so you can reapply it after a stale-version refresh. If a run is in progress, wait for it to finish and save again. A failed save shows a note; retry after the report is current.
Session exports
The Outputs toolbar offers three exports once the session has scripts or figures.
| Export | What you get |
|---|---|
Jupyter notebook (.ipynb) | A title and plan header, then one section per kept execution with its code cell and recorded output. Kept executions are the latest succeeded run per analysis. Exploratory scratch runs are excluded. |
Quarto (.qmd) | The same structure as a literate document. Code chunks do not run automatically. Tables and figures link by path. |
Replication package (.zip) | A README with replay instructions and hashes, the report, code translations, and one folder per execution with its code, recorded inputs, execution record, and output tables and figures. The materialized table for a large dataset is left out; keep the original file and rebuild that table before replaying the execution. The README notes this requirement and records the omitted table's hash. |
Verify a package by replaying an execution. Mizura runs it again from its recorded inputs and compares the result with the recorded hash. A mismatch means the replay did not reproduce the original result. Say so plainly, and investigate the difference before you share the package.
Per-item exports
- Figures. Download PNG, or open the reproducible script behind the figure.
- Tables. Copy as Markdown or CSV. The viewer shows every row. Generated reports truncate tables over 200 rows to the first 200 with a caption note. Full precision stays in the CSV.
- Scripts. Download the Python, open it in VS Code, or read the provenance: execution, seed, data hash, code hash, result hash, edited-from.
- Reports. Download Markdown, PDF, DOCX, or TeX from the download menu.
- Sources. Download the session's source list as Markdown.
- Datasets. Download the full file, or copy the visible page as CSV.
Languages and RTL reports
Chat replies follow the Analysis Language setting: English, Arabic, French, Spanish, German, Italian, Portuguese. When it is not English, narrative replies come in that language regardless of the language of your current message. Code, citations, and verbatim names stay unchanged. Reports go in the language of the request.
Arabic reports typeset right-to-left. Paragraphs and tables that start with Arabic become RTL blocks. Inline runs use the Arabic font with bracket mirroring. The date line uses Arabic month names. Arabic column names work in formulas.
Limits, stated plainly. Mixed tokens like an Arabic word with a digit can reverse the digit. An emoji glyph in neither font gets dropped with a log warning. A very long cell without spaces can overflow the PDF. DOCX was checked in LibreOffice only. Typesetting is not journal-grade. Check the PDF before you submit it.
Figures
Figure style is set at session start. A layout preset (Auto, Display, Manuscript, Nature, APA, IEEE) and a palette (Okabe-Ito, Grayscale, Nature, Viridis, and others). All palettes pass colour-vision-deficiency checks. The print-safe ones, Grayscale and APA, switch to non-chromatic encoding: linetypes and shapes vary, so a figure survives black-and-white printing. Colours for significant, violation, and confidence band are locked. They never follow the palette. Change the style by starting a new session. Settings → Figures & Visuals holds the choices.