+ We have many plan for further developing both the \hbugs{} architecture and
+ our prototype implementing them. Interesting results could be obtained
+ augmenting the informative content of each suggestion. We can for example
+ modify the broker so that also negative results are sent back to the client.
+ Those negative suggestions could be reflected in the user interface by
+ deactivating command narrowing the choice of tactics available to the user.
+ This approach could be interesting expecially for novice users, but require
+ the client to trust other actors a bit more than in the current approach.
+
+ We plan also to add some rating mechanism to the architecture. A first
+ improvement in this direction could be to distinguish between hints that, when
+ applied, are able to close one or more\ednote{Zack: e' possibile?} goals and
+ tactics that doesn't. Other heuristics and/or measures could be added to rate
+ hints and show them to the user in a particular order: an interesting one
+ could be a measure that try to minimize the size of the generated proof,
+ privileging therefore non-overkilling solutions\ednote{Zack: qua se vuoi ti
+ puoi pure auto-citare, cosa vuoi di piu'?}
+
+ We are also considering to follow the \OmegaAnts{} path more closely adding
+ ``recursion'' to the system so that proof status resulting from the
+ application of old hints are cached somewhere and could be used as a starting
+ point for new hint searches. Tough the approach is interesting, it moves the
+ focus closer to automatic theorem proving and we are considering if its worth
+ the effort given the increasing availability of automation in proof
+ assistants' tactics.
+
+ Even if not strictly part of the \hbugs{} architecture, the graphical user
+ interface (GUI) of our prototype needs a lot of improvement if we would like
+ it to be usable by novices.\ednote{Zack: la parte della GUI non ci sta molto
+ bene, sembra che vogliamo fare soldi vendendo HBugs ... forse va solo
+ formulata meglio ...}
+
+ Finally we hardly believe that \wss{} such our brokers and tutors could be
+ used also as components uncoupled from our client, exploiting their
+ capabilities is for example possible to develop a web-based proof assistant
+ demonstrative application. In order to widen even more their accessibility we
+ plan to write MONET descriptions \ednote{Zack: controllare se esiste un
+ termine piu' preciso} of the \wss{} offered by \hbugs{} actors. For the same
+ reasons we plan also to add support for Mathematical Object Managers both for
+ store and retrieve proof status.