PM-STA-0020

A State is modelled as a subclass of a Thing

A State MUST be modelled as a specialisation of the Thing whose lifecycle stage it represents.

Non-normative: formally neat and pedagogically awful. "New Artist is a kind of Artist" is true in the subsumption sense and collides with the everyday reading, where being new is a stage Larry is in, not a kind of thing Larry is. It also sits awkwardly with PM-STA-0010: class membership in the RDFS sense accumulates and never retracts, whereas a lifecycle stage must be left behind.

The specification keeps the subclass notation because it is what the source says. Any product built on this should never show a user the word "subclass"; states should be presented as stages of a lifecycle. The notation is a liability at the surface even though it is sound underneath.

SRC-BLOG MUST · draft · area STA · since 0.1.0

Verbatim quote

this amounts to specifying each State as a subclass of some Thing

Source

frozen 2026-09-08T095339Z · sha256 59f2395f5971a03e… · live