Metadata-Version: 2.4
Name: xorq
Version: 0.3.23
Summary: Data processing library built on top of Ibis and DataFusion to write multi-engine data workflows.
Project-URL: Homepage, https://www.xorq.dev/
Project-URL: Repository, https://github.com/xorq-labs/xorq/
Project-URL: Issues, https://github.com/xorq-labs/xorq/issues
Project-URL: Changelog, https://github.com/xorq-labs/xorq/blob/main/CHANGELOG.md
Project-URL: Documentation, https://docs.xorq.dev/
Author-email: Hussain Sultan <hussain@letsql.com>
Maintainer-email: Dan Lovell <dan@letsql.com>, Daniel Mesejo <mesejo@letsql.com>
License:                                  Apache License
                                   Version 2.0, January 2004
                                http://www.apache.org/licenses/
        
           TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
        
           1. Definitions.
        
              "License" shall mean the terms and conditions for use, reproduction,
              and distribution as defined by Sections 1 through 9 of this document.
        
              "Licensor" shall mean the copyright owner or entity authorized by
              the copyright owner that is granting the License.
        
              "Legal Entity" shall mean the union of the acting entity and all
              other entities that control, are controlled by, or are under common
              control with that entity. For the purposes of this definition,
              "control" means (i) the power, direct or indirect, to cause the
              direction or management of such entity, whether by contract or
              otherwise, or (ii) ownership of fifty percent (50%) or more of the
              outstanding shares, or (iii) beneficial ownership of such entity.
        
              "You" (or "Your") shall mean an individual or Legal Entity
              exercising permissions granted by this License.
        
              "Source" form shall mean the preferred form for making modifications,
              including but not limited to software source code, documentation
              source, and configuration files.
        
              "Object" form shall mean any form resulting from mechanical
              transformation or translation of a Source form, including but
              not limited to compiled object code, generated documentation,
              and conversions to other media types.
        
              "Work" shall mean the work of authorship, whether in Source or
              Object form, made available under the License, as indicated by a
              copyright notice that is included in or attached to the work
              (an example is provided in the Appendix below).
        
              "Derivative Works" shall mean any work, whether in Source or Object
              form, that is based on (or derived from) the Work and for which the
              editorial revisions, annotations, elaborations, or other modifications
              represent, as a whole, an original work of authorship. For the purposes
              of this License, Derivative Works shall not include works that remain
              separable from, or merely link (or bind by name) to the interfaces of,
              the Work and Derivative Works thereof.
        
              "Contribution" shall mean any work of authorship, including
              the original version of the Work and any modifications or additions
              to that Work or Derivative Works thereof, that is intentionally
              submitted to Licensor for inclusion in the Work by the copyright owner
              or by an individual or Legal Entity authorized to submit on behalf of
              the copyright owner. For the purposes of this definition, "submitted"
              means any form of electronic, verbal, or written communication sent
              to the Licensor or its representatives, including but not limited to
              communication on electronic mailing lists, source code control systems,
              and issue tracking systems that are managed by, or on behalf of, the
              Licensor for the purpose of discussing and improving the Work, but
              excluding communication that is conspicuously marked or otherwise
              designated in writing by the copyright owner as "Not a Contribution."
        
              "Contributor" shall mean Licensor and any individual or Legal Entity
              on behalf of whom a Contribution has been received by Licensor and
              subsequently incorporated within the Work.
        
           2. Grant of Copyright License. Subject to the terms and conditions of
              this License, each Contributor hereby grants to You a perpetual,
              worldwide, non-exclusive, no-charge, royalty-free, irrevocable
              copyright license to reproduce, prepare Derivative Works of,
              publicly display, publicly perform, sublicense, and distribute the
              Work and such Derivative Works in Source or Object form.
        
           3. Grant of Patent License. Subject to the terms and conditions of
              this License, each Contributor hereby grants to You a perpetual,
              worldwide, non-exclusive, no-charge, royalty-free, irrevocable
              (except as stated in this section) patent license to make, have made,
              use, offer to sell, sell, import, and otherwise transfer the Work,
              where such license applies only to those patent claims licensable
              by such Contributor that are necessarily infringed by their
              Contribution(s) alone or by combination of their Contribution(s)
              with the Work to which such Contribution(s) was submitted. If You
              institute patent litigation against any entity (including a
              cross-claim or counterclaim in a lawsuit) alleging that the Work
              or a Contribution incorporated within the Work constitutes direct
              or contributory patent infringement, then any patent licenses
              granted to You under this License for that Work shall terminate
              as of the date such litigation is filed.
        
           4. Redistribution. You may reproduce and distribute copies of the
              Work or Derivative Works thereof in any medium, with or without
              modifications, and in Source or Object form, provided that You
              meet the following conditions:
        
              (a) You must give any other recipients of the Work or
                  Derivative Works a copy of this License; and
        
              (b) You must cause any modified files to carry prominent notices
                  stating that You changed the files; and
        
              (c) You must retain, in the Source form of any Derivative Works
                  that You distribute, all copyright, patent, trademark, and
                  attribution notices from the Source form of the Work,
                  excluding those notices that do not pertain to any part of
                  the Derivative Works; and
        
              (d) If the Work includes a "NOTICE" text file as part of its
                  distribution, then any Derivative Works that You distribute must
                  include a readable copy of the attribution notices contained
                  within such NOTICE file, excluding those notices that do not
                  pertain to any part of the Derivative Works, in at least one
                  of the following places: within a NOTICE text file distributed
                  as part of the Derivative Works; within the Source form or
                  documentation, if provided along with the Derivative Works; or,
                  within a display generated by the Derivative Works, if and
                  wherever such third-party notices normally appear. The contents
                  of the NOTICE file are for informational purposes only and
                  do not modify the License. You may add Your own attribution
                  notices within Derivative Works that You distribute, alongside
                  or as an addendum to the NOTICE text from the Work, provided
                  that such additional attribution notices cannot be construed
                  as modifying the License.
        
              You may add Your own copyright statement to Your modifications and
              may provide additional or different license terms and conditions
              for use, reproduction, or distribution of Your modifications, or
              for any such Derivative Works as a whole, provided Your use,
              reproduction, and distribution of the Work otherwise complies with
              the conditions stated in this License.
        
           5. Submission of Contributions. Unless You explicitly state otherwise,
              any Contribution intentionally submitted for inclusion in the Work
              by You to the Licensor shall be under the terms and conditions of
              this License, without any additional terms or conditions.
              Notwithstanding the above, nothing herein shall supersede or modify
              the terms of any separate license agreement you may have executed
              with Licensor regarding such Contributions.
        
           6. Trademarks. This License does not grant permission to use the trade
              names, trademarks, service marks, or product names of the Licensor,
              except as required for reasonable and customary use in describing the
              origin of the Work and reproducing the content of the NOTICE file.
        
           7. Disclaimer of Warranty. Unless required by applicable law or
              agreed to in writing, Licensor provides the Work (and each
              Contributor provides its Contributions) on an "AS IS" BASIS,
              WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
              implied, including, without limitation, any warranties or conditions
              of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
              PARTICULAR PURPOSE. You are solely responsible for determining the
              appropriateness of using or redistributing the Work and assume any
              risks associated with Your exercise of permissions under this License.
        
           8. Limitation of Liability. In no event and under no legal theory,
              whether in tort (including negligence), contract, or otherwise,
              unless required by applicable law (such as deliberate and grossly
              negligent acts) or agreed to in writing, shall any Contributor be
              liable to You for damages, including any direct, indirect, special,
              incidental, or consequential damages of any character arising as a
              result of this License or out of the use or inability to use the
              Work (including but not limited to damages for loss of goodwill,
              work stoppage, computer failure or malfunction, or any and all
              other commercial damages or losses), even if such Contributor
              has been advised of the possibility of such damages.
        
           9. Accepting Warranty or Additional Liability. While redistributing
              the Work or Derivative Works thereof, You may choose to offer,
              and charge a fee for, acceptance of support, warranty, indemnity,
              or other liability obligations and/or rights consistent with this
              License. However, in accepting such obligations, You may act only
              on Your own behalf and on Your sole responsibility, not on behalf
              of any other Contributor, and only if You agree to indemnify,
              defend, and hold each Contributor harmless for any liability
              incurred by, or claims asserted against, such Contributor by reason
              of your accepting any such warranty or additional liability.
        
           END OF TERMS AND CONDITIONS
        
           APPENDIX: How to apply the Apache License to your work.
        
              To apply the Apache License to your work, attach the following
              boilerplate notice, with the fields enclosed by brackets "[]"
              replaced with your own identifying information. (Don't include
              the brackets!)  The text should be enclosed in the appropriate
              comment syntax for the file format. We also recommend that a
              file or class name and description of purpose be included on the
              same "printed page" as the copyright notice for easier
              identification within third-party archives.
        
           Copyright [yyyy] [name of copyright owner]
        
           Licensed under the Apache License, Version 2.0 (the "License");
           you may not use this file except in compliance with the License.
           You may obtain a copy of the License at
        
               http://www.apache.org/licenses/LICENSE-2.0
        
           Unless required by applicable law or agreed to in writing, software
           distributed under the License is distributed on an "AS IS" BASIS,
           WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
           See the License for the specific language governing permissions and
           limitations under the License.
License-File: LICENSE
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: Science/Research
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: Implementation :: CPython
Classifier: Programming Language :: Rust
Classifier: Topic :: Database :: Database Engines/Servers
Classifier: Topic :: Software Development :: User Interfaces
Requires-Python: <3.14,>=3.10
Requires-Dist: atpublic>=5.1
Requires-Dist: attrs>=24.1.0; python_version >= '3.10' and python_version < '4.0'
Requires-Dist: cityhash<1,>=0.4.7; python_version >= '3.10' and python_version < '4.0'
Requires-Dist: click>=8.0
Requires-Dist: cloudpickle>=3.1.1
Requires-Dist: cryptography>=45.0.3
Requires-Dist: dask==2025.1.0; python_version >= '3.10' and python_version < '4.0'
Requires-Dist: envyaml>=1.10.211231
Requires-Dist: filelock>=3.13
Requires-Dist: geoarrow-types<1,>=0.2; python_version >= '3.10' and python_version < '4.0'
Requires-Dist: git-annex>=10.20250220
Requires-Dist: gitpython>=3.1.46
Requires-Dist: opentelemetry-exporter-otlp-proto-grpc>=1.32.1
Requires-Dist: opentelemetry-exporter-otlp>=1.32.1
Requires-Dist: opentelemetry-exporter-prometheus>=0.55b1
Requires-Dist: opentelemetry-sdk>=1.32.1
Requires-Dist: pandas<3,>=1.5.3; python_version >= '3.10' and python_version < '4.0'
Requires-Dist: parsy>=2
Requires-Dist: prometheus-client>=0.22.1
Requires-Dist: py-yaml12
Requires-Dist: pyarrow-hotfix<1,>=0.4; python_version >= '3.10' and python_version < '4.0'
Requires-Dist: pyarrow<22,>=13.0.0; python_version >= '3.10' and python_version < '4.0'
Requires-Dist: python-dateutil>=2.8.2
Requires-Dist: pythran>=0.17.0; sys_platform == 'darwin'
Requires-Dist: pytz>=2022.7
Requires-Dist: rich>=13.9.4
Requires-Dist: sqlglot!=26.32.0,<28.7.0,>=23.4
Requires-Dist: strenum>=0.4.15; python_version <= '3.10'
Requires-Dist: structlog<26,>=24.2.0; python_version >= '3.10' and python_version < '4.0'
Requires-Dist: textual>=1.0.0
Requires-Dist: tomlkit>=0.12
Requires-Dist: toolz>=0.11
Requires-Dist: typing-extensions>=4.3.0
Requires-Dist: uv>=0.7.20
Requires-Dist: xorq-datafusion==0.2.5
Provides-Extra: bsl
Requires-Dist: boring-semantic-layer>=0.1.0; extra == 'bsl'
Provides-Extra: databricks
Requires-Dist: adbc-driver-manager>=1.0.0; extra == 'databricks'
Requires-Dist: databricks-sql-connector>=3.0.0; extra == 'databricks'
Provides-Extra: datafusion
Requires-Dist: datafusion<49,>=0.6; (python_version >= '3.10' and python_version < '4.0') and extra == 'datafusion'
Provides-Extra: duckdb
Requires-Dist: duckdb>=1.1.3; extra == 'duckdb'
Provides-Extra: examples
Requires-Dist: adbc-driver-postgresql>=1.4.0; extra == 'examples'
Requires-Dist: adbc-driver-sqlite>=1.4.0; extra == 'examples'
Requires-Dist: duckdb<2,>=0.10.3; (python_version >= '3.10' and python_version < '4.0') and extra == 'examples'
Requires-Dist: matplotlib>=3.8.0; extra == 'examples'
Requires-Dist: mcp>=1.5.0; extra == 'examples'
Requires-Dist: openai>=1.65.4; extra == 'examples'
Requires-Dist: pins[gcs]<1,>=0.8.3; (python_version >= '3.10' and python_version < '4.0') and extra == 'examples'
Requires-Dist: pyiceberg[sql-postgres,sql-sqlite]>=0.9.0; extra == 'examples'
Requires-Dist: quickgrove>=0.1.2; extra == 'examples'
Requires-Dist: requests>=2.32.3; extra == 'examples'
Requires-Dist: scikit-learn<2.0.0,>=1.4.0; extra == 'examples'
Requires-Dist: xgboost>=1.6.1; (python_version >= '3.10' and python_version < '4.0') and extra == 'examples'
Requires-Dist: xorq-feature-utils; extra == 'examples'
Requires-Dist: xorq-weather-lib; extra == 'examples'
Provides-Extra: gizmosql
Requires-Dist: adbc-driver-gizmosql>=1.1.5; extra == 'gizmosql'
Requires-Dist: duckdb>=1.1.3; extra == 'gizmosql'
Provides-Extra: ibis
Requires-Dist: ibis-framework>=10.5.0; extra == 'ibis'
Provides-Extra: postgres
Requires-Dist: adbc-driver-postgresql>=1.4.0; extra == 'postgres'
Requires-Dist: psycopg[binary]>=3.2.0; extra == 'postgres'
Provides-Extra: pyiceberg
Requires-Dist: pyiceberg[sql-postgres,sql-sqlite]>=0.9.0; extra == 'pyiceberg'
Provides-Extra: quickgrove
Requires-Dist: quickgrove>=0.1.2; extra == 'quickgrove'
Provides-Extra: snowflake
Requires-Dist: adbc-driver-snowflake>=1.5.0; extra == 'snowflake'
Requires-Dist: snowflake-connector-python<4,>=3.10.1; (python_version >= '3.10' and python_version < '4.0') and extra == 'snowflake'
Provides-Extra: sqlite
Requires-Dist: adbc-driver-sqlite>=1.4.0; extra == 'sqlite'
Provides-Extra: trino
Requires-Dist: trino==0.336.0; extra == 'trino'
Description-Content-Type: text/markdown

<div align="center">

![Xorq Logo](docs/images/Xorq_WordMark_RGB_Midnight.png#gh-light-mode-only)
![Xorq Logo](docs/images/Xorq_WordMark_RGB_BlueSky.png#gh-dark-mode-only)

![License](https://img.shields.io/github/license/xorq-labs/xorq)
![PyPI - Version](https://img.shields.io/pypi/v/xorq)
![CI Status](https://img.shields.io/github/actions/workflow/status/xorq-labs/xorq/ci-test.yml)

**A compute manifest and composable tools for ML.**

[Documentation](https://docs.xorq.dev) • [Website](https://www.xorq.dev)

</div>

---

# The Problem

You write a feature pipeline. It works on your laptop with DuckDB. Deploying
it to Snowflake ends up in a rewrite. Intermediate results should be cached so you add infrastructure and a result naming system. A requirement to track pipeline changes is introduced, so you add a metadata store. Congrats, you're going to production! It's time to add a serving layer ...

Six months later: five tools that don't talk to each other and a pipeline only one person understands

| Pain | Symptom |
|------|---------|
| **Glue code everywhere** | Each engine is a silo. Moving between them means rewriting, not composing. |
| **Runtime Feedback** | Imperative Python code where you can only tell if something will fail while running the job.
| **Unnecessary recomputations** | No shared understanding of what changed. Everything runs from scratch. |
| **Opaque Lineages** | Feature logic, metadata, lineage. All in different systems. Debugging means archaeology. |
| **"Works on my machine"** | Environments drift. Reproducing results means reverse engineering someone's setup and interrogating your own. |
| **Stateful orchestrators** | Retry logic, task states, failure recovery. Another system to manage, another thing that breaks.

Feature stores, Model registries, Orchestrators: Vertical silos that don't
serve agentic processes, which need context and skills, not categories.

# Xorq

![intro](docs/images/intro-light.svg#gh-light-mode-only)
![intro](docs/images/intro-dark.svg#gh-dark-mode-only)

**Manifest = Context.** Every ML computation becomes a structured,
input-addressed YAML manifest.

**Exprs = Tools.** A catalog to discover. A build system to deterministically
execute anywhere with user directed caching.

**Templates = Skills.** Various skills to get started e.g. scikit-learn
pipeline, feature stores, semantic layers etc.

```bash
$ pip install xorq[examples]
$ xorq init -t penguins
```

---

# The Expression

Write declarative [Ibis](https://ibis-project.org) expressions that can be
run like a tool. Xorq extends Ibis with caching, multi-engine execution, and
UDFs.

```python
import ibis
import xorq.api as xo
from xorq.common.utils.ibis_utils import from_ibis
from xorq.caching import ParquetCache

penguins = ibis.examples.penguins.fetch()

penguins_agg = (
    penguins
    .filter(ibis._.species.notnull())
    .group_by("species")
    .agg(avg_bill_length=ibis._.bill_length_mm.mean())
)

expr = (
    from_ibis(penguins_agg)
    .cache(ParquetCache.from_kwargs())
)
```

Declare `.cache()` on any node. Xorq handles the rest. No cache keys to generate or manage,
no invalidation logic to write.

## Compose across engines

One expression, many engines. Part of your pipeline runs on DuckDB, part on
Xorq's embedded [DataFusion](https://datafusion.apache.org) engine, UDFs
via Arrow Flight. Xorq systematically handles data transit with low overhead. Bye bye glue code.

```python
expr = from_ibis(penguins).into_backend(xo.sqlite.connect())
expr.ls.backends
```
```
(<xorq.backends.sqlite.Backend at 0x7926a815caa0>,
 <xorq.backends.duckdb.Backend at 0x7926b409faa0>)
```

## Expressions are tools, Arrow is the pipe

Unix gave us small programs that compose via stdout. Xorq gives you
expressions that compose via Arrow.

```
In [6]: expr.to_pyarrow_batches()
Out[6]: <pyarrow.lib.RecordBatchReader at 0x15dc3f570>
```

---

# The Manifest

Build an expression, get a manifest.

```bash
$ xorq build expr.py
builds/28ecab08754e
```

```
$ tree builds/28ecab08754e
builds/28ecab08754e
├── database_tables
│   └── f2ac274df56894cb1505bfe8cb03940e.parquet
├── expr.yaml
├── metadata.json
└── profiles.yaml
```

No external metadata store. No separate lineage tool. The build directory *is*
the versioned, cached, portable artifact.

```yaml
# Input-addressed, composable, portable
# Abridged expr.yaml
nodes:
  '@read_31f0a5be3771':
    op: Read
    name: penguins
    source: builds/28ecab08754e/.../f2ac274df56894cb1505bfe8cb03940e.parquet

  '@filter_23e7692b7128':
    op: Filter
    parent: '@read_31f0a5be3771'
    predicates:
      - NotNull(species)

  '@remotetable_9a92039564d4':
    op: RemoteTable
    remote_expr:
      op: Aggregate
      parent: '@filter_23e7692b7128'
      by: [species]
      metrics:
        avg_bill_length: Mean(bill_length_mm)

  '@cachednode_e7b5fd7cd0a9':
    op: CachedNode
    parent: '@remotetable_9a92039564d4'
    cache:
      type: ParquetCache
      path: parquet
```

## Reproducible builds

The manifest is roundtrippable and machine-writeable. Git-diff
your pipelines. Code review your features. Track python dependencies. Rebuild from YAML alone.

```bash
$ xorq uv build expr.py
builds/28ecab08754e/

$ ls builds/28ecab08754e/*.tar.gz
builds/28ecab08754e/sdist.tar.gz  builds/28ecab08754e/my-pipeline-0.1.0.tar.gz
```

The build captures everything: expression graph, dependencies, memory tables.
Share the build that has sdist, get identical results. No "works on my machine."

## Only recompute what changed

The manifest is input-addressed: same inputs = same hash. Change an input, get a new hash.

```python
expr.ls.get_cache_paths()
```
```
(PosixPath('/home/user/.cache/xorq/parquet/letsql_cache-7c3df7ccce5ed4b64c02fbf8af462e70.parquet'),)
```

The hash *is* the cache key. No invalidation logic to debug.
If the expression is the same, the hash is the same, and the cache is valid.
Change an input, get a new hash, trigger recomputation.

Traditional caching asks "has this expired?" Input-addressed caching asks "is
this the same computation?" The second question has a deterministic answer.

---

# The Tools

The manifest provides context. The tools provide skills: catalog, introspect,
serve, execute.

## Catalog

```bash
# Add to catalog
$ xorq catalog add builds/28ecab08754e/ --alias penguins-agg
Added build 28ecab08754e as entry a498016e-5bea-4036-aec0-a6393d1b7c0f revision r1

# List entries
$ xorq catalog ls
Aliases:
penguins-agg    a498016e-5bea-4036-aec0-a6393d1b7c0f    r1
Entries:
a498016e-5bea-4036-aec0-a6393d1b7c0f    r1      28ecab08754e
```

## Run

```bash
$ xorq run builds/28ecab08754e -o out.parquet
```

## Serve

Serve expressions anywhere via Arrow Flight:

```bash
$ xorq serve-unbound builds/28ecab08754e/ \
  --to_unbind_hash 31f0a5be37713fe2c1a2d8ad8fdea69f \
  --host localhost --port 9002
```

```python
import xorq.api as xo

backend = xo.flight.connect(host="localhost", port=9002)
f = backend.get_exchange("default")

data = {
    "species": ["Adelie", "Gentoo", "Chinstrap"],
    "island": ["Torgersen", "Biscoe", "Dream"],
    "bill_length_mm": [39.1, 47.5, 49.0],
    "bill_depth_mm": [18.7, 14.2, 18.5],
    "flipper_length_mm": [181, 217, 195],
    "body_mass_g": [3750, 5500, 4200],
    "sex": ["male", "female", "male"],
    "year": [2007, 2008, 2009],
}

xo.memtable(data).pipe(f).execute()
```

```
     species  avg_bill_length
0     Adelie             39.1
1  Chinstrap             49.0
2     Gentoo             47.5
```

## Debug with confidence

No more archaeology. Lineage is encoded in the manifest—not scattered across
tools—and queryable from the CLI.

```bash
$ xorq lineage penguins-agg

Lineage for column 'avg_bill_length':
Field:avg_bill_length #1
└── Cache xorq_cached_node_name_placeholder #2
    └── RemoteTable:236af67d399a4caaf17e0bf5e1ac4c0f #3
        └── Aggregate #4
            ├── Filter #5
            │   ├── Read #6
            │   └── NotNull #7
            │       └── Field:species #8
            │           └── ↻ see #6
            ├── Field:species #9
            │   └── ↻ see #5
            └── Mean #10
                └── Field:bill_length_mm #11
                    └── ↻ see #5
```

## Workflows, without state

No task states. Just retry on failure.

Xorq executes expressions as Arrow RecordBatch streams. There's no DAG of tasks
to checkpoint, just data flowing through operators. If something fails, rerun
from the manifest. Cached nodes resolve instantly; the rest recomputes.

## Scikit-learn Integration

Xorq translates `scikit-learn` Pipeline objects to deferred expressions:

```python
from xorq.expr.ml.pipeline_lib import Pipeline

sklearn_pipeline = ...
xorq_pipeline = Pipeline.from_instance(sklearn_pipeline)
```

---
# Templates

Ready-to-start code as skills:
```bash
$ xorq init -t <template>
```

| Template | Description |
|----------|-------------|
| `penguins` | Minimal example: caching, aggregation, multi-engine |
| `sklearn` | Classification pipeline with train/predict separation |


## Skills for humans

Templates work as easy to get started components with expressions ready to be
composed with your sources.

## Coming Soon

- `feast` — Feature store integration
- `boring-semantic-layer` — Metrics and dimensions catalog
- `dbt` — dbt model composition
- Feature Selection

---

# The Horizontal Stack

Write in Python. Catalog as YAML. Compose anywhere via Ibis. Portable compute
engine built on DataFusion. Universal UDFs via Arrow Flight.

![Architecture](docs/images/architecture-light.svg#gh-light-mode-only)
![Architecture](docs/images/architecture-dark.svg#gh-dark-mode-only)

Lineage, caching, and versioning travel with the manifest; cataloged, not locked
in a vendor's database.

**Integrations:** Ibis • scikit-learn • Feast(wip) • dbt (upcoming)

---

# Learn More

- [Quickstart tutorial](https://docs.xorq.dev/getting_started/quickstart)
- [Why Xorq?](https://docs.xorq.dev/#why-xorq)
- [Scikit-learn template](https://github.com/xorq-labs/xorq-template-sklearn)

---

Pre-1.0. Expect breaking changes with migration guides.
