> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getbased.health/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer documentation

> Developer guide index for getbased: architecture, data model, AI surfaces, feature internals, testing, deployment, and release gates.

# Developer documentation

getbased is authored in TypeScript and compiled with TypeScript 7. Local development loads the emitted JavaScript as native ES modules; hosted deployments use Rolldown bundles. Source-checkout development requires Node.js 24 and dependencies installed with `npm ci`. npm also provides tests, type checks, architecture checks, Playwright, and deployment tooling.

If you are new here, start with [CONTRIBUTING.md](https://github.com/elkimek/get-based/blob/main/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](/developers/architecture) | How the source-module graph, startup phases, lazy features, and production bundles fit together |
| [Module Reference](/developers/module-reference) | Finding the TypeScript module that owns a feature or window binding |
| [Cross-Module Patterns](/developers/cross-module-patterns) | Shared patterns: window exports, state access, dependency boundaries |

## Data model and sync

| Page | Use it for |
| - | - |
| [Marker Model and Category Placement](/developers/marker-model) | Generated schema authoring, stable marker identities, visual placement, and compatibility boundaries |
| [Laboratory Terminology Registry](/developers/marker-terminology) | LOINC, NPU, NČLP, and UCUM mapping isolation and update rules |
| [Data Pipeline](/developers/data-pipeline) | How `getActiveData()` builds the data used by charts and AI context |
| [Lab Markers and Range Internals](/developers/lab-markers-ranges-internals) | Marker identity, range precedence, collection and cycle context, calculations, and migrations |
| [Storage Schema](/developers/storage-schema) | localStorage, importedData, IndexedDB, export/import, and Agent Access state |
| [Report Data Contract](/developers/report-data) | Versioned selected-data snapshot shared by report rendering, summaries, and authorized integrations |
| [Sync and Delta Internals](/developers/sync-delta-internals) | Cross-device sync surfaces, tombstones, import snapshots, and merge rules |
| [Context Assembly](/developers/context-assembly) | How labs, context cards, wearables, notes, and Agent Access context are assembled |

## AI and agents

| Page | Use it for |
| - | - |
| [AI Surfaces Map](/developers/ai-surfaces-map) | Which features use AI and which are deterministic |
| [AI Provider Internals](/developers/ai-provider-internals) | Direct provider routing, cloud consent, private transports, Local AI, OAuth, and web search |
| [CLI agent providers](/developers/cli-agent-providers) | Loopback Companion, adapter and gateway boundaries, capabilities, tools, and lifecycle security |
| [System Prompt Catalog](/developers/system-prompts) | Every developer-controlled instruction family, source location, output contract, and review workflow |
| [Agent Access Relay](/developers/agent-access-relay) | Owner-bound encrypted context relay, setup payload, and local MCP decrypt behavior |
| [Local Lens Internals](/developers/lens-local-internals) | In-browser Knowledge Base storage, chunks, embeddings, and worker behavior |
| [Lens Endpoint Contract](/developers/lens-endpoint-contract) | Wire spec for an external Knowledge Source server |

## Feature internals

| Page | Use it for |
| - | - |
| [Biology Scores](/developers/biology-scores) | Score engine, coverage planner, context gate, adapters, UI, and tests |
| [Chat Internals](/developers/chat-internals) | Composer drafts, thread storage, editing and forks, discussions, personas, sync, and backups |
| [Genome Evidence Methodology](/developers/genome-evidence-methodology) | Catalog claim scope, evidence and relevance grades, privacy boundaries, and contribution review |
| [Supplements and Medications Internals](/developers/supplements-medications-internals) | Therapy lifecycle, reviewed imports, quality evidence, bounded AI context, migration, and sync |
| [Meals and Nutrition Internals](/developers/nutrition-internals) | Meal analysis, editable estimates, encrypted thumbnail storage, summaries, targets, benchmarks, sync, and AI context |
| [Sun Spectrum Model](/developers/sun-spectrum-model) | Bird-Riordan spectral reconstruction for Light sessions |
| [Wearables Internals](/developers/wearables-internals) | OAuth, local daily rows, synced summaries, runtime config, and Agent Access series |

## Operations and release checks

| Page | Use it for |
| - | - |
| [Testing](/developers/testing) | Test commands, browser specs, and how to add assertions |
| [Deployment](/developers/deployment) | Vercel config, CSP, service worker, API routes, and PWA behavior |
| [Legal Consent](/developers/legal-consent) | First-launch Terms/Privacy gate, re-consent, startup ordering, and release checks |
| [Routstr/Cashu Safety](/developers/routstr-cashu-safety) | Money-path invariants and required tests for wallet/node/session flows |
| [Codex PR Coverage Workflow](/developers/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.

Public guides belong here. The app repository keeps `AGENTS.md`, `ARCHITECTURE.md`, the generated `MODULE_MAP.md`, and maintained engineering contracts alongside executable checks. Task progress, checkpoints, and audit logs stay in its ignored `.local-notes/` directory.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.