Current Context We are actively enhancing the homepage by replacing the About section with live Steam review data to improve user engagement and credibility, following recent alignment concerns. Active Projects 1. Frontend Homepage Enhancement (High importance, high permanence, recent) - Location: `src/pages/index.astro`, `src/components/Community.tsx`, `src/lib/steam.ts` - Status: Steam review integration complete; About section to be replaced with new component - Blockers: None identified - Next: Deploy to Cloudflare Pages and verify Steam review data loads 2. Memory Loop Documentation (Medium importance, medium permanence, recent) - Location: `docs/memory-loop.excalidraw`, `docs/memory-loop.mmd` - Status: Diagrams generated and stored - Blockers: None - Next: Reference for memory pipeline 3. Phoenix Model Parameters Check (Low importance, low permanence) - Location: Repository (not specific) - Status: Phoenix Ranker (~480K) and Retrieval Model (~600K) confirmed as demo-scale - Blockers: No training code exists in repository - Next: User question answered Recent Work - Implemented Steam review integration: extended `src/lib/steam.ts` to fetch individual reviews, created `src/components/Community.tsx`, and updated `src/pages/index.astro` to replace About section - Generated memory loop diagrams (excalidraw and mermaid) with emoji issues resolved - Clarified Phoenix models are inference-only with no training capability Technical Notes - Frontend: Astro static site deployed on Cloudflare Pages - Steam API: Requires `num_per_page > 0` for individual reviews (current implementation uses `num_per_page=0` for aggregate data) - Memory pipeline: Documented in `docs` with both visual and textual formats Rules & Warnings - ⚠️ Do not deploy Steam review component without testing data loading (prevents broken pages) - ⚠️ Phoenix models are inference-only – no training code exists; requires writing training loop from scratch - ⚠️ Always use `--release` when running Rust binaries to avoid debug mode performance issues