Principle of massive information exchange

About Switch from a 'Top → Down' to a 'Bottom → Up' information control culture.

That is, information in society flowing many-to-one rather than one-to-many.

Inspiration: PBS Nova's "Wright Brothers flying machine" 's development method. Notion Overview → Analogy → Disclaimer → How to connect information? → Protocol for information revision?

Overview This uses a hierarchy of Wikia articles for an information handling paradigm.

The paradigm is achievable using the Wright Brothers' method of solving a hard problem.

Analogy Exposing the Wright Brothers strategy for finding a reliable way to fly.

The Wright Brothers solved the flight problem by breaking the problem into:



1) How does lift work?

2) How do you control the aircraft?

3) How do you fly the aircraft? (Propeller blade cross section)

The below images show that each answer to above three questions had a common link: cross section.



) Shape influences air motion: slower (shorter arrows) below the wing than above the wing.

2) Warping changes to turn left or to turn right by modifying the end-to-end aircraft's lift.

3) A propeller mimics wing cross section in the propeller's blade for blade push backward.

The Wright Brothers solved the flight problem by tapping available material and problem solutions whenever possible - re-designing only when necessary.

To them, a sufficient solution to a problem solved that particular problem.

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">A better answer appears while using the current solution to a problem.

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">█

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">

<h2 align="LEFT" lang="en-US" style="margin-bottom:0in;">Massive information exchange requires modifying the problem in a similar way:

<p align="LEFT" lang="en-US" style="margin-bottom:0in;"><span style="font-size:medium;font-family:Arial,sans-serif;color:rgb(0,0,0);">1) How to connect information?

<p align="LEFT" lang="en-US" style="margin-bottom:0in;"><span style="font-size:medium;font-family:Arial,sans-serif;color:rgb(0,0,0);">2) Protocol for information revision?

<p align="LEFT" lang="en-US" style="margin-bottom:0in;"><span style="font-size:medium;font-family:Arial,sans-serif;color:rgb(0,0,0);">3) Can objective be refined?

<p align="LEFT" lang="en-US" style="margin-bottom:0in;"> M assive information exchange requires sufficient comprehension and coordination.

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">1) Overall navigation strategy: Start with partitioned list(s) of choices and add restrictions.

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">2) Initiate content then manage a series of extensions to the original content.

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">3) Refining a given content objective means introducing shortcuts to that content - often the intermediate guidance information to the content becomes unimportant.

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">▼

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">▼

<p align="LEFT" lang="en-US" style="margin-bottom:0in;">The assembler of information has a responsibility to assist those who desire a particular part of the information to that part of the information as q