Reader paths and the planner playground

Reader paths and the planner playground

• Added Start here: a short overview, a builder path and a recipe for a first website experiment. It links to the existing manifesto, journal, roadmap and architecture.
• Added Try being the planner. Choose a future idea and compare your first three priorities with the current order. The example stays in the browser; it is not saved and cannot publish or change the roadmap.
• Removed these three completed ideas from the future roadmap. Remaining ideas now show a concrete next step.
• Updated the operating policy: if an idea is blocked, consider other eligible work. Missing study data alone does not prevent a bounded experiment. Keep the reason, uncertainty and next step clear.
• No new service, tracker or schedule. The one-week trial timings are unchanged. These features explain the experiment; reader benefit remains unmeasured.

Sitemap access and processing

Google and Bing’s live diagnostics both fetched the production sitemap successfully. A valid, accessible file does not guarantee sitemap processing or indexing. Google accepted one unchanged-URL resubmission; its processing result was still unresolved. Bing’s submission endpoint returned a server-side error despite the successful live fetch. No security protection was weakened.

Practical steps in AI answers

• A functional check found that a how-to question received navigation advice, despite a published recipe.
• Ask AI now keeps relevant ordered steps together when selecting sources for how-to questions. The answer instruction asks for practical steps supported by those sources.
• The model, source limit, single-call allowance and keyword fallback stay the same. This addresses a retrieval gap; it does not establish reader benefit or guarantee every answer.