Distillation

Date: Jul 30, 2026

• 🟡 (19:13) Fetched GitHub PR https://github.com/BYK/loreai/pull/1528 ("docs(website): position Lore as infrastructure, not a plugin"). PR was force-pushed on Jul 30, 2026 12:25 from f7df199 to 67b2c8f on branch docs/infrastructure-positioning; 9 commits added by BYK on Jul 30 11:09
• 🔴 (19:13) Mermaid integration pattern from loreai PR #1528: add mermaid@11.16.0 as a runtime dep of @loreai/website. Create new integration integrations/mermaid-renderer.mjs that uses injectScript to drop a bundled Mermaid renderer on every page (Starlight docs AND blog). Remove the CDN script from Starlight's head config — replaced by the bundled injector. Lockfile regenerated for the new dependency
• 🔴 (19:13) PR #1528 scope: 3 intended files changed (README.md, index.astro, the-embedding-trap.md). CI check from PR: pnpm --filter @loreai/website run check — 0 errors, 0 warnings; pnpm run format:check — clean
• 🔴 (19:13) PR #1528 narrative refactors documented (useful as prior art for tone shaping, not direct binpatch work): (1) "The Bet" section expanded from .lore.md-only to three pillars (local SQLite with open schema/distillations/LTM/entities, E2E encrypted sync engine, plus .lore.md) to tell the no-lock-in story across all artifacts; (2) LangChain counter reframed from "wrongness is self-serving" to "harness-first bias" — concede the point, extend the same lock-in logic to the harness (harness is what you swap, artifact is what stays); (3) three-level taxonomy — vendor-cloud DB (worst), harness-tied DB (better but harness changes), replaceable middle layer with local data (the rest of the way); (4) caption "Lore is the brain. The harness is the body. The model provider API is the cognition." was corrected — Lore is the memory layer, not the brain; LLM is the cognition; together they form the brain; harness is the body/actuator; (5) "export the corpus" changed from sqlite3 lore.db .dump to "copy the file" (the SQLite file IS the database); (6) Harrison three-levels placement: Claude Managed Agents = worst (whole harness + long-term memory behind API), Codex = separate case (open source but encrypted compaction summary) now placed alongside worst as creeping toward it; (7) intro/meta-description dropped awkward "local, sqlite & markdown" punchline for plain "plain Markdown and an open SQLite database" — the Mermaid box label still carries the original tight tag
• 🔴 (19:13) PR #1528 review-decision precedent: when a MUST-FIX is framed as a directive violation but the actual user instruction was scoped to a specific surface (e.g., Mermaid diagram label), the broader word choice should be reinstated. Specifically the word "proxy" was reinstated for product description, body intro, and README positioning line because it matches the existing "transparent LLM proxy" tagline on line 11 and "transparent HTTP proxy" architecture description on line 67