Lens / E.D.I.T.H.

Execution quality: safety, privacy and performance

Safety

  • The server never trusts client intent, role, tools, system text or selectors; unknown chat fields are dropped by the schema and guide ids must match a strict pattern.
  • Rate limiting runs before the pipeline with salted HMAC keys and a hard-bounded in-memory limiter; client IP is the Nth hop from the right of X-Forwarded-For, and a header shorter than the configured hops is never trusted. Within the first day a security review found a phone-redaction bypass (fixed with regression tests) and the client-IP resolution and limiter were hardened.
  • Policy gate order: distress first, then injection, explicit, private and abuse. Flagged and serious turns are never stored.
  • Tickets, allowlists, whole-plan validation before execution, sequential execution with compensating undo, and revalidation at execution time.
  • Studio content is published-only end to end, cleaned of links, emails, long numbers and markup, validated on both sides, and fails soft to her built-in behaviour.

Privacy

  • Session-only by default in the original design; saved chat is now on by default by an explicit owner decision (D80) but local-only, capped at 50 messages and 14 days, with a visible switch, a delete button and an export. Emails, phone-like numbers and secret-like text are never stored, and everything read back is re-validated.
  • Sound defaults on but never plays before a real user gesture.
  • No microphone, no voice and no webcam; capability data is never sent to analytics.

Performance and accessibility

  • Lazy by construction: an eager gate and avatar in the shell; the host is a separate chunk of about 5.8 KB gzip JS and 2 KB gzip CSS; the guide UI, detached chat, executor and local model are separate lazy chunks; Phaser is a single 1.08 MB chunk only the games fetch.
  • No global polling, no recurring inference loops, one timer slot for her idle life, CSS-only movement and nothing running while the tab is hidden.
  • Reduced motion collapses entrances to one fade, hands-on to an instant act and games skip particle bursts; tour buttons grow to 44 px on coarse pointers.
  • A pre-change Lighthouse baseline was captured before touching the shell (mobile 77, desktop 99) and the lock-screen pop-in is flagged for a Lighthouse check on every change.

Honest limitations

  • Answers are extractive: they quote and list published text and do not reason across records beyond Mind's counts, filters and comparisons.
  • The fact index changes only when the sync script runs, so a CMS change needs a rebuild.
  • Rate limits are per Node process; behind several instances the limits multiply.
  • Needle and the guide runtime depend on browser WebAssembly workers and real-browser verification that earlier docs flagged as not yet done in a GitHub-only authoring environment.
  • The tour is English only and apps without a guide get an honest summary instead of a walkthrough.