Explorations
An exploration builds something to answer a question. Use it for knowledge that only building can give: how it looks, if it works, or how much work it is. It does not change the repositories. Its artifacts stay in its folder, because they are progress.
#Create one
Give intake an input. When only building can answer it, intake writes explorations/E-<number>-<slug>/exploration.md, with the status ready.
| Section | It holds |
|---|---|
## Question | The one question that it answers |
## How to find out | What to build or to try |
## Context changes | What future tasks must know |
## Evidence | What the build did, what it learned, and how to see it |
## Findings | The answer |
## Review | The result of accept |
#Build it
build builds or tries only what ## How to find out gives, and does not make it ready for production. It can read the code in the repositories, and it does not change them. It makes each decision itself, and writes it under ## Evidence.
#Accept it
accept shows the question, what the build learned and each artifact. You choose one.
- The findings answer the question. The status becomes
done. - The findings do not answer the question. You change the question or
## How to find out. The status becomesready. - Discard it. The reason goes under
## Review. The status becomesdiscarded.
#Turn it into tasks
Give intake the id of a done exploration. It reads the findings and the artifacts, and asks only about the gaps that are left. Each change task gives the id in exploration, and build uses the artifacts as a reference.
When each of those tasks is done, the exploration is consumed.