**Weekly competitive synthesis - 2026-06-12 to 2026-06-18** --- **What changed** This is a setup report. All 26 signals collected across 43 configured sources are baseline captures with zero changed signals and zero material signals. No competitor made a detectable move during this window that differs from the established baseline. There is nothing to report as a competitive event. Collection ran across all 43 enabled sources. 30 succeeded, 13 failed, 0 were missing. Collection failures by source: - Gartner MQ Search and Product Discovery (https://www.gartner.com/en/documents/6633334): HTTP 403 Forbidden. Collection failure. - Lucidworks blog (https://lucidworks.com/blog): HTTP 403 Forbidden. Collection failure. - Lucidworks products (https://lucidworks.com/products): HTTP 403 Forbidden. Collection failure. - Yext products/search (https://www.yext.com/products/search): HTTP 503 Service Unavailable. Collection failure. - CMSWire Digital Experience: HTTP error on its single configured source. Collection failure. - OpenAI / ChatGPT: HTTP error on its single configured source. Collection failure. - Perplexity AI: HTTP error on its single configured source. Collection failure. - Algonomy: HTTP error on its single configured source. Collection failure. - AI Agent Ecosystem: one of two sources failed. Partial collection failure. - Community: three of four forum sources failed. Partial collection failure. - Elastic: one of three sources failed. Partial collection. Sources that were checked successfully and produced no changed signal are quiet, not silent. That includes Bloomreach (all 4 sources), Constructor (all 3), Coveo (5 sources checked, 3 returning HTTP 202 with no signal delta), Google Vertex AI Search (all 3), Meilisearch (both), Typesense (both), Yext blog, Elastic blog, AWS OpenSearch, Martech Edge, Glean, Contra Collective, and both Algolia MCP docs pages. --- **Strategic pattern** No strategic pattern can be asserted from this data. Every signal is a baseline snapshot, meaning the system has recorded the state of each source for the first time or confirmed an unchanged state. There is no delta to reason from. The collection infrastructure is functional across the majority of sources. The 403 failures on Lucidworks and Gartner are structural blockers that require engineering attention, not market interpretation. The Coveo sources returning HTTP 202 instead of 200 warrant a check on whether the extractor is handling that response code correctly and whether content is being captured. The forum category has a 75 percent failure rate (3 of 4 sources erroring), which will be a persistent blind spot on community voice and practitioner sentiment if not resolved before the next cycle. --- **Recommended actions by owner** Competitive Intelligence: - Confirm the system correctly interprets HTTP 202 responses from Coveo sources (https://www.coveo.com/en/blog, https://www.coveo.com/en/resources/case-studies, https://www.coveo.com/en/platform, https://www.coveo.com/en/solutions/commerce). If the extractor is silently discarding content on 202, these are effectively collection failures masquerading as successes. - Triage the three forum source failures. Community voice is the only signal category with a single captured signal this week out of four configured sources. Restoring forum coverage before next cycle is a collection health priority. Engineering / Ops: - Investigate 403 blocks on Lucidworks blog and product pages. These are tier-2 sources on a daily cadence returning persistent 403s. Either the crawler is being rate-limited and blocked, or the pages require authentication. Resolve or replace with an alternative access method. - Investigate 403 on Gartner MQ (https://www.gartner.com/en/documents/6633334). This is a gated analyst document. Either a licensed session cookie or a headless auth flow is needed. If neither is feasible, flag this source as permanently uncrawlable and route Gartner coverage through a manual review process. - Fix or replace the single failing AI Agent Ecosystem source and the single failing CMSWire source. Both have 100 percent failure rates on their respective covered URLs. - Confirm OpenAI / ChatGPT and Perplexity AI source failures are transient. Both are tier-relevant given the AI search narrative. If they are structurally blocked, find alternative URLs. --- **Battlecard updates** None. This is a setup report with no changed signals. Battlecard updates require confirmed competitive movement. No updates are warranted this cycle. --- **Coverage gaps** The following gaps are supported by the source coverage data: - Analyst coverage: collection failure on the single Gartner MQ source. No analyst signal was captured this week. This is a collection failure, not market quiet. - Lucidworks: both sources in collection failure. No signal of any kind available. Missing competitor visibility until the 403 is resolved. - Community and practitioner voice: 3 of 4 forum sources in collection failure. The single successful forum signal is a baseline. Effective forum coverage this week was 25 percent. - OpenAI / ChatGPT: single source, collection failure. No signal captured. - Perplexity AI: single source, collection failure. No signal captured. - Algonomy: single source, collection failure. No signal captured. - CMSWire Digital Experience: single source, collection failure. No signal captured. - AI Agent Ecosystem: partial collection failure (1 of 2 sources). Signal from this category is incomplete. Sources with no stored signal this week but no collection failure (quiet, not missing): - Coveo blog and case study pages returned HTTP 202 with no signal delta. Treated as quiet pending confirmation of extractor behavior noted above.