Optimizing the neurosphere of work involves improving the DEEP flow of the play of a riveting game. It's ALL in the mind.
Annotations and notifications might be KEY, but the secret neuro-sauce is how we meditatively freshen-up transform the "air quality" in the work noosphere.
Paying attention to the creative mind is how we will build a collaborative workflow mgmt systems utilizing AI/ML for distributed, reproducible, extensible reliability engineering data analyses with annotated discussion and notifications for peer review. It's entirely about optimizing human engagement to collaboratively HYBRIDIZE cognitive intelligence of teams of humans using machines and optimizing trained models for better automation/recommendation.
Optimizing the neurosphere of work involves improving the DEEP flow of the play of a riveting game. It's ALL in the mind.
In general, we see this implementation as being about using patterns and re-using as much code as possible from the Pythonic data science ecosystem, eg Conda package mgmt, the Jupyter architecture and the standard .ipynb JSON notebook schema, SnakeMake workflow mgmt system, as well as others, like Google Colaboratory or Amazon EMR JupyterHub or others which use a similar, nearly standard architecture.
We believe that this distributed, but version-controlled workflow should work well for those who are already famililar with advanced Git[Lab] workflows of including affiliated methods, processes, issues, CI/CD pipelines and a wide variety of tools used in MLops. Data engineering for reliability engineering and warranty tracking in systems [which often involve products from different, possibly competing companies and entities] is perhaps not really so much feature-based as with software as much as the forks in the reliability analyses might be annotation-based or driven by cross-referenced or other documented concerns which arise during peer-review of the analyses of issues and opportunities for improvement.
Annotify.APP will be primarily intended to illustrate, in one specific example, how the ANNOTIFY.ORG open source material might be implemented.
The goal, at least at first, of ANNOTIFY.APP will be exclusively for illustration. At first, the open source project will be developed in order to make this one concrete example of an application work. Later the open source project will be developed for other usage profiles. It is possible that this example could also eventually someday evolve into a separate product, but not at first.
As all open source advocates well know projects are not products ... illustrative examples of projects are not immediately intended to be products.