Developer documentation
getbased is a native ES module web app with no app bundler. It still uses npm for tests, type checks, Playwright, and deployment helpers. If you are new here, start with CONTRIBUTING.md for setup, local runs, tests, and PR guidelines. Use this section when you need implementation details that are too technical for the user guides.Start here
| Page | Use it for |
|---|---|
| Architecture | How the app is structured, started, and deployed without bundling app source |
| Module Reference | Finding the JS module that owns a feature or window binding |
| Cross-Module Patterns | Shared patterns: window exports, state access, dependency boundaries |
Data model and sync
| Page | Use it for |
|---|---|
| Data Pipeline | How getActiveData() builds the data used by charts and AI context |
| Storage Schema | localStorage, importedData, IndexedDB, export/import, and Agent Access state |
| Sync and Delta Internals | Cross-device sync surfaces, tombstones, import snapshots, and merge rules |
| Context Assembly | How labs, context cards, wearables, notes, and Agent Access context are assembled |
AI and agents
| Page | Use it for |
|---|---|
| AI Surfaces Map | Which features use AI and which are deterministic |
| AI Provider Internals | Provider routing, private transports, Custom API proxying, OAuth, and web search |
| Agent Access Relay | Owner-bound encrypted context relay, setup payload, and local MCP decrypt behavior |
| Local Lens Internals | In-browser Knowledge Base storage, chunks, embeddings, and worker behavior |
| Lens Endpoint Contract | Wire spec for an external Knowledge Source server |
Feature internals
| Page | Use it for |
|---|---|
| Biology Scores | Score engine, coverage planner, context gate, adapters, UI, and tests |
| Sun Spectrum Model | Bird-Riordan spectral reconstruction for Light sessions |
| Wearables Internals | OAuth, local daily rows, synced summaries, runtime config, and Agent Access series |
Operations and release checks
| Page | Use it for |
|---|---|
| Testing | Test commands, browser specs, and how to add assertions |
| Deployment | Vercel config, CSP, service worker, API routes, and PWA behavior |
| Legal Consent | First-launch Terms/Privacy gate, re-consent, startup ordering, and release checks |
| Routstr/Cashu Safety | Money-path invariants and required tests for wallet/node/session flows |
| Codex PR Coverage Workflow | PR review and coverage workflow for agent-assisted changes |
Maintenance rule
When adding a user-visible feature, update both sides in this repo:- the user guide that explains what the feature does and how to use it;
- the developer page that explains storage, sync, privacy, tests, and owner modules.