--- id: ITC-WP-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: "10ba1533-5128-5f84-b4a5-d1d4f8ae4b45" --- # ITC-WP-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: ITC-WP-ADHOC-2026-08-15-T01 status: done priority: medium state_hub_task_id: "ee19b730-bf8c-5303-ab8f-ecaf1d5afc2b" ``` 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: ITC-WP-ADHOC-2026-08-15-T02 status: done priority: medium state_hub_task_id: "121bc369-7f06-568f-8068-087a611ca619" ``` 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: ITC-WP-ADHOC-2026-08-15-T03 status: done priority: high state_hub_task_id: "f2bde186-f4cc-5402-a816-4c47c0553377" ``` 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.