keyword-explorer

ARCHIVED

"lets aggregate the data in a single table view on the hub. I want a datatable where I can sort and filter on all the fields we have. Assume that months from now I might drop new csv files for the same tag. And yes the data is often already filtered to remove obviously overcrowded keywords."

STAGES

  1. proposal09-21
  2. requirements09-21
  3. design09-21
  4. tasks09-21
  5. build—
  6. archived09-21

CAPABILITIES — 2 IN ONE CHANGE

  • keyword-corpus3 requirements
  • keyword-explorer2 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ✓1.1Katy runs one command and every archived keyword CSV is in the table — the ten 2026-09-17 exports' **83 data rows, represented as 71 keyword rows carrying 83 query hits** (12 of the 83 are the same keyword seen under a second query, which is the row grain working, not loss).not stated
  • ✓1.2*(generator verified against a synthetic second capture in 4.2; awaiting a real drop)* Katy drops a new export into `docs/pulls/`, re-runs the same command, and its rows appear with no file edited by hand. — **Verified for real by #501 (40 eRank exports) and #503 (Sep 18 batch)**, both landed after the generator was written; no file hand-edited.not stated
  • ✓1.3Katy reads `embroidery font` and sees its four per-query tag-occurrence counts — 80, 81, 12 and 6 — not one merged number.not stated
  • ✓1.4Katy sees searches, competition and KD once on the row, not repeated once per query that surfaced it.not stated
  • ✓1.5Katy re-exports a query months later and can read both captures: the new one current, the previous marked superseded.not stated
  • ✓1.6Katy finds a keyword missing from a later pull and the table says *seen in N of M captures* — never that demand fell.not stated
  • ✓1.7*(implemented; awaiting her interactive check)* Katy sorts or filters on any column, computed columns included, and the table reorders or narrows on that field. — **Katy, 2026-09-21:** walkthrough done (*"I did my walkthrough - consider it done"*).not stated
  • ✓1.8Katy scrolls one surface past a screenful of rows and finds no page controls.not stated
  • ✓1.9*(implemented; column sits beyond the fold at 1024 — verify by scrolling)* Katy tells current rows from superseded ones at a glance, with each row's capture date legible. — **Katy, 2026-09-21:** walkthrough done (*"I did my walkthrough - consider it done"*).not stated
  • ✓1.10Katy sees no cell wrapped to a second line, and one type size across the whole table, header row included.not stated
  • ✓1.11Katy widens the window and the surplus goes to the keyword column while the others hold their width.not stated
  • ✓1.12Katy sees no colour band on any value — the schema is recorded in the proposal, not applied.not stated

WHAT HAPPENED

  1. ARCHIVED

    proposal and specs and design and tasks and archive landed

    2026-09-21 · 1 pull request
    • #512chore(openspec): archive five shipped keyword-explorer changes — SHIPPED

History read from a manifest built at 2026-09-30 (09e7bcc).

1 pull request, found by commits touching the change folder