Design records

IncQL keeps normative design decisions and longer-form explorations separate from current API documentation.

RFCs

Requests for Comments define IncQL's stable design intent and record why important boundaries exist. They cover the language and carrier foundations, Prism and Substrait, Session execution, the function catalog, evidence and governance, external ingress, and backend modes.

RFCs are moment-in-time design records. Use the Reference pages for current package behavior and the RFC series when you need the normative contract, rationale, alternatives, or design history.

Whitepapers

Whitepapers explore product and architectural directions that benefit from a cohesive narrative but are not themselves the public API contract. The current collection includes IncQL-DB, the local embedded analytical store direction.

Contributing a design

Read Writing RFCs before proposing a normative change. New RFCs start from the RFC template and should make the north-star end state explicit before describing implementation stages.