No custom topic types or type-specific workflows

What the limitation is
Talkyard offers a fixed set of topic types: Discussion, Wiki, Question, Problem, Idea. There is no ability to define custom types, attach custom status models to them, or modify the behavior of existing types.

How it was discovered
Structuring the Talkyard Limitations subcategory. The topics here needed to convey "immutable observed fact" — something that exists as a permanent record with no resolution workflow. None of the five available types fit precisely. Problem was the closest but imposes a New/Planned/Started/Done status model that implies the limitation is something to be resolved, which misrepresents what these topics are. Discussion was chosen as the least wrong option because it imposes nothing.

Impact
Every domain has its own kinds of things with their own lifecycles. Forcing them into a fixed type set means either picking the least wrong option or misrepresenting the nature of the content. The type system cannot be made to reflect the actual structure of the work.

Workaround
Discussion type used for limitation records — it imposes no status model and makes no claims about the topic's lifecycle. README documentation carries the meaning that the type cannot express.

Status
Workaround in place. Accepted constraint for interim platform use.

LOGOS Requirement
See: LOGOS → Requirements — Custom topic types with definable status workflows