Explorer
A wide, multi-column view of the active project: every record type gets its own column so you can read objectives, requirements and constraints side by side.
For: Product owner, Project lead
When to use it
- Before a planning or review session, to see the whole requirement set at once.
- To spot gaps: an empty column, or objectives with no requirement that serves them.
- To check consistency between types, for example a technical requirement that conflicts with a business constraint.
How it works
Columns follow the order Intent → Requirements → Constraints. Each card shows the code, state and statement; open a card to see the full record. Scroll sideways to move between columns.
Keep in mind Retired records are hidden here. Open a record type from the menu and filter by state to see them.