Status: non-canonical orientation for commercial app surfaces.
Product law: .specifications/BITCODE_SPEC.txt and the draft-target V48 family under .specifications/. If this file conflicts with the SPEC, the SPEC wins.

This guide describes what ships as apps in the monorepo under V48 launch-freeze. Domain packages live under packages/. Engineering craft: .docs/AGENTS.md. Package map: .docs/FAMILIARIZATION.md. Layout: .docs/BITCODE_SOURCE_LAYOUT.md. Security: .docs/SECURITY.md. DataPack measurement orientation: .docs/ASSET_PACKS.md.

Not V48 launch scope: value-bearing mainnet; full Conversations commercialization; API/MCP and ChatGPT/Claude Apps as primary commercial paths; advanced market mechanics; deeper BTD mining cryptography beyond the website contract.

Those monorepo apps may still exist as compatibility / future-readiness surfaces — they must not regress source-safe contracts, but they are not the V48 website launch path unless a later gate reopens them (SPEC goals/non-goals).

See BITCODE_SPEC_V48_NOTES.md unpaid READ disclosure law. Pre-settle: title + summary + measurements only; settle rehydrates by synthesisRunId + indexes; post-settle PR on bitcode/ + rich Packs download; owner deposit always full.

TODO (document only — do not implement this pass): apply the same unpaid matrix + redaction to MCP, ChatGPT App, Claude App, and public API machine surfaces before they become commercial primary paths.

There is no root uapi/ or mcp/ symlink. Always use apps/uapi / apps/mcp (or pnpm filters).

Run website (local app + remote/staging DB posture as configured):

pnpm run dev:remote
# or
pnpm -C apps/uapi run dev:remote

Env, host, and deploy: .docs/DEPLOYMENT.md, .docs/VERCEL.md, .docs/SUPABASE.md, CONTRIBUTING.md.

packages/* (domain)
  → apps/uapi/lib, networking, hooks
  → components/shadcn (Shadcn*)
  → components/bitcode (Bitcode*)
  → experiences: Marketing | Packs | Reads | Deposits | Docs | Conversations | Auxillaries
  → app/* thin page shells only

Strict dependency direction: never experience → experience; never page client → page client; never packages → apps.

Compatibility (not product homes):

• Legacy /exchange (and similar cockpit paths) route into /exchange.
• Dead cockpit-only modules are deleted; do not rebuild Terminal or exchange cockpit as product.

Login / TPS wallet authorize and Supabase callbacks live under app shells such as /login and app/tps/* — infrastructure for identity, not separate product experiences. TPS holds third-party overlays (wallet OAuth, Supabase auth callback, GitHub App install/callback). Settlement money is BTC-testnet.

Depositor (/deposits)
  connect source + Obfuscations
  → SynthesizeDepositDataPacks (SDIVF)
  → source-safe option select / admit to Depository
  → /exchange activity + compensation expectation

Reader (/reads)
  Read Request → Need → Fits
  → source-safe preview → quote
  → BTC-testnet settlement → BTD rights → delivery
  → /exchange activity

Operator (Auxillaries + /exchange)
  wallet / GitHub authenticity, histories, portfolio readback

Every user-visible money or rights state must name its honesty class (estimate, potential, preview, quote, observed testnet payment, final settlement, rights transfer, delivery, compensation, repair) — see SPEC.

V48 product pipelines that the website drives:

SDIVF = Setup → Discovery → Implementation → Validation → Finish — the phased corridor for synthesis pipelines (packages/asset-packs-pipelines). It is not a V26 “Code Change → PR / Design Document → Issue” product matrix.

Agent composition inside steps (when used): PTRR (Plan → Try → Refine → Retry) with FailsafeGeneration parents and ThinkingsGeneration children (Reason → Judge → StructuredOutput). Vocabulary: .docs/TERMINOLOGY.md.

Hosts: long synthesis runs on pipeline hosts — Vercel sandbox (Pipeliner image) on serverless; LocalHost only on developer machines. See .docs/VERCEL.md and packages/pipeline-hosts.

Streaming: source-safe pipeline telemetry to the UI (Pipeline language); never stream secrets or protected source.

V48 Auxillaries are the operator / authenticity side of the website MVP — not a separate “Orbitals product suite” and not a prepaid usage dashboard.

Typical concerns (names follow components under apps/uapi/components/auxillaries/):

Wallet and GitHub authenticity gate commercial deposit/read actions. Do not invent bootstrap org authority the SPEC denies.

Marketing is not product law. Do not treat landing copy as SPEC.

Do not market these as the V48 GA website entrypoints. Do not regress source-safety or auth boundaries while they remain in-tree.

• Thin App Router handlers under apps/uapi/app/api/* (and related) adapt packages domain — they are not a second product.
• Edge middleware stack: telemetry → security headers → CORS → rate-limit → authentication → … (see .docs/SECURITY.md).
• Service-role Supabase clients are server only.

• Not the SPEC (no gate acceptance law here).
• Not a V26 / GA‑1 / “precision instrument” feature catalog (PR automation, design-doc issue bots, prepaid usage products, exponential “network effect” marketing copy, fake latency/SLA tables).
• Not package domain depth (use FAMILIARIZATION + ASSET_PACKS + package READMEs).
• Not env/deploy runbooks (use DEPLOYMENT / VERCEL / SUPABASE / CONTRIBUTING).

V48 website launch entrypoints: /deposits, /reads, /exchange, Auxillaries
Settlement: BTC-testnet · Rights: BTD · Unit: DataPack · Safety: source-safe always