Algolia-Central2 — Open Questions / Tracker

Living checklist. Check items off with a resolution line when answered; add new ones as they surface. Mirrors the P0/P1/P2 structure tracked interactively at bible.chowmes.com/ac2/tracker.html.

P0 — Tuesday deadline (2026-07-14)

• [ ] Full 3-journey scope (case study + pricing + homepage), or narrow to one journey done well? Scope-vs-deadline risk, not a data gap — see **2026-07-12-content-engagement-motion-decisions**.
• [ ] Which copy does the POC actually query against — enriched AC2 copy vs current production, or a merged view? See **data-health-final-verdict**.
• [ ] Screenshot sweep of representative case study / pricing / homepage pages — not started.
• [ ] GA / Looker Studio export — not started, needs Arijit's export or an authenticated browser session (dashboard not reachable via plain fetch).
• [ ] Joint UI/UX brainstorm: where engagement surfaces, what it says, at what journey point — blocked on the two items above.
• [ ] Build the actual Agent Studio embedding for the POC journey(s) — not started.

P1 — data quality, improves the POC

• [ ] Link-health sweep, both indexes.
• [ ] Category-structure backfill for Documentation/Developers/Customer Stories, both indexes.
• [ ] Dedupe current production data by URL.
• [ ] Filter job postings (category: Careers) from any product/marketing retrieval scope.
• [ ] Complete the enriched copy's body-enrichment pass to full coverage (currently 40.6%).
• [ ] Backfill Resources descriptions from underlying PDF/ebook assets (current production).

P2 — longer-term, safe to defer past Tuesday

• [ ] Auto-generate tags/keywords for empty records, both indexes.
• [ ] Differentiate description vs abstract where currently identical.
• [ ] Ask ingestion pipeline owner: is algoliaDisabled vestigial, or is disabled content filtered pre-index?
• [ ] Root-cause the 38x duplicate-chunk indexing bug with the crawl/ingestion pipeline owner.
• [ ] Root-cause why the enriched copy's topic metadata is thinner than the baseline's despite being derived from the same content.
• [ ] Escalate the shared Documentation category gap to the source content pipeline owner (fix once, not twice).
• [ ] Turn "build documentation as you go, becomes the project bible" into a reusable skill for other projects. Idea only, not started.

Resolved

• [x] Timeline, audience, success criteria, official naming, AC2 relationship — all resolved (2026-07-12): see **2026-07-12-content-engagement-motion-decisions**.