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.
1.2 KiB
| id | type | status | date | consumer | consumer_domain | canon_version | artifacts | related_demand | related_workplan | spawned_demand | spawned_workplan |
|---|---|---|---|---|---|---|---|---|---|---|---|
| feedback/YYYY-MM-DD-<consumer>-<slug> | consumer-feedback | inbound | YYYY-MM-DD | <repo-or-agent-name> | <domain or unknown> | <version the consumer used> |
Feedback:
Consumer:
Canon version used:
Artifacts exercised:
Related demand: none | demand/<file>.md
Consumer purpose
What the consumer was trying to do. One short paragraph. Not a feature request.
Hits
Concepts, ids, or rules that were used as specified and provided utility. Each item: the id or name, what they did with it, and why it counted as a hit.
Friction
Concepts that were used but incomplete, misplaced, or in the way.
Each item: the id, what went wrong, and whether a demand/ was filed.
Gaps
Needed something the canon does not name. Usually becomes demand/.
Drop candidates
Only if the consumer would not miss the concept. Unused in this cycle is not enough. High bar; this list is often empty.
Steward notes
Canon-side disposition. Status, links to spawned demand or work, and any limit on how far this report should be generalized.