* WM client lib that implements afb calls to the WM
* Most of the API
X Application structure, whereas controller events should be forwarded to it?
  Decorator? Proxy?
X Loose coupling between API calls and the actual handler in the appliation,
  perhaps convert the verb's json input into a nlohmann::json and pass it to
  some app method which then in turn can return a Result<error, json> kind
  of thing. The verb's entry point would then construct a reply accordingly
X Design a sensible and lightweight representation of a Layout inside the WM
  Appication.
* Wm Objects (Layers, Screen, Surface, Areas?) Should be handled with IDs, only
  Upon making the concrete calls shall the actual objects be resolved.
* Implement an application configuration, possibly in /etc, must contain:
  - json configuration names