Skip to main content

Documentation Index

Fetch the complete documentation index at: https://orbit-docs.devotel.io/llms.txt

Use this file to discover all available pages before exploring further.

Architecture Decision Records

Architecture Decision Records (ADRs) capture the load-bearing decisions that shape Orbit’s architecture, billing posture, workflow, and compliance stance. Each ADR is short and factual; full operational context lives in the .serena/memories/ memos referenced at the end of each record. The set exists because prior agent sessions repeatedly re-proposed reverting decisions that were already locked. Future agents (and humans) read this directory before proposing architectural change.

Status legend

  • CURRENT — the decision is in force.
  • SUPERSEDED-BY-ADR-XXX — replaced by a newer ADR.
  • DEPRECATED — no longer in force; retained for audit trail.

Records

ADRTitleStatus
001Anthropic-only LLM stack with OpenAI carve-outsCURRENT
002Devotel softswitch is the sole outbound voice and SMS egressCURRENT
003Self-hosted orbit-media SFU replaces LiveKit CloudCURRENT
004Pay-as-you-go end-to-end — no tiers, no subscriptionsCURRENT
005BYO embedded-signup channels — no Orbit-side billingCURRENT
006Push (FCM) and Web Chat are always-free platform infrastructureCURRENT
007Single production environment — no dev / staging splitCURRENT
008Direct-to-main workflow — no long-lived branchesCURRENT
009Owner mode — Claude is technical owner; Erol is decision-makerCURRENT
010E911 block and disclaim — no PSAP routing pre-launchCURRENT
011Compliance gates default OFF; US TCPA voice is the only federal hard guardCURRENT
012Single Sentry project for all servicesCURRENT
013Design register — Modal / Resend / Stripe / Linear / VercelCURRENT
014Playwright banned for routine UI verificationCURRENT
015Migration prefix discipline — five grandfathered collisionsCURRENT

Authoring guidance

When adding a new ADR:
  1. Pick the next available NNN.
  2. Keep the body under ~200 words per the 2026 minimal-and-precise norm.
  3. Use the section structure: Context / Decision / Reason / Consequences / Source memos.
  4. Cross-link the relevant invariant numbers and Serena memos rather than duplicating their contents.
  5. If the new ADR supersedes an older one, update the older ADR’s status and add a SUPERSEDED-BY-ADR-XXX line.
ADRs sit alongside the rest of the developer docs so the decision history survives in git log and is permanently navigable in the rendered docs site.