kai-topical-maplisted

# /kai-topical-map — the map of pages, entities, and passages a team can start building ## Objective A topical map built for AI search and traditional search together: which entities the brand must own, which sub-queries each pillar has to satisfy, where the brand can say something nobody else can, which pages that implies, and in what order they publish. Every decision traces to retrievability, entity clarity, source quality, and measurable demand. AI search visibility is sampled, volatile, and engine-specific. This skill does not promise citations. It builds the thing that can be measured — pages to create, entities to clarify, passages to make retrievable, sources to cite, and the follow-up checks that show whether any of it worked. ## Done when Work type `strategy-plan` (`also_covers: topical-map`) — floor **E3/C3/O1** (`harness/eco-floors.yaml`). - **E3** — a named human approved the exact content node architecture: entity clusters make strategic sense, hub-and-spoke groupings are right, information gain angles are achievable with data the brand actually has, no critical sub-query is missing, and the priority order by Citation Impact Score is correct. - **C3** — `banned_word_check` clean, every structural gate below met, and a named non-producer read the map end to end. - **O1** — the baseline AI Presence Scorecard is recorded before any page ships, with the re-read scheduled at 30/60/90 days. Each priority node names the query set it targets and who owns publishin