Go LLM Operations for Marketplace Knowledge Bases: Async Jobs Versus Live Output

Use asynchronous batch jobs for large or numerous private documents, and use streaming chat for a person waiting on one answer. The important implementation choice is the recovery contract: a lost response must be safe to replay, and a completed summary must be safe to write twice. For a marketplace knowledge base, I would keep that contract inside a Go adapter so changing the model provider does not change document ownership, revision tracking, or rollback.

The first operational rule is simple: assign a stable identity before sending work. Persist the document revision, chunk manifest, prompt revision, provider choice, and attempt state.…