Dashboard/Algolia-Central/Releases.md
Algolia-Central

Releases.md

Algolia Central — Release History

This is the authoritative record of Algolia Central's release lines. When a session asks "which release are we on?" or "what was shipped?" the answer comes from here, not from git alone.

🟢 RC2-Algolia — FIRST STABLE RELEASE

  • Status: SEALED ✅ — 2026-04-22
  • Git tag: rc2-algolia-final (commit d2df6a19)
  • Branch: rc2-algolia (also = main, both at the tag)
  • Working directory (sealed): /Users/arijitchowdhury/AI-Development/RAG/AlgoliaRAG-Google/rc2-algolia/
  • Significance: The first time the world saw Algolia Central. Publicly demoed at Adobe Summit 2026 (Apr 20–22). First stable public-facing release of the concept. POC phase closed here.

What RC2 delivered

  • Demoable Algolia Central system (Maverick + Elena + Bruno agent trio).
  • Agent Studio Atlas + Search dual-tool architecture (precision + breadth).
  • Content engagement flow (renamed from "field report").
  • Pipeline audit Phases 1–2 (instrumentation + per-link HTTP checks).
  • Dead-code cleanup (partial — not all finished pre-pivot).
  • Survived the show-floor Gemini deprecation incident (Apr 20) via hotfix to gemini-2.5-flash-lite.

What RC2 validated (from Summit)

  • Story resonates. Nobody said no.
  • Adobe Brand Concierge team wants to pilot.
  • MasterCard expressed strong interest.
  • Other customers + SI partners curious.
  • Pilot framework forming: Adobe Brand Concierge + 1–2 direct customer pilots + 1 Adobe-partnered pilot.

RC2 limitations (known at seal)

  • Bootstrap data layer — index schema, weights, normalization are placeholder, not production.
  • Maverick skips follow-up questions (P0 demo defect).
  • Handoff touch-and-go (P1 reliability).
  • Production-readiness gaps: guardrails, security, brand, zero-hallucination not yet architectural.
  • No per-use-case reference implementations yet.

RC2 archive location

All pre-pivot docs moved into docs/archive/pre-pivot-notes/ on commit d2df6a19. Sibling /rc3-phoenix/ docs-only dir (pre-pivot audit notes + V2 screenshots) absorbed into same archive. History preserved via git mv.

🚀 RC3-Phoenix — ACTIVE: Production Pivot

  • Status: ACTIVE — born 2026-04-22
  • Git branch: rc3-phoenix
  • Working directory: /Users/arijitchowdhury/AI-Development/RAG/AlgoliaRAG-Google/rc3-phoenix/
  • First commit: 70ef4ec4 (d2df6a19 + today's pivot files)
  • Latest: a5468ba5 (SESSION + RESUME_PROMPT + CLAUDE.md)
  • Significance: POC → Product pivot. Takes the validated RC2 story and rebuilds the product at production grade: layered architecture, native-Algolia primitives, prescriptive reference implementations, production-readiness from day 1.

RC3 thesis (what we're building)

  • Algolia Central = unified knowledge base with intelligence.
  • Category: beyond "product search" — sharper framing TBD (R9).
  • Reference implementation = the product (prescriptive, per-use-case, not a toolkit).
  • Neural-search configuration tuning = proprietary IP.
  • Dual deployment modes: (A) Algolia-as-agent-platform + (B) Algolia-as-knowledge-source.
  • Shared-responsibility delivery: Algolia ships data + guardrails; customer owns front-end + audit.

RC3 arc (phases, per plan §14)

  1. Phase 1: Close R1–R12 research gate.
  2. Phase 2: Define purpose-built agents (post-research).
  3. Phase 3: Build the prescriptive reference implementation.
  4. Phase 4: Pilots (Adobe Brand Concierge + direct customers + partner-Adobe).
  5. Phase 5: Package hardens into sellable SKU.

RC3 workstreams (9 total, see Messaging-Positioning-Pivot.md §15)

WS8 Agent Factory (first) → WS1 Arch → WS2 Design → WS3 Refactor → WS4 Use Cases → WS7 Production Readiness. WS5 Story + WS6 Presentation run parallel. WS9 Defect Remediation protects demos.

RC3 research gate (12 items, R1–R12 — see Messaging-Positioning-Pivot.md §3)

Connectors inventory, normalization, enrichment, crawler strategy, transformations, canonical schema, neural-search tuning, category naming, use case specs, production readiness, defects.

RC3 success criteria

  • R1–R12 closed with evidence-backed deliverables.
  • Reference implementation demoed to pilot customers with measurable uplift.
  • Shared-responsibility contract signed with at least one pilot partner.
  • Production-readiness gates passed (guardrails, security audit, zero-hallucination verified).

When RC3 seals → RC3.x patches or RC4-?

TBD. Criteria for seal: first paying pilot live on reference implementation, customer audit-ready.

Historical pre-RC2

  • RC1-Maverick — predecessor branch + sibling dir. Preserved, not in active scope.
  • .algolia-central-deprecated/ — earliest prototypes. Preserved, not in active scope.

Release protocol (going forward)

  • Each release gets a section in this file when sealed (tag + date + significance + what shipped + limitations).
  • Active release gets "ACTIVE" status with current state.
  • Next release opens as draft under "Planned" when committed.
  • Vault = authoritative source. Git tags mirror vault. Memory references this file by name.
  • When a session asks "what release are we on?" — answer FROM THIS FILE, not from git log.