How Belief Maps Work

Believing things on blind faith is OK as long as they are treated as axioms. The BeliefCot App encourages individuals (possibly in groups) to design a robust network of beliefs so that they may be traded among peers and debated non-subjectively. Outrageous ideas are best placed at the top of the hierarchy while the bottom leafs mandate the "axiom property".

Can bold thoughts stand alone?
There are no rules, just a trade-off between Time and Space. Beliefs almost always have a support tree which gives such concepts their context. There are two ways for a belief to garner support and it can be a mixture of both.

  • Beliefs can be supported by contradictions (space / discrete / dual). Click on the STATUS button to see the "contradiction tree".
  • Beliefs can be supported by other beliefs (time / imagination / singular).

What are the advantages to using a Belief Map instead of a Contradiction Tree?
The "right way" is the path which is free of mistakes. Understanding the trade-offs in any decision is a requirement for avoiding mistakes (excluding chance).

  • It tends to be easier to think about the reasons why one believes in something versus why it shouldn't because the mind perceives concepts singularly.
  • Belief structures can be re-used symbolically. Therefore, refining one's thoughts in a Belief Map in such a way that prevents "circular dependencies" can be difficult but the reward is a "clear head". Contradictions don't have dependency issues because of the "breakout parameter".
  • It is important to collaborate on thoughts using both types of reasoning (Beliefs + Contradictions) because, together, they create a perpendicular structure. DocuCot is an App which requires a blend.

How does one determine if a belief is true?
It is important to remember that all thoughts must be considered "TRUE by default".

  • Click the STATUS button and watch how the fate of each belief is determined solely by the contradictions.
  • Use the CantCot App to defeat or defend the status of all beliefs.
  • Thought Cot's software combined with the user's "contradiction database" can only be used to say whether or not a belief is FALSE.

Can this application show the status of each belief within the corresponding row instead of launching a "STATUS pop-up"?

  • It is not possible to store a global flag in the database which says whether or not the belief is FALSE because the status is relative.
    • The status of every belief is dependent upon the user-defined "breakout parameter" which controls the depth of recursion.
    • Contradictions and beliefs are saved concurrently.
  • It is possible to display the Belief Map with each row labeled as either TRUE or FALSE by changing the "Status" list-menu in the command bar. The downside is that the list can take longer to generate.
  • A single CANT/CUZ object added to the database can lead to rather surprising results. Contradictions can cause a cascading crash of the entire belief structure when injected at the right (not-wrong) spot.

Are there are any existing data structures which mimic the behavior of Cant/Cuz?s

  • Think of Cant/Cuz as everything, and the Belief Map as a way to shuffle the cards in order.
  • The Bloom Filter mimics the Cant/Cuz in that contradictions absolutely mask the data stream.


The command bar has a list-menu labeled "Linking" which lets users find belief entries that are considered "Top Beliefs". Ideally there should only be one "top belief" for each endeavor. Use the linking menu to search for other types of beliefs which include "axioms", "orphans", and combinations thereof.

The Belief Map allows users to re-use hierarchal trees (much like the DocuCot App). If a belief is available within the list menu after clicking on the LINK button, it means that the belief (and possible sub tree) may be shared as support without creating a circular dependency.