Opening reviewed archive snapshot…
Opening reviewed archive snapshot…
Engineering archive / CP-RECALL
A reviewed view of Recall's web, API, worker, transcription, curriculum and search boundaries.
Claim / Public evidence / Source / Limitation
Reviewed public claims with explicit confidence and proof boundaries.
The repository tree contains apps/web, apps/api, packages/shared, extension, docker and supabase migrations.
Inspect evidence +The product and infrastructure boundaries are inspectable.
The repository tree contains apps/web, apps/api, packages/shared, extension, docker and supabase migrations.
Repository layout does not prove all integrations are deployed or operational together.
The reviewed evidence is static public code, not a production runtime inspection.
Public worker files and Redis/RQ dependencies support the documented asynchronous processing boundary.
Inspect evidence +Long-running processing is represented outside request-response handlers.
Public worker files and Redis/RQ dependencies support the documented asynchronous processing boundary.
The files do not prove queue throughput, uptime or successful operation under production load.
No public runtime benchmark or production reliability evidence was used.
The code defines Groq and Whisper transcribers, provider selection and explicit transcription errors.
Inspect evidence +Fallback behaviour is represented by executable provider boundaries rather than marketing copy alone.
The code defines Groq and Whisper transcribers, provider selection and explicit transcription errors.
This does not prove transcript quality, provider availability or successful processing for arbitrary media.
The portfolio lab uses prepared segments and never calls either provider.
Public service files represent search, backend selection and indexing responsibilities.
Inspect evidence +Search is modeled as a subsystem rather than embedded in a page component.
Public service files represent search, backend selection and indexing responsibilities.
This does not prove that a Meilisearch instance is available or populated in production.
The lab concludes with a local fixture marked indexed, not a real search request.
These areas are directly visible under apps/api/app in the public repository.
Inspect evidence +The codebase exposes application responsibilities and persistence boundaries.
These areas are directly visible under apps/api/app in the public repository.
Folder separation does not prove perfect layering or absence of cross-layer coupling.
The X-Ray represents significant boundaries only and intentionally omits individual files.
The public README describes heuristic, OpenRouter, Ollama and auto provider modes, and the service tree contains provider boundaries.
Inspect evidence +The architecture distinguishes provider choice from the learning workflow.
The public README describes heuristic, OpenRouter, Ollama and auto provider modes, and the service tree contains provider boundaries.
Documentation and provider files do not prove model quality, cost, availability or production configuration.
The portfolio demonstration uses prepared concepts and does not execute AI.