This release is a pre-release and may not be stable for production use.
Lintel
Dynamic GraphQL + Relay APIs from UMF, with an embeddable Python/FastAPI runtime and generated TypeScript operation/fragment artifacts for Batten applications.
Install the experimental alpha
pip install lintel-api==0.1.0a1
Import project from lintel.experimental.projection and
build_probe_schema / export_sdl from lintel.experimental.schema.
These expose the bounded S-01 scalar projection: string, boolean, exact decimal
text and canonical UUID, with optional-field omission preserved. Supply UMF JSON
and explicit record/field references; the example below uses the task-board model
in the source distribution.
from pathlib import Path
from lintel.experimental.projection import project
from lintel.experimental.schema import build_probe_schema
plan = project(
Path("docs/helix/02-design/examples/task-board.umf.json").read_text(),
("board", "Task"), "Task", {("board", "title"): "title"},
)
schema = build_probe_schema(plan, {"title": "Fabricated task"})
assert schema.execute_sync("{ probe { title } }").data == {
"probe": {"title": "Fabricated task"}
}
The alpha contains laboratory probe and echo roots. Do not mount them as a
production API. Native execution/admission, Relay identity/pagination, TypeScript
clients and Batten embedding are not provided by this wheel. Native qualification
harnesses and governed specifications are included in the source archive, without
installing PostgreSQL or its tools as library dependencies. Experimental APIs may
change between alpha releases. Python 3.11 is the initial qualified interpreter.
Lintel is a provisional name. This repository currently contains the HELIX specifications and a bounded direct UMF interoperability spike. The spike reads UMF JSON through the public umf-core reader/validator and builds a dynamic Strawberry schema. It is not a production API service.
Run uv sync --locked --group spike --python 3.11, then
uv run --locked --group spike python -m spikes.direct_umf.run.
Verification and limits distinguish
this proof from native execution, Relay clients and Batten embedding.
Start with the project packet, scope and MVP, and architecture.
The intended family documentation location is documentdrivendx.github.io/lintel. The source repository is created; family-catalog registration and documentation-site publication remain pending.
The native read spike
measures pagination, declared-key batching and request consistency on disposable
PostgreSQL 18. Run uv sync --locked --group spike --group native-spike, then
uv run --locked --group spike --group native-spike python -m spikes.native_reads.run.
Use both dependency groups for python scripts/check_quality.py on the current tree.
Results and gaps keep unsupported
execution guarantees explicit; no upstream schema API is introduced.
Metadata
Release files for lintel-api 0.1.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| lintel_api-0.1.0a1.tar.gz | 158.4 kB | With provenance | Details for lintel_api-0.1.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lintel_api-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details for lintel_api-0.1.0a1-py3-none-any.whl |
Total release size: 164.9 kB
Release files / lintel_api-0.1.0a1.tar.gz
| Download URL | lintel_api-0.1.0a1.tar.gz |
|---|---|
| Size | 158.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8099dff22ab31e79a40d4c879c3567e01e88e377c110e9236468e4466d9d366c
|
|
BLAKE2b-256 checksum How to use checksums |
4592f720b613aca3141110922239be23b434ac6a2d77d5e82d4ef2200c70e660
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logRelease files / lintel_api-0.1.0a1-py3-none-any.whl
| Download URL | lintel_api-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9de2c63ec7e7947c36a558a3c6d9f3a420fd6840f572643f794fe92056d1a403
|
|
BLAKE2b-256 checksum How to use checksums |
3d07bb4f463dee546d27fdabad432c0d66061896f3e28b59ae4ce4b2c7c699de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logSecurity for lintel-api 0.1.0a1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for lintel_api-0.1.0a1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.