---
id: ADHOC-2026-08-15
type: workplan
title: "Ad hoc: feedback directory and provision relationships"
domain: infotech
topic_slug: canon
repo: info-tech-canon
status: finished
priority: low
created: "2026-08-15"
updated: "2026-08-15"
owner: grok
spec_refs:
  - feedback/README.md
  - demand/CapabilityProvisionEconomics.md
  - demand/ProvisionRelationships.md
state_hub_workstream_id: "dd403bf7-b84d-49af-b914-fb5b0bd1b88a"
---

# ADHOC-2026-08-15 — Consumer feedback directory

## Goal

Give the canon a durable place to collect consumer reports on whether
existing concepts hit, friction, gap, or are drop candidates — without
collapsing that evidence into `demand/` or `incoming/`. Land the
provision-to-provision relationship the resource-control restatement
needed, so class `P` does not become a dumping ground again.

## Tasks

### T01 — Establish `feedback/` front door

```task
id: ADHOC-2026-08-15-T01
status: done
priority: medium
state_hub_task_id: "9554b8c9-879a-4ddf-a3d2-f0fe141c2935"
```

Add `feedback/README.md`, `TEMPLATE.md`, and `index.yaml`. Distinguish the
directory from `demand/` and `incoming/` in those files and in the intake
practice. Register the path in `canon.yaml`. Not a canon artifact.

### T02 — Seed first report from resource-control

```task
id: ADHOC-2026-08-15-T02
status: done
priority: medium
state_hub_task_id: "95599215-b461-4893-8736-d249030bef34"
```

Write `feedback/2026-08-15-resource-control-capability-provision.md` from the
2026-08-15 backup-cycle mapping. Hits stay here; the three defects remain
`demand/CapabilityProvisionEconomics.md`.

### T03 — Provision-to-provision relationships

```task
id: ADHOC-2026-08-15-T03
status: done
priority: high
```

Accept `demand/ProvisionRelationships.md`. Add `uses_provisions` on
`CapabilityProvision` with `depends_on` / `may_use` only (CAP-R11). Add
`security.secrets` to `data.backup` `may_use`. Do not cap maturity across
the dependency. Canon 0.5.0 / ITC-CAP 0.4.0.