Implementation status
What runs today in each environment and for each Connector: implemented, experimental or planned.
This is the one page that describes what is implemented today. Every other page describes ActQL 0.1 as designed: the guarantees in the specification and the product surface the rest of the documentation shows. Use this page to check whether a feature runs in your environment before you depend on it. The ceilings every Program runs under are on Runtime limits.
Status by environment
| Mark | Status | Meaning |
|---|---|---|
| ✔Implemented | Implemented | Runs in that environment; covered by the repository's checks. |
| ◐Experimental | Experimental | Runs, but the surface or its limits may still change before 0.1. |
| ○Planned | Planned | Defined in the specification and shown in the documentation; not yet executable in that environment. |
| —Not applicable | Not applicable | The feature has no meaning in that environment or for that Connector. |
| Feature | CLI | Node | Python | Remote Host | ActQL Cloud |
|---|---|---|---|---|---|
| SQL and Pipe queries over local values | ✔Implemented | ✔Implemented | ○Planned | ✔Implemented | ○Planned |
check, explain, run, approve, status (convenience commands) | ○Planned | —Not applicable | —Not applicable | —Not applicable | —Not applicable |
explain --verbose, explain --run, actql-explanation/0.1 JSON | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
connect / startSource / wait / result / attach | —Not applicable | ✔Implemented | ○Planned | ✔Implemented | ○Planned |
Mock profile (--profile mock) | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
| Pushdown to a Connector | ◐Experimental | ◐Experimental | ○Planned | ◐Experimental | ○Planned |
| Cross-source joins in DuckDB | ◐Experimental | ◐Experimental | ○Planned | ◐Experimental | ○Planned |
INFER with a model task | ◐Experimental | ◐Experimental | ○Planned | ◐Experimental | ○Planned |
EFFECT … UPDATE TARGET … MAPPING … (long form) | ◐Experimental | ◐Experimental | ○Planned | ◐Experimental | ○Planned |
EFFECT … COMMAND postlude (long form) | ◐Experimental | ◐Experimental | ○Planned | ◐Experimental | ○Planned |
CREATE [OR REPLACE] TABLE | ◐Experimental | ◐Experimental | ○Planned | ◐Experimental | ○Planned |
EFFECT UPDATE / UPSERT / DELETE … ID … (short forms) | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
EFFECT INSERT, EFFECT STORE, EFFECT COMMAND … ID … (short forms) | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
LIST_FILES, contents sources (content_ref), SERIALIZE, STORE of content | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
SQL INSERT / UPDATE / DELETE statement Effects | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
| Checkpoints and approval | ◐Experimental | ◐Experimental | ○Planned | ◐Experimental | ○Planned |
--stop-before commit / stopBefore | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
| Reconciliation of unknown outcomes | ◐Experimental | ◐Experimental | ○Planned | ◐Experimental | ○Planned |
| Named Results and delivery | ✔Implemented | ✔Implemented | ○Planned | ✔Implemented | ○Planned |
NEAREST shorthand and vector functions | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
Graph construction, MATCH and graph operations | ◐Experimental | ◐Experimental | ○Planned | ◐Experimental | ○Planned |
| Event operations | ◐Experimental | ◐Experimental | ○Planned | ◐Experimental | ○Planned |
| Local Host (embedded) | ✔Implemented | ✔Implemented | ○Planned | —Not applicable | —Not applicable |
| Remote Host over HTTPS | —Not applicable | ✔Implemented | ✔Implemented | ✔Implemented | ○Planned |
"Node" is the @actql/node package; "Python" is the actql package. The
CLI column covers the native actql command.
Connectors
Every Connector page describes the full v0.1 surface: reads, record Effects, tables and content, operations, Preview and reconciliation. The columns say what runs today.
| Connector | Read | Record Effects | Tables and content | Operations | Preview and reconciliation |
|---|---|---|---|---|---|
| DuckDB | ✔Implemented | ◐Experimentalinsert, update | ○Planned | —Not applicable | ○Planned |
| Local files | ✔Implemented | ○Planned | ◐Experimentalstore rows, long form | ○Planned | ○Planned |
| Google Cloud Storage | ◐Experimental | ○Planned | ◐Experimentalupload, long form | ○Planned | ○Planned |
| Salesforce | ◐Experimental | ◐Experimentalsingle-record update | ○Planned | ○Planned | ○Planned |
| Google Sheets | ◐Experimental | ◐Experimentalappend | ○Planned | ○Planned | ○Planned |
| GitHub | ◐Experimental | ◐Experimentalcreate | ○Planned | ○Planned | ○Planned |
| Snowflake | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
| BigQuery | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
| HubSpot | ○Planned | ○Planned | —Not applicable | ○Planned | ○Planned |
| Slack | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
| Notion | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
| kintone | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
| Tableau | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
| Google Drive | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
| Gmail | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
| Google Calendar | ○Planned | ○Planned | —Not applicable | ○Planned | ○Planned |
| Amazon S3 | ○Planned | ○Planned | ○Planned | ○Planned | ○Planned |
"Preview and reconciliation" means the apply-time condition check
(full_diff with a conflict outcome) and the evidence-based lookup of a lost
reply that each Connector page describes.
Source: actql/actql/docs/reference/status.md at d904416674e4 · Edit on GitHub