Collective Agency: NeuSphere: Project -OPEN-

Get Started. It's Free
or sign up with your email address
Collective Agency: NeuSphere: Project -OPEN- by Mind Map: Collective Agency: NeuSphere: Project -OPEN-

1. Story

1.1. Why

1.1.1. Blah

1.1.1.1. Increasing our ability to store our present mind state in a usable format for our future selves makes us more fully-adapted 4 dimensional beings; able to better see patterns and meaningful connections, allowing us to impact the future.

1.1.1.2. Developing this ONLY for syntropians initially would give us a strategic advantage against the forces of entropy.

1.1.1.3. Asana, Mindmeister & Evernote has created a phase-change in my abilities. Imagine what NeuSphere could do.

1.1.1.4. Wikipedia was a breakthrough, but come on. It's a series of manually hyperlinked documents based on an ancient editing interface. Imagine a global map of all human knowledge made for the new world.

1.1.1.5. The web still exists in 2D. It's trapped in a box behind glass.

1.2. What

1.2.1. Blah

1.2.1.1. A mind-map for the future

1.2.1.2. A 3D conceptual-mapping interface

1.2.1.3. An elegant way to collectively map concepts the same way our brains do. Holarchical, networked, and fractal, rather than hierarchical.

1.2.1.4. "Mapping the global brain."

1.3. How

2. Inbox

2.1. Launch this project via CrowdCamp?

2.1.1. Does this have mass-scale appeal? Or enough appeal to be crowdfunded?

2.2. Ideal interface: contact lenses

2.2.1. Augmented reality

2.2.2. Records sound and subtle bio signals (dilated pupils, blood pressure, eye tracking, etc)

3. Spec

3.1. Aesthetic

3.1.1. Default: elegant, ethereal, syntropic, geometric, organic

3.1.1.1. Design references

3.1.1.1.1. Prometheus: Star Map

3.1.1.1.2. Tron Legacy: Quorra Repair Hologram

3.1.1.1.3. Iron Man 2: Molecule hologram

3.1.1.1.4. Osmos game

3.1.1.1.5. Complexity Graphics

3.1.1.1.6. Passat commercial

3.1.1.1.7. Misc

3.1.1.1.8. Visual Complexity

3.1.1.1.9. HUDs and GUIs

3.1.1.2. The glowing blue orb from Micah's rebirthday

3.1.2. Aesthetically customizable

3.1.2.1. Anyone can create their own skins, which are actually rich 3D worlds with their own metaforests. For example...

3.1.2.1.1. A microscopic world where nodes are microbes

3.1.2.1.2. A world that looks like the brain and nodes look like neurons

3.1.2.1.3. A universe with galaxies, planets, stars, etc

3.1.2.1.4. Totally abstract worlds of form and color

3.2. Use cases

3.2.1. Mind mapping

3.2.2. Programming

3.2.3. Conceptual architecting

3.2.4. Relationship mapping

3.2.5. Product design

3.2.6. Decision mapping (Sway)

3.2.7. Task management

3.2.8. Data visualization

3.2.9. Memetic mapping

3.2.10. Systems design

3.2.11. Data navigation

3.2.12. Post-2D internet navigation

3.2.13. Storytelling

3.2.14. Influence graph (ripple effect)

3.3. Features

3.3.1. Non-hierarchical organization

3.3.2. Motion controlled in 3D space

3.3.3. Focus

3.3.3.1. Disappear / unfocus everything you're not working on. Shifting visibility based on focus.

3.3.4. Mode switching

3.3.4.1. Nodes can reorganize based on what "mode" you want to be in. *Fluid hierarchy.*

3.3.4.1.1. Example: organize a "process" mind map by type of input or type of tool, and it dynamically rearranges the map based on which view you want to see based on your context.

3.3.4.1.2. Example: organize a product map by use cases, contexts, features, roadmap, etc

3.3.5. Templateability

3.3.5.1. Master templates can be used among different collaborators. Changes to sub nodes are made locally, but global template changes can also be made.

3.3.5.1.1. Example: When changing the "Curriculum" Mindmeister document, I should be able to easily pull those changes into curriculums for specific projects

3.3.5.2. Self-similar / fractal networks

3.3.6. Node states

3.3.6.1. When mind-mapping strategy, you can twist a sphere to make it actionable. Then you can filter all the actionable items when you want to switch from strategy / brainstorming mode to action mode.

3.3.7. Fractal / layered networks

3.3.7.1. Spheres (nodes) can link to other spheres in a network. But each sphere can also contain its own network. You would "zoom into" a sphere to see a network within. Spheres in that network could contain or link to spheres in other networks. Nonlocality.

3.3.7.2. Example: You could have a sphere which is labeled Friends. Enter the sphere and you see a network of all your friends and their relationships to each other. Zoom into an individual friend and see a network of their memes/interests. You can then query each interest for which friends link to it.

3.3.8. Realtime generated statistical infographics

3.3.9. Contingent and dependent tasks for multi-step workflows

3.3.9.1. A vital feature that's lacking in all GTD software (including Asana) is connection of tasks through the 4th dimension. In NeuSpehere, tasks can be linked together in a concurrent flow. Once contingent tasks are completed, dependent tasks are unlocked / revealed.

3.3.9.1.1. This is the perfect bridge from strategy mode to action mode. When strategizing something like rock soup, you can lay out what people need to be brought onboard before other people can be. And then when you move to action mode, it only shows you the tasks that you can complete now, because nothing else is holding it up. If you encounter a task that you cannot complete right now because something else needs to happen, you create that new task or link it to one that already exists.

3.3.10. Possible tasks that activate when enough related nodes are activated

3.3.10.1. Example: An opportunity / connection is seen but not sure how it's actionable and definitely don't have time for action now. But might want to take action once more things are in place down the line. So you tag it with a bunch of things (contexts in which it might be useful, contingencies that unlock it, related tasks, etc) and then it reactivates once those other things activate. (a more dynamic take on the multi-step workflows)

3.3.10.2. This solves the problem I was aiming to solve with the "Asset Map" / possibilities database idea.

3.3.11. Samadhi mode

3.3.11.1. Allows user to shift out of active "doing" mode into receptive "being" mode… the graph reassembles into beauty / art, dynamically created by the network that's been formed.

3.3.12. Simple import / curation from other sources

3.3.13. Labels of spheres and threads (relationships) may change based on your vantage point / zoom level.

3.3.13.1. Example: In a Swayspace, something that's a What in one view could be the Why of other sub Whats in a more zoomed in view.

3.3.14. Input macros (user-defined and AI generated)

3.3.14.1. Smart templates for object/relationship types that you enter often, and have similar characteristics.

3.3.14.2. Example: In Asana, I have a ton of tasks that read "Contact Person X re: Topic Y." The only "smart" thing I can do with these is manually tag them all with "contact," and then look at that tag when I want to get in a flow of doing nothing but contacting people. In NeuSphere, it would quickly recognize the pattern in these tasks and suggest a smart macro. Now, anytime I start saying "contact…" (or make the hand-near-head phone gesture), it creates a sphere specifically geared toward that type of task. In addition to auto-asking about certain things (like topic to be discussed, contingencies and dependents, etc) it auto-finds relevant spheres (such as that person's sphere in the social graph, tasks that seem related, etc)

4. Similar Attempts

4.1. Incoma

4.1.1. http://www.incoma.org/