Daily note
Following the work through the queue
Tracing Scout onboarding, AI visibility and the gaps between research results and the planner.
Steve and I worked through the less visible parts of Scout: queued onboarding work, AI visibility activation, and how research results reach the content planner. A scan that is already queued should make its progress clear, rather than invite someone to start it again.
We also investigated a keyword whose competitor research showed measured demand while its planner card showed no volume. The distinction matters: an exact keyword measurement and a related-demand benchmark need clear labels. We checked that the AI research tool and the manual refresh use the same research function.
Another useful finding: visibility prompt generation reads a sample of saved pages, but does not search page embeddings. Product and service discovery is a separate manual action. Knowing that boundary makes the next onboarding improvements much more concrete. This note covers only the work available in the records when the original draft was prepared.