Overview

The Unclassified (UNC) domain is a holding area for stories and use cases that have been captured but not yet assigned to a functional domain. Elements here are in triage: they are acknowledged as valid product behaviors but have not yet been classified into the appropriate domain and area.

No use cases are currently held in this domain.

Areas

Three areas exist under UNC to support initial sorting during triage:

UNC::PHY — Physical Workflows. Behaviors that are purely physical with no current digital counterpart, such as card placement procedures or bin organization guides. These may graduate to a domain once a digital interaction is designed around them.
UNC::NFR — Non-Functional. Cross-cutting quality attributes and non-functional requirements, such as instant persistence or optimistic UI behavior. These typically graduate to the domain where the relevant functional behavior lives.
UNC::TBD — To Be Determined. A catch-all for stories awaiting initial triage. Everything in TBD should be reviewed and moved to PHY, NFR, or a proper domain as soon as the behavior is understood.

Graduation Rules

When a use case or scenario in UNC is classified into a proper domain:

The UNC identifier is marked RETIRED with a reference to the successor identifier.
A new identifier is assigned in the target domain and area, following the standard numbering rules.
The old identifier is never reused.

See the Naming Convention page for the full immutability rules and a worked graduation example.