Lucid Rate-Limit and Backpressure Design

Overview

Ground request control in the exact Lucid endpoint contract and observed responses. There is no justified pack-wide fixed requests-per-minute value.

Prerequisites

• Inventory of operations, mutation semantics, concurrency, callers, and service objectives
• Current endpoint documentation and sanitized response headers/bodies
• Stable idempotency or reconciliation strategy for mutations

Tool Discipline

Use Read, Glob, and Grep to inspect clients and tests, WebFetch for current endpoint/limit documentation, and Write or Edit only for local policy, code, tests, and receipts.

Current Contract

Treat limits as endpoint/API-specific and time-sensitive. A legacy or Data API limit must not be generalized to document, export, import, Extension API, or connector operations. Server responses and current endpoint pages control.