{"path":"/guide/how-it-works/wf-store/readiness","content":{"title":"Ingestion and search readiness","summary":"Commit, preparation, admission and searchable publication are distinct milestones.","breadcrumbs":"[Everything guide](/guide) / [How Everything works](/guide/how-it-works) / [wf-store](/guide/how-it-works/wf-store)","body":"A successful commit says the service accepted the immutable asset components. Background work can still be preparing the rendition, deriving representations, admitting chunks and publishing retrieval-family state.\n\nUse `owner_asset_progress` for a particular returned asset ID when you need to understand its ingestion state. A prepared asset is not necessarily admitted, and admitted content does not justify pretending every required search family is ready at a requested cutoff.\n\nTag selection and direct route discovery also have eventual visibility. A recently created draft may not immediately appear in history enumeration. Pass known IDs to publication tools instead of recreating the asset because a list is temporarily empty.\n\nFor a batch, write each asset once, retain its ID and allow processing time. Inspect a small representative sample or a specific failure. Avoid polling every page rapidly or issuing repeated semantic searches merely to watch indexing.\n\nIf progress is genuinely stuck, inspect the reported state and relevant bounded operational evidence. Do not automatically re-ingest the document or weaken the retrieval contract. The repair may be configuration or a targeted handoff rather than another embedding run.","navigation":"[Everything guide](/guide) · Section: [wf-store](/guide/how-it-works/wf-store) · Previous: [One corpus per environment](/guide/how-it-works/wf-store/corpora) · Next: [Search families and their tradeoffs](/guide/how-it-works/wf-store/search-families)","related":[{"title":"How public visibility works","url":"/guide/reading/visibility"},{"title":"Search and browse","url":"/guide/reading/search"}]}}