IncQL RFCs
Search and inspect IncQL's durable design records.
| RFC | Status | Tags | Title |
|---|---|---|---|
| 000 | Planned | Authoring, Interoperability, Planning | Language Specification |
| 001 | In Progress | Authoring, Planning, Types | Dataset types and carriers (DataSet[T]) |
| 002 | In Progress | Extensibility, Interoperability, Planning | Apache Substrait integration |
| 003 | Implemented | Authoring, Interoperability, Planning | query {} blocks — syntax, typing, Substrait |
| 004 | In Progress | Data access, Execution, Interoperability | Execution context and DataFusion |
| 005 | Blocked | Authoring, Planning | Pipe-forward relational syntax (|>) |
| 006 | Blocked | Interoperability, Planning | Promote unnest/explode to core Substrait lowering |
| 007 | In Progress | Evidence, Planning | Prism logical planning and optimization engine |
| 008 | Planned | Evidence, Execution, Planning | Optimizer boundary, statistics, cost-based optimization, and adaptive execution |
| 009 | Draft | Data access, Extensibility | Session Format Handler Registry |
| 010 | Draft | Data access, Interoperability | CSV dialect and interpretation contract |
| 011 | Draft | Data access, Interoperability | Source discovery and parse-unit expansion |
| 012 | Implemented | Authoring, Planning, Types | Unified scalar expression surface |
| 013 | Implemented | Authoring, Extensibility, Functions | Function catalog program |
| 014 | Implemented | Extensibility, Functions, Interoperability | Function registry and catalog governance |
| 015 | Implemented | Authoring, Functions, Interoperability | Core scalar functions and operators |
| 016 | Implemented | Authoring, Functions, Interoperability | Core aggregate functions |
| 017 | Implemented | Authoring, Functions, Interoperability | Aggregate modifiers |
| 018 | Implemented | Authoring, Functions, Interoperability | Common scalar function catalog |
| 019 | Implemented | Authoring, Functions, Planning | Window functions |
| 020 | Implemented | Authoring, Functions, Planning | Nested data functions |
| 021 | Implemented | Authoring, Functions, Planning | Generator and table-valued functions |
| 022 | Implemented | Authoring, Functions, Interoperability | Semi-structured and format functions |
| 023 | Implemented | Authoring, Functions, Interoperability | Approximate and sketch functions |
| 024 | Implemented | Extensibility, Functions, Interoperability | Function extension policy |
| 025 | Implemented | Interoperability, Types | Typed sketch logical values |
| 026 | Implemented | Interoperability, Types | Semi-structured variant logical values |
| 027 | In Progress | Evidence, Governance, Interoperability, Verification | Relational evidence program |
| 028 | In Progress | Evidence | Semantic identity and target model |
| 029 | In Progress | Evidence, Extensibility | Typed metadata attachments |
| 030 | In Progress | Evidence, Planning | Prism lineage graph |
| 031 | In Progress | Evidence, Interoperability | Local inspection APIs and artifacts |
| 032 | Implemented | Evidence, Execution | Execution observations |
| 033 | Implemented | Evidence, Execution, Interoperability | Adapter requirements and coverage |
| 034 | Implemented | Authoring, Evidence, Execution | Quality assertions and observations |
| 035 | Implemented | Evidence, Governance, Planning | Governed attributes and policy checkpoints |
| 036 | Draft | Evidence, Governance, Interoperability | Governed plan bundle |
| 037 | Draft | Evidence, Planning | Plan diff and blast-radius inputs |
| 038 | Draft | Evidence, Extensibility, Interoperability | Evidence exchange bridges |
| 039 | Draft | Authoring | Pandas-familiar exploration API |
| 040 | Draft | Evidence, Interoperability | Interoperability semantic profiles |
| 041 | Draft | Authoring, Interoperability, Planning | Prism plan ingress and external client frontends |
| 042 | Draft | Evidence, Verification | Async verification evidence |
| 043 | Draft | Evidence, Interoperability, Verification | Canonical equality and digest profiles |
| 044 | Draft | Evidence, Verification | Verifier statements and proof artifacts |
| 045 | Draft | Evidence, Planning, Verification | Constraint evidence and verification-aware planning |
| 046 | Draft | Evidence, Governance, Interoperability | Data contract ingress and product topology |
| 047 | Draft | Evidence, Interoperability | Semantic evidence graph and agent query surface |
| 048 | Draft | Evidence, Execution, Interoperability | Cluster execution backend mode |
| 050 | Draft | Data access, Execution, Extensibility, Interoperability | Addon component registry and package contract |
IncQL RFCs cover language, planning, execution, and governance decisions owned by IncQL. They form a separate series from the Incan language RFCs, which govern the host language itself.
How the RFC lifecycle works
Active RFCs remain in docs/rfcs/ while the design is Draft, Planned, In Progress, Blocked, or Deferred. Closed records move without changing their RFC number or filename:
docs/rfcs/closed/implemented/contains implemented RFCs.docs/rfcs/closed/superseded/contains RFCs replaced by a newer design record.docs/rfcs/closed/rejected/contains rejected or withdrawn RFCs.
The generated catalog treats each RFC's heading, metadata, summary, and lifecycle path as source data. The docs build fails when the index, controlled tag assignments, or lifecycle placement drifts from those records.
v0.1 tracking: RFCs 000–004 plus RFC 007 remain the foundation that defines when IncQL v0.1 is complete: authors can read data, write typed queries, lower through Prism to Substrait, execute through DataFusion, and write results. The catalog also includes v0.1-shipped slices that landed before the whole foundation is closed, including the function catalog and evidence/observation work.
Create or update an RFC
Copy TEMPLATE.md, name the file NNN_short_slug.md, choose the next available number, and open a pull request. Follow Writing IncQL RFCs for the metadata contract, lifecycle transitions, and review conventions.