Source Ingest Data Flow

Source Ingest Data Flow A data-flow diagram generated by Archify. 01 / Input 02 / Register 03 / Transfer 04 / Index 05 / Consume Local File · pdf · md · audio · 01 / Input · bytes Local File pdf · md · audio bytes No-byte Inputs · URL · text · Drive · 01 / Input · + Play Books No-byte Inputs URL · text · Drive + Play Books Upload Pipeline · Web · Android control · 02 / Register · own client Upload Pipeline Web · Android control own client Source Add Services · validate · register · 02 / Register · idempotent Source Add Services validate · register idempotent Scotty · resumable upload · 03 / Transfer · start · finalize Scotty resumable upload start · finalize Selected Backend · batchexecute · gRPC · 03 / Transfer Selected Backend batchexecute · gRPC NotebookLM Indexer · server-side parse · 04 / Index · async NotebookLM Indexer server-side parse async Source Rows · Web · Android rows · 04 / Index · status field Source Rows Web · Android rows status field wait_for_ready · poll until READY · 05 / Consume · PROCESSING wait_for_ready poll until READY PROCESSING Grounded Use · chat · artifacts · 05 / Consume Grounded Use chat · artifacts register file metadata first register source selected backend upload bytes outside RPC mutating RPC probe guarded finalized blob server owned source created server owned status updates PROCESSING then READY polled rows read-only ready sources usable Legend primary data async batch data store data flow

Two ingest shapes

  • • File adds register metadata, then move bytes outside the RPC path
  • • The Android backend mirrors both shapes over gRPC plus its own upload pipeline

Duplicate safety

  • • Web URL and Drive mutations are probe-guarded by idempotent_create
  • • Text and Play Book adds register through the selected backend

Readiness

  • • SourceStatus: PREPARING, PROCESSING, READY, ERROR, UNKNOWN
  • • Only READY sources can ground chat or artifact generation