FEATURE SPEC

Questions or comments?

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

Time and Segment Lenses

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 #617, titled "[Reporting] Time and Segment Lenses":

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

The PRD does not have a section dedicated solely to "Time and Segment Lenses" as its own capability — the closest verbatim matches are the Scope line item and references inside other flows/use cases. Reproduced below rather than inventing a dedicated section that doesn't exist in the source.

Reproduced verbatim from ../reference/Reporting_PRD_v3_2026-07-17.docx, §3 (Scope) and use case examples.

Scope (MVP): Time lens and segment lens adjustments before re-running a saved query.

Use case example (Finance & Department Leader): "Show me headcount and overtime by cost center for Q2." → Canvas view with a data table and bar chart — headcount and overtime hours broken out by cost center, scoped to the departments the user has access to. Segment lens exposed for further filtering by location or manager.

Phase 2 / Out of Scope: Acquisition cohort and location segment lenses — Phase 2.

Sources

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