FeedbackFlow System FF#
Feedback is essential to keep the balance of any dynamic enterprise over the long term.
Hence, Feedback is essential for any life, which is a dynamic balance.
Hence, when the Feedback Flow ends, life dies.
These general insights extend to information processing as well.
Hence, for any website in the Jubilee System, the ability to process Feedback is critical.
—LLoL
But how can feedback be submitted and processed efficiently for a website like this one?
Challenge#
That is where datageddon nightmares start with myriads of questions about how to integrate data and sort the impact of ideas for further action.
Proof of concept for scalability of core task#
Wikipedia has demonstrated the importance and power of quickly integrating Feedback Flow where it matters most on myriads of aspects on complex websites.
FF aims to connect toughts in minds of readers to thoughts in minds of writers.
Limits of growth are often defined by (in)ability of systems to integrate diverse Feedback Flows appropriately.
Therefore, improving Feedback Flows is essential for the ResearchCity vision presented here.
There exists currently no system, AI included, that can handle such intense FeedbackFlows without losing some valuable insights to random circumstances that should not matter.
Vision of a POST-based FF System#
To facilitate information integration at such a large scale, LLoL has been developing FeedbackFlows for the Evolvix POST System in order to aid the efficient self-stabilizing of diverse innovation-driven projects.
POST stands for P roject O rganizing S tabilizing T oolkit.
To reduce idiosyncrasy in projects, the POST system uses all letters of the alphabet to classify recurrent tasks in projects by defining efficient “double-caps names” like FeedbackFlow. Such a reduction in avoidable and useless complexity is essential if ResearchCity is to win in the war against general confusion about data in our current global datageddon.
For the ReviewedRelease RRv1 description of the Evolvix POST system see the las section of the supporting information in https://doi.org/10.1111/nyas.13192 (Loewe et al. 2017, Annals of the New York Academy of Science).
This is still the best public introduction to the Evolvix POST System, except it’s now somewhat out of date from missing essential updates to key features to be included in the upcoming POST release RRv2. Examples include a rather confusing naming bug and the lack of a proper description of the Jubilee System, without which any vision of true long-term backwards compatibility and lasting long-term self-stabilizing are essentially reduced to castles in the sky.
Simple email-based FF as implemented for Balospe.com#
FeedbackFlow for this Balospe.com site is a super-simple way to recycle the else hard work of sorting data where it belongs best in order to facilitate efficiency in overall improvements. Here is how it works:
Readers who may wish to comment already know what they may wish to comment on. Often they already have the webpage right in front of them (or can easily find it). If there was an easy way to include that web-location along with the comment, then it becomes much easier to aggregate feedback for particular web-pages automatically. Once all the feedback for a given webpage is there, it becomes much more efficient to update and refine it accordingly.
There is of course no shortage of complex, database-driven solutions for this problem. The challenge is to do it with the least amount of technical overhead upfront, in order to allow such a FF system to grow organically along with a project form the start.
Hence, the following email-based solution is implemented here in order to collect more experiences with how to best organize FF in real-world systems.
It requires
a Webdomain like balospe.com for hosting the pages and folders that would benefit from FeedbackFlow
a basic email address that serves as the inbox for all FeedbackFlow, such as FF@balospe.com
an easy way to include a general FF intro at the bottom of every webpage or FF unit
an easy way to configure a specific FF mailto link for every FF unit
specifically configured email-addresses for every FF unit, such as the following:
mailto: FF+path_to_FF_unit@balospe.com, using the Google mail “+” syntax for email addresses and other useful defaults.
For example, this link ( mailto:FF+path_to_FF_unit@balospe.com ) pre-configures the other mailto details in potentially useful ways as follows:
CC to an additional address (like webmaster@) if required to easily sort by impact (k0..k9) and speedup requested (s0..s9).
Subject default defined in ways useful for broader POST System AIMS processing, such as “FF k2 s2 AIMS for [path_to_FF_unit] Replace_by_OneLineSummary_of_proposed_FF_improvement”, where “k2” stands for “Question Ideals”, which “rebuilds for better balancing and to improve flexibility OLT for Jubilees”, and “s2” stands for “MidTermFocus”, as “The key to succed long-term is to adjust focus over the mid term”; hence, such a submission would be expected to be worked into overall AIMS in time to impact mid-term strategies.
A link to definitions for the impact and speedup seasoning classifications (k0..k9, s0..s9, as given at https://balospe.com/jubilee-systems/iron-rod.html), such that submitters can self-select what they deem the most appropriate classifications for their feedback.
The rather slow default-timescale implies that FF from those who don’t adjust k2 s2 will not likely crowd out thoughtful submissions that are more urgent and more important.
A useful body for helping to focus FF on life-trifectas that matters most, such as “To make this page more gentle kind reasonable for beginners, producers, andOr experts with a background in xyz, please consider improving this: “
Advangages:
Only a simple static website using reST suffices to allow thoughtful citizens to contribute much in meaningful ways.
Minimal up-front cost for setting this up allows to start using it immediately.
There is no limit to the complexity this system can grow into if needed by a real website.
Scalability of post-processing of FF received: start with manual sorting in a simple email client for occasional feedback, but then automated sorting solutions can be set up to pre-process feedback received to best simplify the human decision-making required.
Disadvantages:
There is no limit to the avoidable complexity this system can accumulate unless maintained in a thoughful and controlled way.
Overall assessment:
The pros and cons of this systems are the same: it is incredibly flexible and powerful for allowing to serve an extremely broad set of FF cases of use. However, this extreme flexibility requires that its users bring to its use the self-control required to keep data organized, a task elsewhere enforced by database designs.
Open Questions:
Whether it is possible to provide useful POST System standards, e.g. as the AIMS scales do for importance and urgency, such that enough useful FF productivity can be achieved remains to be seen. If not designed with enough care or if too complex to use, error rates due to misclassifications in this system can make it practically unusable. If complexity of using this is too high it will severely limit the FF from those parts of the audience, which struggles with more complex information layouts. How such a system might compare in real-world use to other systems that have higher up-front IT costs for setting them up is currently impossible to tell without trying it out.
Goal of this analysis?
Given LLoL’s prior experience with a similar scalability problem (in the context of the evolution@home project that he created), it may take a few years of experience of using this to learn of its strengths and weaknesses, and then a bit longer to finalize a peer-reviewed publication to report all insights (such as this 2007 paper did for evolution@home: see https://doi.org/10.1002/spe.806). Needless to say, these timelines can be much accelerated if sufficient buy-in for ResearchCity will enable the use of big-tech efficiencies of scale.
Anticipated use and LLoL’s plea for patience#
Note that Balospe.com is currently set up by one person, LLoL, on a shoe-string budget. Hence the plea for patience with processing Feedback.
Given the magnitude and global scope of the discoveries reported, it is unlikely that LLoL will be able to respond quickly to most of the Feedback anticipated once the discoveries are actually understood.
The vision driving this website is to set up an efficient big-tech organization that will be able to leverage efficiency of scale in sorting complex FF while minimizing the arbitrary loss of ideas due to oversimplifying, overcomplicating, or overreaching in how feedback is written, classified, forwarded, and processed.
Therefore, please, let everyone provide all the feedback everyone wants to provide! Please remember to be gentle kind reasonable in order to serve Reality by improving the various webpages on this site in Reality.
LLoL will do what he can to incorporate feedback while working alone.
As the buy-in of people worldwide increases, he will look forward to employ a coalition of the willing to help with that work. Ultimately, ResearchCity is an extension of the vision to provide efficient feedback for all decision-makers on Earth to gentle kind reasonably encourage life-giving decision-making worldwide for everyone.
The vision of saving life on earth deserves no less.