Add /vs/letta comparison page - #248
Open
jy7lsna wants to merge 1 commit into
Open
Conversation
Contributor
|
@jy7lsna is attempting to deploy a commit to the Statewave Team on Vercel. A member of the Team first needs to authorize it. |
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
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.
Description
Adds
/vs/letta, a new comparison page contrasting Statewave against Letta's agent-managed memory model. Deliberately mirrors the structure, components, and tokens of the existing/vs/mem0page — same section order (hero → gap → ranking signals → capability comparison → worked example → governance/receipts → benchmarks → migration → FAQ → CTA), just with the Letta-specific argument: Letta hands memory tools to the model itself (core/recall/archival tiers, agent-driven retrieval), Statewave assembles a deterministic, token-bounded context bundle mechanically with policy on the read path and an integrity-hashed receipt.Related Issue
No linked issue this was scoped directly, not tracked against an existing ticket.
Type of Change
Changes Made
src/pages/StatewaveVsLettaPage.tsx: hero, memory-tier comparison, ranking-signal breakdown, full capability comparison table, worked support-agent example, governance/receipt section, benchmark section (Statewave's fixed LoCoMo/LongMemEval scores as gauges vs. Letta's own published Context-Bench leaderboard rendered as a score distribution, sourced fromleaderboard.letta.comon 2026-08-12), migration cheatsheet, and FAQ.src/App.tsx(lazy-loaded), added a footer link insrc/components/Footer.tsx, and added the/vs/lettaentry (title, description, breadcrumb, OG type) tosrc/lib/seo-meta.ts.tests/vs-letta-page.test.tsxand extendedtests/routes.test.tsxto cover the new route.Testing
Test Commands Run
Both clean (25/25). Also manually checked the page in-browser across light/dark and mobile/tablet/desktop widths (375–1920px).
Checklist
Screenshots / Recordings
Additional Notes