Algolia-Central

Active-Context.md

Algolia Central — Active Context

Read this FIRST when opening any session for Algolia Central. It's the top-of-mind briefing. Vault is memory; this file is the current state of that memory.


⚡ One-paragraph state

Algolia Central is mid-pivot from POC to Product. RC2-Algolia was sealed 2026-04-22 after being publicly demoed at Adobe Summit — first stable public release. RC3-Phoenix was born the same day to carry the pivot: POC → Product, native-Algolia refactor, prescriptive reference implementations, production-readiness from day 1. Pilots on the table (Adobe Brand Concierge, MasterCard, direct customers, Adobe-partnered pilot). Research gate R1–R12 is open and blocks most downstream work. Agent Factory (WS8) is the highest-leverage next move.

Sister project — Crawler Factory (Layer 1, Data Layer). First connector for Central; shipped v1 functional spike 2026-04-30; pivoted to UX + design language in Session 2 (2026-05-03), portable design pack v1.1 frozen. See Status for live state. Cross-jump: Crawler-Factory-Pointer.


🎯 Active task (what's happening right now)

2026-05-01: Two SOP-verified build specs ready. Next session switches to Sonnet and builds.

What's been done (2026-04-30)

  • structure_response client tool added — guaranteed section formatting
  • format_quote client tool added — styled pull-quote card
  • bestContent tracking added to runToolLoop — preserves answer across multi-iteration loop
  • RC2 FINAL DIRECTIVES pattern applied — 5-rule numbered policy at end of INSTRUCTIONS
  • Prose suppressed when structured_sections present (ChatMessage.tsx guard)
  • Date injection at top of INSTRUCTIONS (Maverick knows current date)
  • hitsPerPage: 20 in /api/prepare-dossier (customer stories now reach dossier)
  • Discovery card fires immediately via setDiscoveryCard immediate push
  • Committed at f3294671

Active plan

rc3-phoenix/docs/superpowers/plans/2026-04-30-maverick-quality-phase1.md — 4 regression fixes (Issues 1–4 from cleanup-plan.md) + Phase 1 config centralization. Currently executing via subagent-driven development.

RC3-Phoenix state

  • Branch rc3-phoenix at f3294671
  • Maverick UUID: 6824bd5e-3ee9-4026-9af0-674aafe66d28 (app 0EXRPAXB56)
  • Tests: 98/98 GREEN
  • tsc: CLEAN
  • Dev ports: API=3005, Vite=5173

Background context (still valid): - Master plan: Projects/Algolia-Central/Plans/Maverick-Migration.md - Path β chosen 2026-04-26: Migrate Maverick from lib/search/orchestrator.ts into Agent Studio app 0EXRPAXB56. - Wiki COMPLETE 2026-04-25: Projects/Algolia-Central/Knowledge/AgentStudio/ — 12 sections + 6 evidence cards. - Content Engagement positioning. Confirmed pilots: Sherwin Williams + MasterCard.

Background context (still valid): - Master plan: Projects/Algolia-Central/Plans/Maverick-Migration.md - Path β chosen 2026-04-26: Migrate Maverick from lib/search/orchestrator.ts into Agent Studio app 0EXRPAXB56. - Wiki COMPLETE 2026-04-25: Projects/Algolia-Central/Knowledge/AgentStudio/ — 12 sections + 6 evidence cards. - Content Engagement positioning. Confirmed pilots: Sherwin Williams + MasterCard.


🗺 Release state (pointer to authoritative record)

  • RC2-Algolia — SEALED ✅ at tag rc2-algolia-final (commit d2df6a19), 2026-04-22.
  • RC3-Phoenix — ACTIVE 🚀, branch rc3-phoenix, latest commit a5468ba5.
  • Full release history: Projects/Algolia-Central/Releases.md.

If you need to know… Read this (in order)
Current state of the project This file → Releases.mdMessaging-Positioning-Pivot.md
The 2026-04-22 pivot directional commitments Messaging-Positioning-Pivot.md §2
The 9 workstreams + dependency graph Messaging-Positioning-Pivot.md §15 (in repo plan)
R1–R12 research gate Messaging-Positioning-Pivot.md §3 (vault) + plan §13 (repo)
The validated story (pitch that resonated at Summit) repo: docs/superpowers/plans/2026-04-22-messaging-positioning-pivot.md §7
Raw source (Arijit's typed stream-of-consciousness) repo: docs/superpowers/plans/2026-04-22-Going-Production-raw-source.txt
Verbatim 12-message capture repo: docs/superpowers/plans/2026-04-22-messaging-positioning-pivot-scratchpad.md
Production readiness pillars Messaging-Positioning-Pivot.md §6 (vault) + plan §16 (repo)
Shared-responsibility matrix plan §16
Known defects (Maverick, handoff) plan §18
Code-writing rules Standards/CodingSOPs.md
Testing rules Standards/TestingSOPs.md
Folder structure rules Standards/FolderStructure.md
Writing deliverables Standards/WritingSOPs.md
Architecture principles Architecture/Manifesto.md
Module contracts Architecture/Module-Contract.md
Adapter interfaces (Connectors/Transformers/Fetch) Architecture/Adapter-Interfaces.md
Evidence tier spec (shared-responsibility) Architecture/Evidence-Tier-Spec.md
Validation patterns (R11 production readiness) Architecture/Validation-Patterns.md
Agent harness patterns (WS8 factory) Architecture/AgentHarnessPatterns.md
Decision log Architecture/DecisionLog.md
Agent Studio knowledge base (prompt + agent + tool refactoring) Knowledge/AgentStudio/README.md → routes to 12 sections + evidence cards
Refactoring an existing agent's prompt Knowledge/AgentStudio/03-prompt-patterns.md + 10-our-agents-vs-best-practice.md
Designing index strategy / multi-index routing Knowledge/AgentStudio/06-multi-index-routing.md
UI refactor + InstantSearch adoption Knowledge/AgentStudio/12-ui-and-instantsearch.md
Choosing tool set / output shape for an agent Knowledge/AgentStudio/02-tool-types.md + 04-agent-archetypes.md + 05-output-shape-decision.md

🔑 Non-negotiables (RC3-specific, additive to global rules)

  • Branch hygiene: All RC3 work on rc3-phoenix. Never commit to rc2-algolia or main. Tag milestones (rc3-phoenix-alphaN, etc.).
  • Code guards: Do not touch lib/search/prompts/maverick.ts without explicit approval. Do not re-add F-041 short-circuit. Render-path-first on UI bugs.
  • Refactor compass: Move-to-native-Algolia. Delete anything rc3 reinvents that Algolia primitives handle.
  • Availability: Live refactor — Algolia Central stays demoable through re-architecture.
  • Validation first: AI-structured plans must be validated against raw source before acting on them.
  • Verbatim capture: Scratchpad-first, structure-second for strategic sessions.
  • Research is the gate: Agents cannot be re-specified before R1–R12 close.
  • API bundles: Rebuild node scripts/bundle-api.mjs + commit api/*.mjs after backend changes.

🧱 Current workstream sequencing

Ready to start (3 parallel tracks): - Track A — WS8 Agent Factory + R1–R12 research gate - Track B — WS9 Bootstrap Defect Remediation (Maverick fix, handoff reliability) - Track C — WS5 Story / Positioning (category renaming R9, value-prop sharpening)

Holding (gated on research + WS8): - WS1 Architecture, WS2 Design, WS3 Refactoring, WS4 Use Cases, WS6 Presentation, WS7 Production Readiness


❓ Top critical open questions

  • Q13: What replaces "content search" as the category framing? (blocks WS5/WS6/WS4)
  • Q18: Agent factory starting roster — validate or edit the 13-agent draft? (blocks WS8)
  • Q11: Do Maverick/Elena/Bruno survive re-architecture, get renamed, or get replaced? (blocks WS1/WS9)
  • Q20: Fix Maverick-skips-follow-up now (bootstrap patch) or defer to refactor? (blocks WS9)

Full list: Messaging-Positioning-Pivot.md §7 (vault) + plan §4 (repo).


🔄 Update protocol (for this file)

  • Update this file whenever the active state changes — new active task, new release sealed, new blocker, major decision.
  • Do NOT let this file bloat — it's a briefing, not a plan. Deep detail lives in Messaging-Positioning-Pivot.md + repo plan.
  • Cross-reference everything; never duplicate content.
  • This file + Releases.md + Messaging-Positioning-Pivot.md form the vault trio for Algolia Central. All other files are supporting detail.