- rethink persistence (process definition and orchestration, realization)

=> persistance is essential and was central to Aare. Beside removing
Omnibase references (and implication of WfManagedObject), some of the
application features were very dependant on the persistence (like logging,
tracing process evolution). All of these features are to be thing again
considering as much as possible a loosely coupled solution. A general
purpose storage solution like Voyage could be used. At first, in image
storage will be used to focus on the running aspects of the library.
- rethink interaction
=> Designing a general interaction sub-system is probably the more
challenging tasks. Aare was web based. We want workflow to be UI agnostic.
Moreover, we want to associate  ,
remove Magritte (replace UI or build an independant system based on
Annoucement for instance)

Yes I agree. Now I would like to be able to
- define a super simple workflow: I picked sequence: start -> task1 -> task2