InQL uses its own RFC series (starting at 000), independent of the Incan language RFCs.
New RFC: copy TEMPLATE.md, name the file NNN_short_slug.md, pick the next number from the table (or from open issues), and open a PR. Section order and header fields follow that template. For workflow and conventions, see Writing InQL RFCs.
| RFC | Status | Title | |
|---|---|---|---|
| 000 | Planned | Language specification — core model, naming, schema shapes, layer boundaries | |
| 001 | In Progress | Dataset types and carriers (DataSet[T], BoundedDataSet[T], UnboundedDataSet[T]) |
|
| 002 | In Progress | Apache Substrait — Rel-level contract, mapping catalog, binding boundaries |
|
| 003 | Planned | query {} blocks — grammar, typing, Substrait lowering |
|
| 004 | In Progress | Execution context — session, DataFusion, read/transform/write | |
| 005 | Blocked | Pipe-forward relational syntax (|>) — optional surface |
|
| 006 | Blocked | Promote unnest/explode to core Substrait lowering — blocked on upstream Substrait standardization | |
| 007 | In Progress | Prism logical planning and optimization engine | |
| 008 | Planned | Optimizer boundary, statistics, cost-based optimization, and adaptive execution | |
| 009 | Draft | Session format handler registry (plugin-style source format registration) | |
| 010 | Draft | CSV dialect and interpretation contract | |
| 011 | Draft | Source discovery and parse-unit expansion | |
| 012 | Draft | Unified scalar expression surface | |
| 013 | Draft | Function catalog program | |
| 014 | Draft | Function registry and catalog governance | |
| 015 | Draft | Core scalar functions and operators | |
| 016 | Draft | Core aggregate functions | |
| 017 | Draft | Aggregate modifiers | |
| 018 | Draft | Common scalar function catalog | |
| 019 | Draft | Window functions | |
| 020 | Draft | Nested data functions | |
| 021 | Draft | Generator and table-valued functions | |
| 022 | Draft | Semi-structured and format functions | |
| 023 | Draft | Approximate and sketch functions | |
| 024 | Draft | Function extension policy |
v0.1 scope: RFCs 000–004 plus RFC 007. When those foundational RFCs are resolved (Draft → Planned → Implemented), InQL v0.1 is complete: authors can read data, write typed queries, lower through Prism to Substrait, execute through DataFusion, and write results.
New RFCs should follow TEMPLATE.md (aligned with Incan’s RFC structure, adapted for InQL).