Description
Let's explore the idea of measuring "cognitive trust" in projects, inspired by "cognitive complexity" linters. By identifying good and bad patterns among Gnolang contract developers, we can enhance our environment for building highly trustworthy apps and systems.
It's not just about scoring contracts; we want to make smart choices in VM features to minimize the risk of untrustworthy code. Our goal is to make it nearly impossible to create such code.
Considering our mission and unique advantage, let's document this approach. We could even measure cognitive trust in other languages and provide scores.
To improve contract quality, let's create our own set of linting rules. This will facilitate static analysis, promote unambiguous patterns, and reduce the cognitive load of working with multi-contract scenarios.
Your feedback and any existing work links are welcome. We might even consider sponsoring a PhD research project to delve deeper into this concept.
Related with #17 (comment)