@talonic/docs 0.20.18 → 0.20.19

package/dist/content.js

@@ -1,5 +1,5 @@
 // src/content/helpers.ts
-function deriveBreadcrumbs(sections52, leafId, domain) {
+function deriveBreadcrumbs(sections55, leafId, domain) {
   const domainLabels = {
     api: "API Reference",
     platform: "Platform Guide",
@@ -10,20 +10,20 @@ function deriveBreadcrumbs(sections52, leafId, domain) {
     label: domainLabels[domain] ?? domain,
     slug: domain
   };
-  for (const group of sections52) {
+  for (const group of sections55) {
     const child = group.children?.find((c) => c.id === leafId);
     if (child) {
       return [root, { label: group.label, slug: group.id }, { label: child.label, slug: child.id }];
     }
   }
-  const topLevel = sections52.find((s) => s.id === leafId);
+  const topLevel = sections55.find((s) => s.id === leafId);
   if (topLevel) {
     return [root, { label: topLevel.label, slug: topLevel.id }];
   }
   return [root];
 }
-function derivePrevNext(sections52, leafId) {
-  const flat = sections52.flatMap(
+function derivePrevNext(sections55, leafId) {
+  const flat = sections55.flatMap(
     (s) => s.children ?? [{ id: s.id, label: s.label }]
   );
   const idx = flat.findIndex((c) => c.id === leafId);
@@ -250,6 +250,29 @@ var API_NAV_SECTIONS = [
   { id: "registry", label: "Registry", children: [
     { id: "registry-query", label: "Query" }
   ] },
+  { id: "data-products", label: "Data Products", children: [
+    { id: "list-data-products", label: "List Data Products" },
+    { id: "get-data-product", label: "Get Data Product" },
+    { id: "delete-data-product", label: "Delete Data Product" },
+    { id: "get-data-product-results", label: "Get Results" }
+  ] },
+  { id: "data-policies", label: "Data Policies", children: [
+    { id: "list-data-policies", label: "List Policies" },
+    { id: "create-data-policy", label: "Create Policy" },
+    { id: "get-data-policy", label: "Get Policy" },
+    { id: "update-data-policy", label: "Update Policy" },
+    { id: "delete-data-policy", label: "Delete Policy" },
+    { id: "list-data-policy-versions", label: "List Versions" },
+    { id: "list-data-policy-fields", label: "List Fields" },
+    { id: "list-data-policy-rules", label: "List Rules" }
+  ] },
+  { id: "record-sets", label: "Record Sets", children: [
+    { id: "list-record-sets", label: "List Record Sets" },
+    { id: "get-record-set", label: "Get Record Set" },
+    { id: "list-record-set-fields", label: "List Fields" },
+    { id: "list-record-set-records", label: "List Records" },
+    { id: "export-record-set", label: "Export" }
+  ] },
   { id: "billing", label: "Billing", children: [
     { id: "billing-settings", label: "Settings" },
     { id: "billing-topup", label: "Auto Top-Up" },
@@ -25906,6 +25929,1500 @@ var sections49 = [
   }
 ];
 
+// src/content/api/data-products.ts
+var sections50 = [
+  {
+    slug: "list-data-products",
+    parentSlug: "data-products",
+    title: "List Data Products",
+    seoTitle: "List Data Products Endpoint \u2014 Talonic Docs",
+    description: "List assembled data products with cursor-based pagination. Filter by status to find active, draft, or archived products across your workspace.",
+    content: [
+      { type: "paragraph", text: "Data products are the final assembled output datasets produced by the Talonic pipeline. Each data product represents a structured, validated, and optionally resolved collection of records ready for downstream consumption. Data products are created automatically when a job run completes validation, or manually via the platform UI." },
+      { type: "paragraph", text: "Use this endpoint to list all data products in your workspace. Results are returned in reverse chronological order by default and support cursor-based pagination. You can filter by status to find only active products, or locate draft and archived products for lifecycle management." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/data-products",
+        summary: "List data products with optional status filter and cursor-based pagination.",
+        description: "Requires read scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "status", type: "string", description: "Filter by product status (e.g. active, draft, archived)." },
+              { name: "limit", type: "integer", default: "20", description: "Maximum number of items to return (1-100)." },
+              { name: "cursor", type: "string", description: "Opaque pagination cursor from a previous response." },
+              { name: "order", type: "string", default: "desc", description: "Sort order by creation date (asc | desc)." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "list-data-products-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "data", type: "array", description: "Array of data product objects." },
+          { name: "data[].id", type: "string", description: "Data product UUID." },
+          { name: "data[].name", type: "string", description: "Human-readable product name." },
+          { name: "data[].description", type: "string | null", description: "Optional description of the data product." },
+          { name: "data[].schema_id", type: "string", description: "UUID of the user schema that defines the output columns." },
+          { name: "data[].run_id", type: "string", description: "UUID of the source job run that produced the data." },
+          { name: "data[].status", type: "string", description: "Product status: active, draft, or archived." },
+          { name: "data[].created_at", type: "string", description: "ISO 8601 creation timestamp." },
+          { name: "data[].updated_at", type: "string", description: "ISO 8601 last update timestamp." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s https://api.talonic.ai/v1/data-products?status=active&limit=10 \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "data": [
+    {
+      "id": "d1a2b3c4-e5f6-7890-abcd-ef1234567890",
+      "name": "Q4 Invoice Extract",
+      "description": "Structured invoice data from Q4 batch",
+      "schema_id": "s1a2b3c4-e5f6-7890-abcd-ef1234567890",
+      "run_id": "r1a2b3c4-e5f6-7890-abcd-ef1234567890",
+      "status": "active",
+      "created_at": "2024-11-01T14:20:00.000Z",
+      "updated_at": "2024-11-01T14:25:30.000Z"
+    }
+  ],
+  "cursor": "eyJpZCI6ImQxYTJiM2M0In0="
+}`
+      },
+      { type: "heading", level: 2, id: "list-data-products-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "Resolutions", slug: "list-resolutions" },
+      { label: "Jobs", slug: "list-jobs" },
+      { label: "Schemas", slug: "list-schemas" }
+    ],
+    faq: [
+      { question: "What is a data product?", answer: "A data product is the final assembled dataset from the Talonic pipeline. It contains structured, validated, and optionally resolved records ready for export or delivery. Each product is tied to a schema and a source job run." },
+      { question: "How do data product statuses work?", answer: "Data products start as `draft` during assembly, move to `active` once validated and ready for consumption, and can be `archived` when no longer needed. Only `active` products are included in delivery bindings by default." },
+      { question: "Can I filter data products by schema?", answer: "The list endpoint currently supports filtering by `status`. To find products for a specific schema, list all products and filter client-side by `schema_id`, or use the filter/search endpoints for more advanced queries." }
+    ],
+    mentions: ["data product", "export", "structured output"]
+  },
+  {
+    slug: "get-data-product",
+    parentSlug: "data-products",
+    title: "Get Data Product",
+    seoTitle: "Get Data Product Endpoint \u2014 Talonic Docs",
+    description: "Retrieve a single data product by ID with its schema reference, source run, status, and metadata. Requires read scope for the workspace.",
+    content: [
+      { type: "paragraph", text: "Retrieve the full details of a specific data product by its UUID. The response includes the product name, description, associated schema and source run references, current status, and timestamps. Use this endpoint to inspect a product before fetching its result rows." },
+      { type: "paragraph", text: "The `schema_id` field references the user schema that defines the output columns. The `run_id` field references the job run that produced the underlying extracted data. Together these let you trace the full lineage of the data product back to the original documents." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/data-products/{id}",
+        summary: "Get a single data product by ID.",
+        description: "Requires read scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Data product UUID." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "get-data-product-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "id", type: "string", description: "Data product UUID." },
+          { name: "name", type: "string", description: "Human-readable product name." },
+          { name: "description", type: "string | null", description: "Optional description." },
+          { name: "schema_id", type: "string", description: "UUID of the user schema." },
+          { name: "run_id", type: "string", description: "UUID of the source job run." },
+          { name: "status", type: "string", description: "Product status: active, draft, or archived." },
+          { name: "created_at", type: "string", description: "ISO 8601 creation timestamp." },
+          { name: "updated_at", type: "string", description: "ISO 8601 last update timestamp." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s https://api.talonic.ai/v1/data-products/d1a2b3c4-e5f6-7890-abcd-ef1234567890 \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "id": "d1a2b3c4-e5f6-7890-abcd-ef1234567890",
+  "name": "Q4 Invoice Extract",
+  "description": "Structured invoice data from Q4 batch",
+  "schema_id": "s1a2b3c4-e5f6-7890-abcd-ef1234567890",
+  "run_id": "r1a2b3c4-e5f6-7890-abcd-ef1234567890",
+  "status": "active",
+  "created_at": "2024-11-01T14:20:00.000Z",
+  "updated_at": "2024-11-01T14:25:30.000Z"
+}`
+      },
+      { type: "heading", level: 2, id: "get-data-product-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Data product not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Data Products", slug: "list-data-products" },
+      { label: "Get Data Product Results", slug: "get-data-product-results" },
+      { label: "Jobs", slug: "list-jobs" }
+    ],
+    faq: [
+      { question: "How do I trace a data product back to its source documents?", answer: "The `run_id` field references the job run. Use `GET /v1/jobs/{run_id}` to find the job details, including the list of documents that were processed. The `schema_id` field tells you which output schema was used." },
+      { question: "What does the schema_id represent?", answer: "The `schema_id` references the user schema that defines the output columns and field mappings for this data product. It determines which fields appear in the result rows and how they are named." }
+    ],
+    mentions: ["data product", "export", "structured output", "lineage"]
+  },
+  {
+    slug: "delete-data-product",
+    parentSlug: "data-products",
+    title: "Delete Data Product",
+    seoTitle: "Delete Data Product Endpoint \u2014 Talonic Docs",
+    description: "Permanently delete a data product and its result rows. Requires write scope. The source job run and extracted data are not affected.",
+    content: [
+      { type: "paragraph", text: "Permanently delete a data product and all associated result rows. This action is irreversible. The source job run, its documents, and extracted data are not affected by this operation. Use this to remove products that are no longer needed or to clean up test data." },
+      { type: "callout", variant: "warning", text: "Deletion is permanent. All result rows associated with this data product are removed. Any active delivery bindings referencing this product will stop delivering data." },
+      {
+        type: "endpoint",
+        method: "DELETE",
+        path: "/v1/data-products/{id}",
+        summary: "Delete a data product and its results.",
+        description: "Requires write scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Data product UUID." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "delete-data-product-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "deleted", type: "boolean", description: "Always true on success." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s -X DELETE https://api.talonic.ai/v1/data-products/d1a2b3c4-e5f6-7890-abcd-ef1234567890 \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "deleted": true
+}`
+      },
+      { type: "heading", level: 2, id: "delete-data-product-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Data product not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Data Products", slug: "list-data-products" },
+      { label: "Resolutions", slug: "list-resolutions" },
+      { label: "Schemas", slug: "list-schemas" }
+    ],
+    faq: [
+      { question: "Does deleting a data product affect the source job run?", answer: "No. The source job run, its documents, and all extracted data are completely unaffected. Only the data product and its assembled result rows are removed." },
+      { question: "What happens to delivery bindings when a product is deleted?", answer: "Any delivery bindings that reference the deleted product will stop delivering data. The bindings themselves are not deleted, but they will produce errors on the next delivery attempt. Update or remove affected bindings after deleting a product." }
+    ],
+    mentions: ["data product", "export", "structured output"]
+  },
+  {
+    slug: "get-data-product-results",
+    parentSlug: "data-products",
+    title: "Get Data Product Results",
+    seoTitle: "Get Data Product Results \u2014 Talonic Docs",
+    description: "Retrieve the structured result rows of a data product with cursor-based pagination. Each row contains field values aligned to the product schema.",
+    content: [
+      { type: "paragraph", text: "Retrieve the assembled result rows for a data product. Each row contains the structured field values aligned to the product's schema, with one row per document or entity. Results are returned with cursor-based pagination for efficient traversal of large datasets." },
+      { type: "paragraph", text: "The result rows represent the final output of the Talonic pipeline: extracted, validated, and optionally resolved field values. Each row maps field names (from the associated user schema) to their values. Use this endpoint to programmatically consume the structured data for downstream integration, analytics, or export." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/data-products/{id}/results",
+        summary: "Get paginated result rows for a data product.",
+        description: "Requires read scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Data product UUID." }
+            ]
+          },
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "limit", type: "integer", default: "20", description: "Maximum number of rows to return (1-100)." },
+              { name: "cursor", type: "string", description: "Opaque pagination cursor from a previous response." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "get-data-product-results-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "data", type: "array", description: "Array of result row objects." },
+          { name: "data[].id", type: "string", description: "Result row UUID." },
+          { name: "data[].document_id", type: "string", description: "Source document UUID." },
+          { name: "data[].fields", type: "object", description: "Key-value map of field names to extracted values." },
+          { name: "data[].created_at", type: "string", description: "ISO 8601 timestamp." },
+          { name: "cursor", type: "string | null", description: "Pagination cursor for the next page, or null if no more results." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s "https://api.talonic.ai/v1/data-products/d1a2b3c4-e5f6-7890-abcd-ef1234567890/results?limit=10" \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "data": [
+    {
+      "id": "row-1a2b3c4d-e5f6-7890-abcd-ef1234567890",
+      "document_id": "doc-a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+      "fields": {
+        "invoice_number": "INV-2024-0042",
+        "vendor_name": "Acme Corp",
+        "total_amount": "1250.00",
+        "currency": "USD",
+        "invoice_date": "2024-10-15"
+      },
+      "created_at": "2024-11-01T14:25:00.000Z"
+    }
+  ],
+  "cursor": "eyJpZCI6InJvdy0xYTJiIn0="
+}`
+      },
+      { type: "heading", level: 2, id: "get-data-product-results-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Data product not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Data Product", slug: "get-data-product" },
+      { label: "Resolutions", slug: "list-resolutions" },
+      { label: "Jobs", slug: "list-jobs" },
+      { label: "Schemas", slug: "list-schemas" }
+    ],
+    faq: [
+      { question: "What format are the result row fields in?", answer: "The `fields` object is a flat key-value map where keys are field names from the associated schema and values are strings. All values are returned as strings regardless of the field type defined in the schema." },
+      { question: "How do I export all results at once?", answer: "Paginate through all results using the `cursor` parameter until `cursor` is null. Alternatively, use the platform UI to export the data product as CSV or XLSX, which handles pagination automatically." },
+      { question: "Are resolved values included in the results?", answer: "Yes. If a resolution run was executed against the source job, the result rows contain the resolved canonical values rather than the raw extracted values. The data product always reflects the latest resolved state." }
+    ],
+    mentions: ["data product", "export", "structured output", "result rows"]
+  }
+];
+
+// src/content/api/data-policies.ts
+var sections51 = [
+  {
+    slug: "list-data-policies",
+    parentSlug: "data-policies",
+    title: "List Data Policies",
+    seoTitle: "List Data Policies Endpoint \u2014 Talonic Docs",
+    description: "List data policies that define field transformations, normalization rules, and lookup cascades applied during resolution runs. Supports cursor-based pagination.",
+    content: [
+      { type: "paragraph", text: "Data policies are first-class, versioned configuration objects that define how field values are transformed, normalized, and validated during resolution runs. Each policy contains a set of fields (output contract) and rules (transformation logic) that are compiled into an executable pipeline. Policies support 14 rule types including direct mapping, lookup cascades, Lua scripting, and deterministic computation." },
+      { type: "paragraph", text: "Use this endpoint to list all data policies in your workspace. Policies are returned in reverse chronological order by default. Each policy can have multiple versions, allowing you to iterate on transformation logic without affecting in-flight resolution runs that have already captured a policy snapshot." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/data-policies",
+        summary: "List all data policies in the workspace.",
+        description: "Requires read scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "limit", type: "integer", default: "20", description: "Maximum number of items to return (1-100)." },
+              { name: "cursor", type: "string", description: "Opaque pagination cursor from a previous response." },
+              { name: "order", type: "string", default: "desc", description: "Sort order by creation date (asc | desc)." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "list-data-policies-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "data", type: "array", description: "Array of data policy objects." },
+          { name: "data[].id", type: "string", description: "Data policy UUID." },
+          { name: "data[].name", type: "string", description: "Human-readable policy name." },
+          { name: "data[].description", type: "string | null", description: "Optional description of the policy purpose." },
+          { name: "data[].version", type: "integer", description: "Current version number." },
+          { name: "data[].created_at", type: "string", description: "ISO 8601 creation timestamp." },
+          { name: "data[].updated_at", type: "string", description: "ISO 8601 last update timestamp." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s https://api.talonic.ai/v1/data-policies \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "data": [
+    {
+      "id": "p1a2b3c4-e5f6-7890-abcd-ef1234567890",
+      "name": "Invoice Normalization",
+      "description": "Standardize currency codes, country names, and date formats for invoice processing",
+      "version": 3,
+      "created_at": "2024-10-01T09:00:00.000Z",
+      "updated_at": "2024-10-15T11:30:00.000Z"
+    }
+  ],
+  "cursor": "eyJpZCI6InAxYTJiM2M0In0="
+}`
+      },
+      { type: "heading", level: 2, id: "list-data-policies-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "Create Data Policy", slug: "create-data-policy" },
+      { label: "Resolutions", slug: "list-resolutions" },
+      { label: "Schemas", slug: "list-schemas" }
+    ],
+    faq: [
+      { question: "What do data policies do?", answer: "Data policies define how field values are transformed and normalized during resolution runs. They support lookup cascades (mapping raw values to canonical codes via reference tables), Lua scripting for custom logic, deterministic computation, and direct field-to-field mappings." },
+      { question: "How do data policy versions work?", answer: "Each time you update a policy, a new version is created. Resolution runs capture a snapshot of the active version at run time, so changes to a policy do not retroactively affect completed runs. You can inspect which version was used via the `policy_snapshot` field on a resolution run." },
+      { question: "Can I have multiple data policies per workspace?", answer: "Yes. You can create multiple policies for different transformation scenarios. Each resolution run uses the active policy configured for the workspace, but you can switch between policies as needed." }
+    ],
+    mentions: ["data policy", "transformation", "normalization", "lookup", "Lua"]
+  },
+  {
+    slug: "create-data-policy",
+    parentSlug: "data-policies",
+    title: "Create Data Policy",
+    seoTitle: "Create Data Policy Endpoint \u2014 Talonic Docs",
+    description: "Create a new data policy to define field transformation rules, lookup cascades, and normalization logic for resolution runs.",
+    content: [
+      { type: "paragraph", text: "Create a new data policy in your workspace. The policy starts at version 1 with no fields or rules. After creation, use the fields and rules endpoints to define the output contract and transformation logic. Policies are not active until they contain at least one field and one rule." },
+      { type: "paragraph", text: "The policy name should be descriptive enough to distinguish it from other policies in the workspace. Use the optional description field to document the policy purpose, the types of documents it targets, and the normalization strategies it employs." },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/data-policies",
+        summary: "Create a new data policy.",
+        description: "Requires write scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "name", type: "string", required: true, description: "Human-readable policy name." },
+              { name: "description", type: "string", description: "Optional description of the policy purpose." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Request body",
+            code: `{
+  "name": "Invoice Normalization",
+  "description": "Standardize currency codes, country names, and date formats"
+}`
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "create-data-policy-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields (201 Created)",
+        params: [
+          { name: "id", type: "string", description: "Data policy UUID." },
+          { name: "name", type: "string", description: "Policy name." },
+          { name: "description", type: "string | null", description: "Policy description." },
+          { name: "version", type: "integer", description: "Initial version, always 1." },
+          { name: "created_at", type: "string", description: "ISO 8601 creation timestamp." },
+          { name: "updated_at", type: "string", description: "ISO 8601 last update timestamp." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s -X POST https://api.talonic.ai/v1/data-policies \\
+  -H "Authorization: Bearer tlnc_your_api_key" \\
+  -H "Content-Type: application/json" \\
+  -d '{"name":"Invoice Normalization","description":"Standardize currency codes, country names, and date formats"}'`
+      },
+      {
+        type: "code",
+        title: "Response (201 Created)",
+        code: `{
+  "id": "p1a2b3c4-e5f6-7890-abcd-ef1234567890",
+  "name": "Invoice Normalization",
+  "description": "Standardize currency codes, country names, and date formats",
+  "version": 1,
+  "created_at": "2024-10-01T09:00:00.000Z",
+  "updated_at": "2024-10-01T09:00:00.000Z"
+}`
+      },
+      { type: "heading", level: 2, id: "create-data-policy-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "400", type: "bad_request", description: "Invalid request body or missing required fields." },
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Data Policies", slug: "list-data-policies" },
+      { label: "List Data Policy Fields", slug: "list-data-policy-fields" },
+      { label: "List Data Policy Rules", slug: "list-data-policy-rules" }
+    ],
+    faq: [
+      { question: "What should I do after creating a policy?", answer: "After creating a policy, define its output fields via the fields endpoint and add transformation rules via the rules endpoint. The policy is not active until it has at least one field and one rule configured." },
+      { question: "Can I rename a policy after creation?", answer: "Yes. Use the `PATCH /v1/data-policies/{id}` endpoint to update the name or description. Renaming does not affect the policy version or any existing resolution runs that captured a snapshot of this policy." }
+    ],
+    mentions: ["data policy", "transformation", "normalization"]
+  },
+  {
+    slug: "get-data-policy",
+    parentSlug: "data-policies",
+    title: "Get Data Policy",
+    seoTitle: "Get Data Policy Endpoint \u2014 Talonic Docs",
+    description: "Retrieve a data policy by ID with its fields and rules inlined. Returns the full policy configuration needed to understand transformation behavior.",
+    content: [
+      { type: "paragraph", text: "Retrieve the complete details of a specific data policy, including its fields and rules inlined in the response. This provides a single-call view of the entire policy configuration, which is useful for auditing transformation logic or debugging resolution results." },
+      { type: "paragraph", text: "The inlined fields define the output contract: which field keys the policy declares and their expected types. The inlined rules define the transformation logic: lookup tables, direct mappings, Lua scripts, and computed fields. Rules are executed in topological order based on their declared dependencies." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/data-policies/{id}",
+        summary: "Get a data policy with fields and rules inlined.",
+        description: "Requires read scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Data policy UUID." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "get-data-policy-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "id", type: "string", description: "Data policy UUID." },
+          { name: "name", type: "string", description: "Policy name." },
+          { name: "description", type: "string | null", description: "Policy description." },
+          { name: "version", type: "integer", description: "Current version number." },
+          { name: "fields", type: "array", description: "Array of declared output field objects." },
+          { name: "rules", type: "array", description: "Array of transformation rule objects." },
+          { name: "created_at", type: "string", description: "ISO 8601 creation timestamp." },
+          { name: "updated_at", type: "string", description: "ISO 8601 last update timestamp." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s https://api.talonic.ai/v1/data-policies/p1a2b3c4-e5f6-7890-abcd-ef1234567890 \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "id": "p1a2b3c4-e5f6-7890-abcd-ef1234567890",
+  "name": "Invoice Normalization",
+  "description": "Standardize currency codes, country names, and date formats",
+  "version": 3,
+  "fields": [
+    { "field_key": "country_code", "type": "string" },
+    { "field_key": "currency", "type": "string" }
+  ],
+  "rules": [
+    {
+      "id": "r1a2b3c4-0001",
+      "field_key": "country_code",
+      "rule_type": "lookup",
+      "config": { "table": "country_codes", "source_field": "country" }
+    }
+  ],
+  "created_at": "2024-10-01T09:00:00.000Z",
+  "updated_at": "2024-10-15T11:30:00.000Z"
+}`
+      },
+      { type: "heading", level: 2, id: "get-data-policy-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Data policy not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Data Policies", slug: "list-data-policies" },
+      { label: "Resolutions", slug: "list-resolutions" },
+      { label: "Schemas", slug: "list-schemas" }
+    ],
+    faq: [
+      { question: "Why are fields and rules inlined in the response?", answer: "Inlining fields and rules gives you a complete view of the policy in a single API call. This is useful for auditing the full transformation pipeline, debugging resolution results, or exporting the policy configuration for version control." },
+      { question: "What are the supported rule types?", answer: "Data policies support 14 rule types including `lookup` (reference table matching), `direct` (field-to-field mapping), `lua` (custom Lua scripting), `compute` (deterministic formulas), `format` (string formatting), and more. Each rule type has its own configuration schema." },
+      { question: "How does rule execution order work?", answer: "Rules are compiled into a topological order based on their declared field dependencies. A rule that reads from `country` and writes to `country_code` will always execute after the rule that produces `country`. Circular dependencies are detected at compile time." }
+    ],
+    mentions: ["data policy", "transformation", "normalization", "lookup", "Lua"]
+  },
+  {
+    slug: "update-data-policy",
+    parentSlug: "data-policies",
+    title: "Update Data Policy",
+    seoTitle: "Update Data Policy Endpoint \u2014 Talonic Docs",
+    description: "Update the name or description of a data policy. Creates a new version. Does not affect in-flight resolution runs that captured a previous snapshot.",
+    content: [
+      { type: "paragraph", text: "Update the metadata of an existing data policy. You can change the name, description, or both. Each update increments the policy version number. Resolution runs that have already captured a policy snapshot are not affected by this change." },
+      { type: "paragraph", text: "To modify the transformation logic (fields and rules), use the dedicated fields and rules endpoints. This endpoint only updates the policy-level metadata. Version increments from metadata changes are tracked separately from version increments caused by field or rule modifications." },
+      {
+        type: "endpoint",
+        method: "PATCH",
+        path: "/v1/data-policies/{id}",
+        summary: "Update data policy name or description.",
+        description: "Requires write scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Data policy UUID." }
+            ]
+          },
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "name", type: "string", description: "Updated policy name." },
+              { name: "description", type: "string", description: "Updated policy description." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Request body",
+            code: `{
+  "name": "Invoice Normalization v2",
+  "description": "Updated: added VAT normalization rules"
+}`
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "update-data-policy-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "id", type: "string", description: "Data policy UUID." },
+          { name: "name", type: "string", description: "Updated policy name." },
+          { name: "description", type: "string | null", description: "Updated policy description." },
+          { name: "version", type: "integer", description: "Incremented version number." },
+          { name: "created_at", type: "string", description: "ISO 8601 creation timestamp." },
+          { name: "updated_at", type: "string", description: "ISO 8601 last update timestamp." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s -X PATCH https://api.talonic.ai/v1/data-policies/p1a2b3c4-e5f6-7890-abcd-ef1234567890 \\
+  -H "Authorization: Bearer tlnc_your_api_key" \\
+  -H "Content-Type: application/json" \\
+  -d '{"name":"Invoice Normalization v2"}'`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "id": "p1a2b3c4-e5f6-7890-abcd-ef1234567890",
+  "name": "Invoice Normalization v2",
+  "description": "Updated: added VAT normalization rules",
+  "version": 4,
+  "created_at": "2024-10-01T09:00:00.000Z",
+  "updated_at": "2024-10-20T08:15:00.000Z"
+}`
+      },
+      { type: "heading", level: 2, id: "update-data-policy-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "400", type: "bad_request", description: "Invalid request body." },
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Data policy not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Data Policy", slug: "get-data-policy" },
+      { label: "List Data Policy Versions", slug: "list-data-policy-versions" }
+    ],
+    faq: [
+      { question: "Does updating a policy affect running resolutions?", answer: "No. Resolution runs capture a snapshot of the policy at creation time. Updates to the policy only affect future resolution runs. Completed and in-flight runs are unaffected." },
+      { question: "Do I need to provide all fields in the update?", answer: "No. This is a PATCH endpoint, so you only need to include the fields you want to change. Omitted fields retain their current values." }
+    ],
+    mentions: ["data policy", "transformation", "normalization"]
+  },
+  {
+    slug: "delete-data-policy",
+    parentSlug: "data-policies",
+    title: "Delete Data Policy",
+    seoTitle: "Delete Data Policy Endpoint \u2014 Talonic Docs",
+    description: "Permanently delete a data policy and all its versions, fields, and rules. Requires write scope. Does not affect resolution runs that captured a snapshot.",
+    content: [
+      { type: "paragraph", text: "Permanently delete a data policy and all associated versions, fields, and rules. This action is irreversible. Resolution runs that previously captured a snapshot of this policy are not affected, as they retain their own copy of the policy configuration." },
+      { type: "callout", variant: "warning", text: "Deletion is permanent. All versions, fields, and rules of this policy are removed. Future resolution runs will not be able to reference this policy. Existing resolution runs with captured snapshots are unaffected." },
+      {
+        type: "endpoint",
+        method: "DELETE",
+        path: "/v1/data-policies/{id}",
+        summary: "Delete a data policy and all its versions.",
+        description: "Requires write scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Data policy UUID." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "delete-data-policy-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "deleted", type: "boolean", description: "Always true on success." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s -X DELETE https://api.talonic.ai/v1/data-policies/p1a2b3c4-e5f6-7890-abcd-ef1234567890 \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "deleted": true
+}`
+      },
+      { type: "heading", level: 2, id: "delete-data-policy-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Data policy not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Data Policies", slug: "list-data-policies" },
+      { label: "Resolutions", slug: "list-resolutions" }
+    ],
+    faq: [
+      { question: "Does deleting a policy break existing resolution runs?", answer: "No. Resolution runs capture a complete policy snapshot at creation time. Deleting the policy only prevents future resolution runs from using it. All historical results are preserved." },
+      { question: "Can I recover a deleted policy?", answer: "No. Deletion is permanent. If you need to preserve a policy configuration, export it via the GET endpoint before deleting. You can inspect historical snapshots in completed resolution runs." }
+    ],
+    mentions: ["data policy", "transformation", "normalization"]
+  },
+  {
+    slug: "list-data-policy-versions",
+    parentSlug: "data-policies",
+    title: "List Data Policy Versions",
+    seoTitle: "List Data Policy Versions \u2014 Talonic Docs",
+    description: "List all versions of a data policy showing the change history. Each version captures the policy state at a point in time for auditability.",
+    content: [
+      { type: "paragraph", text: "Retrieve the version history of a data policy. Each version represents a snapshot of the policy configuration at a point in time. Versions are created automatically when the policy, its fields, or its rules are modified. This endpoint is useful for auditing changes and understanding how the policy evolved." },
+      { type: "paragraph", text: "Version numbers are monotonically increasing integers starting at 1. When a resolution run captures a policy snapshot, it records the version number, allowing you to correlate resolution results with the specific policy configuration that produced them." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/data-policies/{id}/versions",
+        summary: "List all versions of a data policy.",
+        description: "Requires read scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Data policy UUID." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "list-data-policy-versions-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "data", type: "array", description: "Array of version objects." },
+          { name: "data[].version", type: "integer", description: "Version number." },
+          { name: "data[].created_at", type: "string", description: "ISO 8601 timestamp when this version was created." },
+          { name: "data[].fields_count", type: "integer", description: "Number of declared fields in this version." },
+          { name: "data[].rules_count", type: "integer", description: "Number of rules in this version." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s https://api.talonic.ai/v1/data-policies/p1a2b3c4-e5f6-7890-abcd-ef1234567890/versions \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "data": [
+    { "version": 3, "created_at": "2024-10-15T11:30:00.000Z", "fields_count": 5, "rules_count": 8 },
+    { "version": 2, "created_at": "2024-10-10T14:00:00.000Z", "fields_count": 4, "rules_count": 6 },
+    { "version": 1, "created_at": "2024-10-01T09:00:00.000Z", "fields_count": 2, "rules_count": 3 }
+  ]
+}`
+      },
+      { type: "heading", level: 2, id: "list-data-policy-versions-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Data policy not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Data Policy", slug: "get-data-policy" },
+      { label: "Update Data Policy", slug: "update-data-policy" }
+    ],
+    faq: [
+      { question: "How do I see which version a resolution used?", answer: "The `policy_snapshot` field on a resolution run includes the version number. Compare it with the version list to understand which configuration was active when the resolution executed." },
+      { question: "Can I roll back to a previous version?", answer: "The API does not support direct rollback. To revert to a previous configuration, inspect the version history and manually re-apply the desired fields and rules, which creates a new version with the old configuration." }
+    ],
+    mentions: ["data policy", "transformation", "normalization", "version history"]
+  },
+  {
+    slug: "list-data-policy-fields",
+    parentSlug: "data-policies",
+    title: "List Data Policy Fields",
+    seoTitle: "List Data Policy Fields \u2014 Talonic Docs",
+    description: "List the declared output fields of a data policy. Fields define the output contract \u2014 which field keys the policy produces and their expected types.",
+    content: [
+      { type: "paragraph", text: "Retrieve the list of declared output fields for a data policy. Fields define the output contract: the set of field keys that the policy executor will emit in resolution results. Only fields declared here appear in the final output; any intermediate values computed by rules but not declared as fields are discarded." },
+      { type: "paragraph", text: "Each field has a `field_key` (the output column name) and a `type` (the expected value type). The field list is used by the resolution pipeline to validate output schema compliance and by the results UI to determine which columns to display. Adding or removing fields creates a new policy version." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/data-policies/{id}/fields",
+        summary: "List declared output fields for a data policy.",
+        description: "Requires read scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Data policy UUID." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "list-data-policy-fields-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "data", type: "array", description: "Array of field definition objects." },
+          { name: "data[].field_key", type: "string", description: "Output field key name." },
+          { name: "data[].type", type: "string", description: "Expected value type (e.g. string, number, date)." },
+          { name: "data[].description", type: "string | null", description: "Optional field description." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s https://api.talonic.ai/v1/data-policies/p1a2b3c4-e5f6-7890-abcd-ef1234567890/fields \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "data": [
+    { "field_key": "country_code", "type": "string", "description": "ISO 3166-1 alpha-2 country code" },
+    { "field_key": "currency", "type": "string", "description": "ISO 4217 currency code" },
+    { "field_key": "invoice_date", "type": "date", "description": "Normalized invoice date in ISO 8601 format" }
+  ]
+}`
+      },
+      { type: "heading", level: 2, id: "list-data-policy-fields-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Data policy not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Data Policy", slug: "get-data-policy" },
+      { label: "List Data Policy Rules", slug: "list-data-policy-rules" },
+      { label: "Schemas", slug: "list-schemas" }
+    ],
+    faq: [
+      { question: "What happens to values not declared as fields?", answer: "Values computed by rules but not declared as policy fields are treated as intermediate variables and discarded from the final output. Only declared fields appear in resolution results. You can enable `emit_undeclared_cells` in pipeline config for debugging." },
+      { question: "Can Lua scripts write to undeclared field keys?", answer: "Yes. Lua scripts can write to any cell name as a temporary variable for intermediate computation. However, only values written to declared field keys will appear in the resolution output. Undeclared keys are silently dropped unless debugging is enabled." }
+    ],
+    mentions: ["data policy", "transformation", "normalization", "Lua"]
+  },
+  {
+    slug: "list-data-policy-rules",
+    parentSlug: "data-policies",
+    title: "List Data Policy Rules",
+    seoTitle: "List Data Policy Rules \u2014 Talonic Docs",
+    description: "List the transformation rules of a data policy. Rules define lookup cascades, Lua scripts, direct mappings, and computed fields executed during resolution.",
+    content: [
+      { type: "paragraph", text: "Retrieve the list of transformation rules for a data policy. Rules define the actual transformation logic executed during resolution: lookup cascades against reference tables, Lua scripting for custom logic, direct field-to-field mappings, deterministic computations, and format transformations. Rules are compiled into topological execution order based on field dependencies." },
+      { type: "paragraph", text: "Each rule targets a specific output field and declares its rule type and configuration. The policy compiler validates that all rule dependencies are satisfiable and detects circular references at compile time. During execution, rules are processed in dependency order so that upstream fields are resolved before downstream rules that read from them." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/data-policies/{id}/rules",
+        summary: "List transformation rules for a data policy.",
+        description: "Requires read scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Data policy UUID." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "list-data-policy-rules-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "data", type: "array", description: "Array of rule objects." },
+          { name: "data[].id", type: "string", description: "Rule UUID." },
+          { name: "data[].field_key", type: "string", description: "Target output field key." },
+          { name: "data[].rule_type", type: "string", description: "Rule type (e.g. lookup, direct, lua, compute, format)." },
+          { name: "data[].config", type: "object", description: "Rule-type-specific configuration." },
+          { name: "data[].order", type: "integer", description: "Execution order within the compiled pipeline." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s https://api.talonic.ai/v1/data-policies/p1a2b3c4-e5f6-7890-abcd-ef1234567890/rules \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "data": [
+    {
+      "id": "r1a2b3c4-0001",
+      "field_key": "country_code",
+      "rule_type": "lookup",
+      "config": {
+        "table": "country_codes",
+        "source_field": "country",
+        "fallback": "llm"
+      },
+      "order": 1
+    },
+    {
+      "id": "r1a2b3c4-0002",
+      "field_key": "currency",
+      "rule_type": "lua",
+      "config": {
+        "script": "if cell.country_code == 'US' then return 'USD' end"
+      },
+      "order": 2
+    }
+  ]
+}`
+      },
+      { type: "heading", level: 2, id: "list-data-policy-rules-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Data policy not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Data Policy", slug: "get-data-policy" },
+      { label: "List Data Policy Fields", slug: "list-data-policy-fields" },
+      { label: "Resolutions", slug: "list-resolutions" }
+    ],
+    faq: [
+      { question: "What rule types are available?", answer: "Data policies support 14 rule types: `lookup` (reference table matching with optional LLM fallback), `direct` (field-to-field mapping), `lua` (custom Lua scripting), `compute` (deterministic formulas), `format` (string formatting), `coalesce`, `constant`, `concat`, `split`, `regex`, `date_format`, `number_format`, `conditional`, and `aggregate`." },
+      { question: "How does the Lua scripting work?", answer: "Lua rules execute a sandboxed Lua 5.4 chunk for each record. The script receives a `cell` table with the current record values and can call chain methods like `:matches()` for reference table matching and `:llm_match()` for LLM-powered fuzzy matching. Scripts return the resolved value for the target field." },
+      { question: "What happens when a lookup fails to find a match?", answer: "Lookup rules support a 3-tier cascade: string normalization (exact match after lowercasing and trimming), token-based fuzzy matching (Jaccard similarity), and an optional LLM fallback (Haiku). If all tiers fail, the field retains its original value. Configure the `fallback` option in the rule config to control cascade behavior." }
+    ],
+    mentions: ["data policy", "transformation", "normalization", "lookup", "Lua"]
+  }
+];
+
+// src/content/api/record-sets.ts
+var sections52 = [
+  {
+    slug: "list-record-sets",
+    parentSlug: "record-sets",
+    title: "List Record Sets",
+    seoTitle: "List Record Sets Endpoint \u2014 Talonic Docs",
+    description: "List record sets across the value plane with cursor-based pagination. Filter by layer (capture, structured, resolved, product) to find sets at specific pipeline stages.",
+    content: [
+      { type: "paragraph", text: "Record sets are the core storage abstraction in the Talonic value plane. Each record set is a table-like collection of records at a specific layer of the pipeline. The value plane organizes data into four layers: **capture** (raw OCR output), **structured** (extracted field values), **resolved** (normalized canonical values), and **product** (final assembled output). Record sets at each layer share the same underlying cell storage model but represent progressively refined data." },
+      { type: "paragraph", text: "Use this endpoint to list all record sets in your workspace. Filter by `layer` to find sets at a specific pipeline stage, or by `source_type` to locate sets from a particular origin. Results support cursor-based pagination and can be sorted by creation date. Each record set contains typed cells with confidence scores and provenance metadata." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/record-sets",
+        summary: "List record sets with optional layer and source type filters.",
+        description: "Requires read scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "layer", type: "string", description: "Filter by value plane layer: capture, structured, resolved, or product." },
+              { name: "source_type", type: "string", description: "Filter by source type (e.g. extraction, resolution, job)." },
+              { name: "limit", type: "integer", default: "20", description: "Maximum number of items to return (1-100)." },
+              { name: "cursor", type: "string", description: "Opaque pagination cursor from a previous response." },
+              { name: "order", type: "string", default: "desc", description: "Sort order by creation date (asc | desc)." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "list-record-sets-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "data", type: "array", description: "Array of record set objects." },
+          { name: "data[].id", type: "string", description: "Record set UUID." },
+          { name: "data[].name", type: "string", description: "Human-readable record set name." },
+          { name: "data[].layer", type: "string", description: "Value plane layer: capture, structured, resolved, or product." },
+          { name: "data[].source_type", type: "string", description: "Origin type that created this record set." },
+          { name: "data[].source_id", type: "string", description: "UUID of the source entity (e.g. extraction run, job run)." },
+          { name: "data[].record_count", type: "integer", description: "Total number of records in this set." },
+          { name: "data[].field_count", type: "integer", description: "Number of fields defined on this set." },
+          { name: "data[].created_at", type: "string", description: "ISO 8601 creation timestamp." },
+          { name: "data[].updated_at", type: "string", description: "ISO 8601 last update timestamp." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s "https://api.talonic.ai/v1/record-sets?layer=resolved&limit=10" \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "data": [
+    {
+      "id": "rs-a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+      "name": "Resolution Run 2024-10-15",
+      "layer": "resolved",
+      "source_type": "resolution",
+      "source_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+      "record_count": 142,
+      "field_count": 12,
+      "created_at": "2024-10-15T11:30:00.000Z",
+      "updated_at": "2024-10-15T11:35:42.000Z"
+    }
+  ],
+  "cursor": "eyJpZCI6InJzLWExYjJjM2Q0In0="
+}`
+      },
+      { type: "heading", level: 2, id: "list-record-sets-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "Extractions", slug: "list-extractions" },
+      { label: "Jobs", slug: "list-jobs" },
+      { label: "Resolutions", slug: "list-resolutions" }
+    ],
+    faq: [
+      { question: "What are the value plane layers?", answer: "The value plane has four layers: **capture** (raw OCR/parsed text), **structured** (extracted field values from Claude), **resolved** (normalized canonical values from resolution), and **product** (final assembled output ready for delivery). Each layer represents a progressive refinement of the data." },
+      { question: "What is a record set?", answer: "A record set is a table-like collection of records at a specific value plane layer. It provides typed cell storage where each cell holds a value, confidence score, status, and provenance trace. Record sets are the primary read model for hot table operations in the platform." },
+      { question: "How do record sets relate to jobs and resolutions?", answer: "Job runs produce record sets at the **structured** layer (extracted values). Resolution runs consume structured record sets and produce new record sets at the **resolved** layer (normalized values). The `source_type` and `source_id` fields let you trace each record set back to its origin." }
+    ],
+    mentions: ["record set", "value plane", "cell", "provenance", "confidence"]
+  },
+  {
+    slug: "get-record-set",
+    parentSlug: "record-sets",
+    title: "Get Record Set",
+    seoTitle: "Get Record Set Endpoint \u2014 Talonic Docs",
+    description: "Retrieve a single record set by ID with its layer, source reference, record count, and field count. Requires read scope for the workspace.",
+    content: [
+      { type: "paragraph", text: "Retrieve the full metadata of a specific record set by its UUID. The response includes the value plane layer, source entity reference, record and field counts, and timestamps. Use this endpoint to inspect a record set before fetching its fields or records." },
+      { type: "paragraph", text: "The `layer` field tells you where this record set sits in the pipeline progression. The `source_type` and `source_id` fields let you trace the record set back to the extraction, job, or resolution run that created it. The `record_count` and `field_count` give you a quick summary of the dataset size without fetching the actual records." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/record-sets/{id}",
+        summary: "Get a single record set by ID.",
+        description: "Requires read scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Record set UUID." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "get-record-set-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "id", type: "string", description: "Record set UUID." },
+          { name: "name", type: "string", description: "Human-readable name." },
+          { name: "layer", type: "string", description: "Value plane layer: capture, structured, resolved, or product." },
+          { name: "source_type", type: "string", description: "Origin type that created this record set." },
+          { name: "source_id", type: "string", description: "UUID of the source entity." },
+          { name: "record_count", type: "integer", description: "Total number of records." },
+          { name: "field_count", type: "integer", description: "Number of defined fields." },
+          { name: "created_at", type: "string", description: "ISO 8601 creation timestamp." },
+          { name: "updated_at", type: "string", description: "ISO 8601 last update timestamp." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s https://api.talonic.ai/v1/record-sets/rs-a1b2c3d4-e5f6-7890-abcd-ef1234567890 \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "id": "rs-a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+  "name": "Resolution Run 2024-10-15",
+  "layer": "resolved",
+  "source_type": "resolution",
+  "source_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+  "record_count": 142,
+  "field_count": 12,
+  "created_at": "2024-10-15T11:30:00.000Z",
+  "updated_at": "2024-10-15T11:35:42.000Z"
+}`
+      },
+      { type: "heading", level: 2, id: "get-record-set-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Record set not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Record Sets", slug: "list-record-sets" },
+      { label: "List Record Set Fields", slug: "list-record-set-fields" },
+      { label: "List Record Set Records", slug: "list-record-set-records" }
+    ],
+    faq: [
+      { question: "How do I find which job or resolution produced a record set?", answer: 'The `source_type` field indicates the origin (e.g. "extraction", "job", "resolution") and the `source_id` is the UUID of that entity. Use the corresponding GET endpoint to retrieve the full source details.' },
+      { question: "What does record_count represent?", answer: "The `record_count` is the total number of records (rows) in the set. For structured and resolved layers, each record typically corresponds to one document. For the product layer, records correspond to assembled output rows." }
+    ],
+    mentions: ["record set", "value plane", "cell", "provenance", "confidence"]
+  },
+  {
+    slug: "list-record-set-fields",
+    parentSlug: "record-sets",
+    title: "List Record Set Fields",
+    seoTitle: "List Record Set Fields \u2014 Talonic Docs",
+    description: "List the field definitions of a record set including field keys, types, and display metadata. Fields define the columns available in the record set.",
+    content: [
+      { type: "paragraph", text: "Retrieve the field definitions for a record set. Fields define the columns available in the set \u2014 each field has a key (column name), a type, and optional display metadata. The field list determines which cell values can appear in each record and how they should be interpreted by downstream consumers." },
+      { type: "paragraph", text: "Field definitions are derived from the schema used during extraction or the policy used during resolution. They include the field key, value type, and optional attributes like display name and description. Use this endpoint to understand the shape of the data before fetching records, or to build dynamic table UIs that adapt to the field list." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/record-sets/{id}/fields",
+        summary: "List field definitions for a record set.",
+        description: "Requires read scope.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Record set UUID." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "list-record-set-fields-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "data", type: "array", description: "Array of field definition objects." },
+          { name: "data[].field_key", type: "string", description: "Field key (column name)." },
+          { name: "data[].type", type: "string", description: "Value type (e.g. string, number, date, boolean)." },
+          { name: "data[].display_name", type: "string | null", description: "Human-readable display name." },
+          { name: "data[].description", type: "string | null", description: "Optional field description." },
+          { name: "data[].ordinal", type: "integer", description: "Display order position." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s https://api.talonic.ai/v1/record-sets/rs-a1b2c3d4-e5f6-7890-abcd-ef1234567890/fields \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "data": [
+    { "field_key": "invoice_number", "type": "string", "display_name": "Invoice Number", "description": null, "ordinal": 0 },
+    { "field_key": "vendor_name", "type": "string", "display_name": "Vendor Name", "description": null, "ordinal": 1 },
+    { "field_key": "total_amount", "type": "number", "display_name": "Total Amount", "description": "Invoice total in local currency", "ordinal": 2 },
+    { "field_key": "invoice_date", "type": "date", "display_name": "Invoice Date", "description": null, "ordinal": 3 }
+  ]
+}`
+      },
+      { type: "heading", level: 2, id: "list-record-set-fields-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Record set not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Record Set", slug: "get-record-set" },
+      { label: "List Record Set Records", slug: "list-record-set-records" },
+      { label: "Extractions", slug: "list-extractions" }
+    ],
+    faq: [
+      { question: "Where do the field definitions come from?", answer: "Field definitions are derived from the user schema (for structured layer sets) or the data policy output contract (for resolved layer sets). They represent the declared columns that the extraction or resolution pipeline was configured to produce." },
+      { question: "Can different record sets have different fields?", answer: "Yes. Each record set has its own independent field definitions. A structured record set may have different fields than a resolved record set, even if they originate from the same documents, because the resolution policy may add, rename, or transform fields." }
+    ],
+    mentions: ["record set", "value plane", "cell", "field definition"]
+  },
+  {
+    slug: "list-record-set-records",
+    parentSlug: "record-sets",
+    title: "List Record Set Records",
+    seoTitle: "List Record Set Records \u2014 Talonic Docs",
+    description: "List records in a record set with offset-based pagination. Each record contains typed cells with values, confidence scores, and provenance metadata.",
+    content: [
+      { type: "paragraph", text: "Retrieve the records (rows) in a record set with offset-based pagination. Each record contains a set of typed cells keyed by field name. Every cell carries a value, a confidence score (0-1), a status indicator, and provenance metadata tracing the value back to its source. This endpoint is the primary way to read structured data from the value plane." },
+      { type: "paragraph", text: "Unlike the cursor-based pagination used by most list endpoints, record set records use offset-based pagination with `page` and `limit` parameters. This is intentional: record sets are table-like structures where random access by page number is a common use case for building paginated table UIs. The total record count is available on the parent record set object." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/record-sets/{id}/records",
+        summary: "List records with typed cells, confidence, and provenance.",
+        description: "Requires read scope. Uses offset-based pagination.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Record set UUID." }
+            ]
+          },
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "page", type: "integer", default: "1", description: "Page number (1-indexed)." },
+              { name: "limit", type: "integer", default: "20", description: "Number of records per page (1-100)." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "list-record-set-records-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "data", type: "array", description: "Array of record objects." },
+          { name: "data[].id", type: "string", description: "Record UUID." },
+          { name: "data[].document_id", type: "string | null", description: "Associated document UUID, if applicable." },
+          { name: "data[].cells", type: "object", description: "Map of field_key to cell objects." },
+          { name: "data[].cells[key].value", type: "string | null", description: "The cell value." },
+          { name: "data[].cells[key].confidence", type: "number", description: "Confidence score (0-1)." },
+          { name: "data[].cells[key].status", type: "string", description: "Cell status (e.g. extracted, resolved, manual)." },
+          { name: "data[].cells[key].source", type: "string | null", description: "Provenance trace indicating how the value was produced." },
+          { name: "page", type: "integer", description: "Current page number." },
+          { name: "total", type: "integer", description: "Total number of records." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s "https://api.talonic.ai/v1/record-sets/rs-a1b2c3d4-e5f6-7890-abcd-ef1234567890/records?page=1&limit=10" \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "data": [
+    {
+      "id": "rec-f1e2d3c4-b5a6-7890-fedc-ba0987654321",
+      "document_id": "doc-a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+      "cells": {
+        "invoice_number": {
+          "value": "INV-2024-0042",
+          "confidence": 0.97,
+          "status": "extracted",
+          "source": "chunk:3/line:12"
+        },
+        "country_code": {
+          "value": "DE",
+          "confidence": 0.95,
+          "status": "resolved",
+          "source": "lookup:country_codes"
+        }
+      }
+    }
+  ],
+  "page": 1,
+  "total": 142
+}`
+      },
+      { type: "heading", level: 2, id: "list-record-set-records-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Record set not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Record Set", slug: "get-record-set" },
+      { label: "List Record Set Fields", slug: "list-record-set-fields" },
+      { label: "Export Record Set", slug: "export-record-set" }
+    ],
+    faq: [
+      { question: "What does the confidence score mean?", answer: "The confidence score (0-1) reflects how certain the system is about the cell value. Values extracted directly from documents with high textual clarity score 0.9+. Values resolved via fuzzy matching or LLM fallback score lower (0.5-0.9). Manually entered values always have confidence 1.0." },
+      { question: "What does the source field contain?", answer: "The `source` field is a provenance trace that indicates how the value was produced. For extracted values, it references the document chunk and line. For resolved values, it references the lookup table or resolution strategy. For computed values, it names the computation formula." },
+      { question: "Why does this endpoint use page/limit instead of cursor?", answer: "Record sets are table-like structures where random access by page number is common in table UIs. Offset pagination supports jumping to arbitrary pages, which cursor pagination does not. For sequential traversal of very large sets, use the export endpoint instead." }
+    ],
+    mentions: ["record set", "value plane", "cell", "provenance", "confidence"]
+  },
+  {
+    slug: "export-record-set",
+    parentSlug: "record-sets",
+    title: "Export Record Set",
+    seoTitle: "Export Record Set Endpoint \u2014 Talonic Docs",
+    description: "Export a complete record set as a downloadable file. Returns all records with their cell values in a single response for bulk consumption.",
+    content: [
+      { type: "paragraph", text: "Export the complete contents of a record set as a downloadable payload. Unlike the paginated records endpoint, this returns all records in a single response, making it suitable for bulk data consumption, ETL pipelines, and offline analysis. The export includes all cell values for every record in the set." },
+      { type: "paragraph", text: "The export endpoint streams the full record set content without pagination. For large record sets, this may result in significant response payloads. Consider using the paginated records endpoint for interactive use cases, and reserve this endpoint for batch export workflows where you need the complete dataset in one call." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/record-sets/{id}/export",
+        summary: "Export a complete record set.",
+        description: "Requires read scope. Returns all records without pagination.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "id", type: "uuid", required: true, description: "Record set UUID." }
+            ]
+          }
+        ]
+      },
+      { type: "heading", level: 2, id: "export-record-set-response", text: "Response" },
+      {
+        type: "param-table",
+        title: "Response fields",
+        params: [
+          { name: "data", type: "array", description: "Complete array of record objects with cells." },
+          { name: "fields", type: "array", description: "Array of field definitions for column ordering." },
+          { name: "record_count", type: "integer", description: "Total number of exported records." },
+          { name: "exported_at", type: "string", description: "ISO 8601 timestamp of the export." }
+        ]
+      },
+      {
+        type: "code",
+        title: "curl",
+        language: "bash",
+        code: `curl -s https://api.talonic.ai/v1/record-sets/rs-a1b2c3d4-e5f6-7890-abcd-ef1234567890/export \\
+  -H "Authorization: Bearer tlnc_your_api_key"`
+      },
+      {
+        type: "code",
+        title: "Response",
+        code: `{
+  "data": [
+    {
+      "id": "rec-f1e2d3c4-b5a6-7890-fedc-ba0987654321",
+      "document_id": "doc-a1b2c3d4-e5f6-7890-abcd-ef1234567890",
+      "cells": {
+        "invoice_number": { "value": "INV-2024-0042", "confidence": 0.97 },
+        "country_code": { "value": "DE", "confidence": 0.95 }
+      }
+    }
+  ],
+  "fields": [
+    { "field_key": "invoice_number", "type": "string", "ordinal": 0 },
+    { "field_key": "country_code", "type": "string", "ordinal": 1 }
+  ],
+  "record_count": 142,
+  "exported_at": "2024-10-16T09:00:00.000Z"
+}`
+      },
+      { type: "heading", level: 2, id: "export-record-set-errors", text: "Errors" },
+      {
+        type: "param-table",
+        title: "Error responses",
+        params: [
+          { name: "401", type: "unauthorized", description: "Missing or invalid API key." },
+          { name: "404", type: "not_found", description: "Record set not found or does not belong to your organization." },
+          { name: "429", type: "rate_limited", description: "Too many requests. Retry after the period indicated in the Retry-After header." }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Record Set Records", slug: "list-record-set-records" },
+      { label: "Extractions", slug: "list-extractions" },
+      { label: "Jobs", slug: "list-jobs" },
+      { label: "Resolutions", slug: "list-resolutions" }
+    ],
+    faq: [
+      { question: "When should I use export vs the paginated records endpoint?", answer: "Use the export endpoint for batch workflows, ETL pipelines, and offline analysis where you need the complete dataset in one call. Use the paginated records endpoint for interactive UIs, incremental processing, or when working with very large record sets where memory is a concern." },
+      { question: "Does the export include confidence and provenance?", answer: "The export includes cell values and confidence scores. Full provenance traces are available through the paginated records endpoint. The export is optimized for bulk data consumption rather than detailed audit trails." },
+      { question: "Is there a size limit on exports?", answer: "There is no hard limit, but very large record sets (10,000+ records) may result in large response payloads and slower response times. For extremely large datasets, consider using the delivery pipeline to push data to an S3 bucket or SFTP server instead." }
+    ],
+    mentions: ["record set", "value plane", "cell", "export", "bulk"]
+  }
+];
+
 // src/content/sdk/sections.json
 var sections_default = [
   {
@@ -26174,7 +27691,7 @@ talonic --help` }
 ];
 
 // src/content/sdk/index.ts
-var sections50 = sections_default;
+var sections53 = sections_default;
 
 // src/content/mcp/sections.json
 var sections_default2 = [
@@ -27848,7 +29365,7 @@ var sections_default2 = [
 ];
 
 // src/content/mcp/index.ts
-var sections51 = sections_default2;
+var sections54 = sections_default2;
 
 // src/content/index.ts
 var ALL_PLATFORM_RAW = [
@@ -27902,10 +29419,13 @@ var ALL_API_RAW = [
   ...sections47,
   ...sections48,
   ...sections49,
+  ...sections50,
+  ...sections51,
+  ...sections52,
   ...sections45
 ];
-var ALL_SDK_RAW = [...sections50];
-var ALL_MCP_RAW = [...sections51];
+var ALL_SDK_RAW = [...sections53];
+var ALL_MCP_RAW = [...sections54];
 function enrich(raw, navSections, domain) {
   return raw.map((r) => {
     const { prev, next } = derivePrevNext(navSections, r.slug);