ck-notes

# cad-khana working notes — the delta Two shared skills already cover most of this and are **not** repeated here: - **`working-notes`** — the `_notes/` symlink mechanism, why `Grep`/`Glob` find nothing, the `rg` forms, the leave-it-uncommitted cadence. - **`repo-research`** — signal doctrine, the promotion policy and its two exemptions, dispositions, the closing-a-shipped-idea workflow, filing formats. Load whichever applies; this file is only what those two don't say about this corpus. `CLAUDE.md` §"Working notes" lists the files; §"Field-notes promotion policy" maps a promoted fix to its code/doc surface. ## The loop these notes serve cad-khana is demand-driven: a feature starts from an observed consumer need and **closes only when the consumer actually converts its sites**. The notes are the two halves of that loop. | File | Role in the loop | |---|---| | `field-notes.md` | Consumer-written friction, unfiltered. The demand side's raw input. | | `adoption-inventory.md` | The *stock* of friction already priced into the consumer's code — workaround sites mapped to the call shape they wish they could write. Each section is a feature's ready-made exercise slice. | | `worklist.md` | **Continuing-state file.** Sequencing and status for the cad-khana side only. | | `research/ideas.md` | Authoritative for provenance and scoring. The worklist points at it, never duplicates it. | | `implementation-log.md` | Why each thing shipped; the durable record when a source note is ...