coulomb/info-tech-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
info-tech-canon/workplans/ADHOC-2026-08-15.md
tegwick 24ac33c89e
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
fix(workplans): qualify ad-hoc identifiers with the repository prefix 
`ADHOC-YYYY-MM-DD` is unique per date but not per repository, so any two repos
opening an ad-hoc on the same day collide. The 2026-08-26 fleet projection
reset refused 9 records for exactly this reason.

Canon (work-record-types_v0.1, CUST-WP-0066) settled the form as
`{PREFIX}-WP-ADHOC-YYYY-MM-DD`, filename unchanged, and grandfathered existing
ids on the condition they are never *silently* re-derived. This is the explicit
migration that clause allows for.

The hub id is derived from the record id, so a changed id is a different
record: stale state_hub_*_id fields are dropped and fix-consistency re-derives.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-28 00:28:23 +02:00

1.8 KiB
Raw Blame History

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

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

id: ITC-WP-ADHOC-2026-08-15-T01
status: done
priority: medium

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

id: ITC-WP-ADHOC-2026-08-15-T02
status: done
priority: medium

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

id: ITC-WP-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.