rob thijssen
8dd82776f1
The secondary narrative page, re-focused (vs the reference placeholder) to lead with European digital sovereignty. - Renamed the `home` i18n namespace → `mission` (32 langs' home.json → mission.json; updated i18n/index.ts imports + ns list and the check-i18n NAMESPACES). The reference's narrative content was already translated, so the non-English languages carry over as mission copy. - Rewrote en/mission.json to lead with sovereignty: data residency, a GDPR-native no-server-side-history stance, EU operator ownership, region-affine routing, and independence from US hyperscalers — same key structure, so cross-language parity holds. - src/pages/Mission.tsx ported from the reference Home page (sections: hero/intent/whyNow/howItWorks/principles/roadAhead/joinMesh) bound to the `mission` namespace; routed at /mission in App.tsx (the Header link from F1 now resolves). Validated: npm run lint, typecheck, build all green; i18n:check (mission namespace consistent across all languages) and i18n:lang-labels pass. Explicit-path commit; no node_modules/dist. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F6o3ddqmYNh9kzdwq6eowh
helexa.ai
The public-beta frontend for the helexa mesh: a chat-first landing experience
(anonymous + authenticated, with all chat history kept client-side in
IndexedDB — no server-side history), a /mission page on European digital
sovereignty, and full account self-service (register, recover, manage API
keys, set per-key limits, redeem top-up codes) against helexa-upstream.
Vite + React (SWC) + TypeScript + react-bootstrap + react-router + react-i18next. Lives as a top-level folder in the cortex monorepo; it is not a Cargo crate.
Develop
cd helexa.ai
npm install
cp .env.example .env.local # adjust backend URLs
npm run dev # vite dev server, proxies /v1+/health → router, /api → upstream
Other scripts: npm run build (tsc -b && vite build → dist/), npm run preview, npm run lint, npm run typecheck.
In dev, vite.config.ts proxies the mesh data-plane (helexa-router) and the
account control-plane (helexa-upstream) same-origin. Run a local router
(cargo run -p helexa-router) for the chat path and a local helexa-upstream
for the account path.
Status
F0 scaffold. Theming + i18n (33 languages, usage-ordered selector), the
/mission page, the chat workspace (Dexie + streaming), and the account
dashboard land in subsequent phases — see
~/.claude/plans/we-need-to-plan-modular-graham.md.