> For the complete documentation index, see [llms.txt](https://docs.internetobject.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.internetobject.org/collections/data-streaming.md). # Data Streaming How collections enable streaming of records. Because a collection is a sequence of independent records, it is naturally **streamable**: a producer can emit records over time and a consumer can process each as it arrives, without waiting for the whole document. ```ruby ~ $schema: { name: string, address: { street, city, state }, active: bool } --- ~ John Doe, { Red Street, Phoenix, AZ }, T ~ Alex, { Carnival Street, San Francisco, CA }, T ``` Further records for the same collection can be sent later in additional batches; a processor merges them into the same collection. Each record is validated on its own, so a malformed record does not interrupt the stream. > **The full protocol lives in its own chapter.** Framing, the stream-item model, schema and state, the error model, and reader and writer obligations are specified normatively in the [Streaming](/streaming/streaming.md) chapter. This page only shows why a collection is streamable; the contract is there. ## See Also * [Streaming](/streaming/streaming.md) — the normative, platform-agnostic streaming protocol * [Collection](/collections/collection.md) · [Collection Rules](/collections/collection-rules.md) * [Creating Collections](/collections/creating-collection.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.internetobject.org/collections/data-streaming.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.