Guide

Functional Requirements

A behaviour the system must have: what it does in response to a user or event.

For: Product owner, Solo builder, Team developer

About functional requirements

A behaviour the system must have: what it does in response to a user or event.

Example: "Dropping a card on another column changes the customer's status."

What you can do here

  • Search by title, code or statement, and filter by state. Press Apply to run the filter.
  • Switch between List (a table) and Cards (statements visible at a glance).
  • The Acceptance column shows how many acceptance criteria are verified as met. No criteria marks a requirement that still needs them.
  • Open a record to read or edit it, or add one with New record.

Tip Filter by Retired to see records that no longer apply; they are hidden in Explorer.

Authority states

StateMeaningAI agents
DraftWork in progress; anyone with edit rights may change it freely.Shown only on request, never binding
ApprovedReviewed and accepted, but not yet the rule for delivery.Informative; agents ask before relying on it
AuthorityThe binding instruction for people and coding agents.Must be followed and cited
RetiredKept for history; replaced or no longer valid.Must not drive new work