Feature Namespaces and Domain Services

Feature Namespaces and Domain Services An architecture diagram generated by Archify. SourcesAPI · client.sources · Architecture component · operation scope SourcesAPI client.sources operation scope Upload Pipeline · own client · semaphore · Architecture component Upload Pipeline own client · semaphore Scotty Upload · start · finalize · byte transfer outside the RPC pipeline Scotty Upload start · finalize Asset Hosts · lh3 · usercontent · byte transfer outside the RPC pipeline Asset Hosts lh3 · usercontent NotebookLMClient · 11 namespaces · Architecture component NotebookLMClient 11 namespaces ArtifactsAPI · 11 generate_* flows · Architecture component · backend-neutral ArtifactsAPI 11 generate_* flows backend-neutral Generation Service · CREATE_ARTIFACT · Architecture component Generation Service CREATE_ARTIFACT Polling Service · leader · follower · Architecture component Polling Service leader · follower ChatAPI · lock · cache · turns · Architecture component · loop guard ChatAPI lock · cache · turns loop guard Stream Seam · _stream_answer · Architecture component Stream Seam _stream_answer Authed POST Path · executor · transport · Architecture component Authed POST Path executor · transport Android Services · session · upload · assets · Architecture component · opt-in Android Services session · upload · assets opt-in add_file resumable create task id rpc_call ask() streaming guarded byte transfer backend=android byte transfer outside the RPC pipeline Legend Backend Cloud

Source ingest

  • • The pipeline registers the file through ADD_SOURCE_FILE, then uploads with its own httpx client
  • • Upload uses epoch-fenced live Kernel cookies, not the RPC pipeline
  • • URL and Drive adds send mutating RPCs once; ambiguous outcomes surface for reconciliation

Artifacts

  • • ArtifactsAPI owns validation, source and language resolution for all eleven flows
  • • Polling is leader/follower over an abstract target-aware studio projection
  • • AssetDownloadService owns rejection, staging and atomic publication

Chat

  • • ChatAPI owns the conversation lock, cache, id recovery and turn numbering
  • • _stream_answer is the one custom request body and error mapping in the client
  • • AndroidChatAPI implements the same neutral base without the web seam