feat(server): EPIC-1 server pipeline — search API, backends, ingestion, dashboard, eval - #2
Merged
evidence-codes merged 16 commits intoMay 29, 2026
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ex status) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ion) Reference impls (in-memory store, stub embedder) behind protocols; pluggable backends via zetix_api.factory; /search and /admin endpoints with tests. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Lazy-imported torch/open_clip/PIL; 512-dim L2-normalised. Test skips without torch. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…hroma) Per-store cosine collections, JSON payloads, distance→score; idempotent clear(). Verified end-to-end. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…schema CSV/JSON/Shopify -> Product; Local/S3 ObjectStorage; SQLAlchemy models (no PII). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…earch-logs stub) Standalone FastAPI+Jinja2 app calling the API; search-logs is a stub pending a logs endpoint. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Runs through /admin/catalog->/search via 'make eval'. Synthetic set is high by construction; real M1 needs OpenCLIP + a 10k catalog. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 33479418 | Triggered | Generic Password | 1a65999 | server/docker-compose.yml | View secret |
| 33479514 | Triggered | Generic Password | b4f4cb5 | server/docker-compose.yml | View secret |
| 33479514 | Triggered | Generic Password | b4f4cb5 | server/docker-compose.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Use env-var substitution with dev defaults; drop the inline postgresql:// URI. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Fixes ModuleNotFoundError: fastapi in the eval job. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
EPIC-1 — Server Pipeline (Phase 1)
Builds out the Phase 1 server pipeline on top of the EPIC-0 mono-repo bootstrap. Foundation built directly; the five backend/feature slices were built by a parallel agent fleet (isolated worktrees) and integrated + verified here.
What's included
/search,/admin/catalog,/admin/index/status,/health.zetix_api.factory(env-selected).OpenCLIPEmbeddingService(ViT-B/32),ZETIX_EMBEDDER=openclip.ChromaVectorStore,ZETIX_VECTOR_STORE=chroma; verified end-to-end.ObjectStorage, SQLAlchemy models (no PII).make eval.Verification
ruff check server models→ clean.torchnot installed in CI/dev here).chromadbinstalled → ChromaDB backend verified live (/admin/catalog→/searchreturns the match).make evalruns the real pipeline (synthetic set; Top-3 100% by construction with the stub embedder).Status / honesty
EPIC-1 is 🟡 in progress, not complete. Dev-complete (🟢): search/ranking/admin (FR-06/34/35), both backends, ingestion, dashboard, eval harness. Still 🔴: TLS 1.3 (1.C.5), a real 10k labelled eval set (1.E.1), and the M1 acceptance bar — Top-3 > 80% on a real catalog (1.E.4) — which needs
ZETIX_EMBEDDER=openclip+ real data. OpenCLIP is code-complete + lint-clean but not runtime-verified here (notorch).Per the working agreement, these are 🟢 (dev-complete) pending owner verification → ✅.
🤖 Generated with Claude Code