FEATURE SPEC

Questions or comments?

Post them as a comment on the tracking issue -- requires a GitHub account with access to this repo.

View Rendering

Parent Feature Set: ../concept.md.

Note

Following information is reverse engineered for [AI-DLC]. Review and remove this note before proceeding.

Important

To follow the AI-DLC process, fill this spec with PM assistance first.

GitHub Issue Description (verbatim)

Issue #615, titled "[Reporting] View Rendering":

Summary

Feature set

No Acceptance Criteria, Expected Business Value, or Additional Context sections were present on this issue — stating that fact rather than inventing content.

Matching PRD Content

Reproduced verbatim from ../reference/Reporting_PRD_v3_2026-07-17.docx, §3 (Scope, Delivery Modalities) and §4 (Flow 2).

Scope (MVP): View rendering: bar chart, line chart, table, summary card — with persistent data source, time range, and segment labels.

Delivery Modalities: - Chat (inline): For direct questions with 5 or fewer key metrics or a single chart. Answer lives in the conversation with a 'View full report' CTA for deeper exploration. - Canvas (expanded view): For multi-chart reports, cross-dimensional comparisons, drilldown tables, and event-triggered reports requiring human review. Includes filters, chart and table views, and export actions. Canvas is the primary surface for the Reporting experience. - Export (PDF/CSV — Phase 2): For executive-shareable packets or any report the user explicitly requests as a downloadable artifact.

Flow 2 — See: The view renders in the same conversational thread or opens in Canvas for multi-metric results. Visualization type is selected automatically. Every rendered view carries persistent labels: data source, time range, active segments. The user types a follow-up and the view updates in place.

Sources

• GitHub issue #615
• ../reference/Reporting_PRD_v3_2026-07-17.docx, §3 and §4