These are examples of business logic that a particular app or service may have in a particular domain / use case.
In a heterogenous Fediverse someone might build msg exchange for water starting to boil in their teapot. It will likely not be a #FEP anytime soon, and most probably never enter into W3C artifacts.
Still, ideally, one should be able to discover from the endpoint how this Teapot service works. Simplest is discovery where docs/specs live. E.g. via "Compliance Profiles".