Overview — Algolia-Central-Spectrum (ACS)

Why this exists

Algolia-Central2 (AC2) proved a strictly-grounded, neural conversational-agent panel (General / Developer / Marketer) on Algolia's own corpus. ACS forks that proven build for Adobe as the prospect — same architecture, prospect's own docs. It demonstrates the AC2 pattern is corpus-portable: point it at any company's documentation and get a grounded agent panel.

What ports from AC2 (don't reinvent)

• 3-agent panel — persona prompts + disjoint source clubbing via native searchParameters.filters on ONE index. See AC2 scripts/setup/honed/build_three_agents.mjs + instructions_{general,developer,marketer3}.md + _shared_grounding.md.
• Grounding contract — SEARCH-FIRST, hit-sourced-only, bait-query verification.
• Handoff — prompt doctrine + client-side baton (Agent Studio has no native handoff tool).
• Judge / eval harness — AC2 lab/server + web (P2b calibration gate carries over).

What changes for ACS

• Corpus = Adobe / Spectrum content, not Algolia's. Source clubbing / persona split may differ from AC2's 9 sources — depends on the Adobe corpus shape.
• Agent namespace = ACS-* (disjoint from ac2-*).
• Ingest path = OPEN: hand-built crawler-army (as AC2) vs. Algolia DocSearch MCP (curated DocSet + NeuralSearch) as the retrieval layer. DocSearch offloads crawl+index+retrieval but not the grounded-agent + judge layer.

Corpus source (to confirm)

https://algolia-central.vercel.app/docs (Spectrum repos, per Arijit 2026-07-01) + Adobe/Spectrum docs.

See open-questions for the decisions that gate the build.