build-report

# Analytical report 1. Define the question, audience, decision, scope, time frame, comparison baseline, and requested output. Use supplied sources or accessible authorized data. 2. Validate definitions, grain, denominators, units, missing data, and comparisons before drawing conclusions. Separate observations, assumptions, estimates, and uncertainty. 3. Form an answer-first narrative with findings, evidence, relevant comparisons, limitations, and actions supported by the analysis. 4. Choose a delivery format the user requested or the host can actually produce. Markdown, HTML, documents, and presentations are supported approaches; no particular app, plugin manifest, renderer, or publication service is required. 5. Use tables and charts where they clarify evidence. Check calculations, labels, scales, citations, and consistency with the narrative. Follow the project's established report conventions when available. 6. If sample data is requested, use a supplied or verified bundled sample. If none exists, request the source or create explicitly synthetic data only when authorized. Do not claim a missing demo file is bundled. 7. Verify the delivered artifact in the chosen format and report remaining gaps. Publishing or sending the report requires the assignment's existing authorization. Optional audience guidance: [stakeholder reports](specifications/executive-report.md) and [technical reports](specifications/technical-report.md). Use their quality criteria within the actual delivery environment; provider-specific examples do not choose a host or grant publication authority.