Skip to main content

R10 Request-Idea

Version​

v1.0, dated 12 May 2022

request and lightbulb manual hand cranked cogs Watercolor

Targets​

  1. R01 Dreamcatcher

Dependencies​

Strategic Intent​

How to catch a Dream ?

The goal of the Dreamcatcher is how to go from an incoherent utterance to a reusable asset using Request/Idea pairing. This pairing is based on splitting out the pure problem as a Request and allowing any number of Ideas to be proposed to meet that Request. Conditional Funding is then applied to these items, and paid out upon completion, providing a form of natural selection causing evolution.

Requests avoid the solutioneering problem, where selection bias dominates, maximizing the open mindedness of the system. Ideas promote maximal reuse of works of knowledge by being pure solution, being applicable to areas not originally thought of, thereby maximizing return on investment of effort

We have a number of possible App ideas floating about that we hope to use the Dreamcatcher to complete, but not in Request/Idea format. It is possible to test the Dreamcatcher Concept internally using git and markdown documents. If we cannot use our own system to manage our own expenditure of resources, then our concept must be fatally flawed.

Particularly we aim for a system with self improvement, and so we must experience this self improvement directly to fundamentally understand it, and to fix its deficiencies. Moreover because we believe it is the fastest way to do any kind of knowledge work, if it works as we expect, it will be the fastest way for us to do our own internal work.

The overall aim is to get the absolute minimum version of the Dreamcatcher operating in manual mode, where the minimum version is a knowledge work producing system that can self improve. We must refuse to operate in any other way, or declare abject failure. This is in order to test the processes involved more easily and earlier than would otherwise be possible, and serves solely as a stepping stone to the development of the software version which will automate much of this. To this end, it is the software version that's the final goal.

Tactical Intent​

To do this, we need to:

  1. Define what a Request and an Idea is
  2. Enter the general app ideas into the manual system
  3. Use the process itself to improve the process using github issues and git commits to the .md files.

Detailed Description​

Tactical Intent 1: Define what a Request and an Idea is.​

Must​

  1. List the concept count required for the implementation by counting the number of items in the Dictionary that need to be used during the execution of this simple system
  2. Define the minimum possible Dreamcatcher features using concept count as a comparison
  3. Define a Pool where Requests and Ideas enter a marketplace for funding
  4. Define a Quality Assurance actor to control minimum standard of the Pool and declare Requests and Ideas as Completed
  5. Produce written material that is presented on the website with every commit
  6. Use AI generated NFT artwork for each Request and Idea.
  7. Handle staking of virtual money against Requests and Ideas

Should​

Always have a single operating version agreed upon between participants

Could​

Manage actual money

Should Not​

  1. Attempt to cover edge cases
  2. Solve problems that will only exist for the manual version of the Dreamcatcher

Must not​

  1. Involve any documentation outside of the Dreamcatcher Website for docs

Tactical Intent 2: Enter the general app ideas into the manual system​

Must​

  1. Enter some of the Ideas into the Pool
  2. Produce at least one Request for each App Idea that enters the Pool

Should​

Could​

  1. Extend or test the content of those App concepts
  2. Leave a substantial number as stub Requests or Ideas

Should Not​

Tactical Intent 3: Use the process itself to improve the process using github issues and git commits to the .md files.​

Must​

  1. Be actively used by at least two actors.
  2. Go through at least 2 rounds of process self improvement