Add feedback/ for consumer reports on canon-concept utility
A third front door next to incoming/ and demand/: longitudinal PurposeFit evidence, not a change request and not a canon artifact. Seeded with the resource-control backup-cycle mapping.
This commit is contained in:
parent
bd14b9bc36
commit
686bfb5a9d
11 changed files with 377 additions and 1 deletions
|
|
@ -54,12 +54,17 @@ Related but distinct front doors — do not confuse them:
|
|||
| Directory | Holds | Next step |
|
||||
|---|---|---|
|
||||
| `incoming/` | raw candidate material to absorb | this practice |
|
||||
| `demand/` | a stated consumer need, not yet a document | workplan + design |
|
||||
| `demand/` | a stated consumer need, not yet a work item | workplan + design |
|
||||
| `feedback/` | observed utility of existing canon concepts | cite; spawn `demand/` only if a gap needs work |
|
||||
| `seeds/` | historical provenance of first-generation canon files | frozen |
|
||||
|
||||
If an input turns out to be a *need* rather than a *body of knowledge*, move it to
|
||||
`demand/` and open a workplan instead of an assimilation workspace.
|
||||
|
||||
If an input is a report on whether existing concepts hit or missed, move it to
|
||||
`feedback/`. A single arrival may split: utility evidence stays in `feedback/`,
|
||||
requested changes go to `demand/`.
|
||||
|
||||
---
|
||||
|
||||
## 3. Stage 1 — Intake
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue