Skip to main content

entail

Keep what a value means intact across LLM inference-stack boundaries.

An inference stack is a chain of parts — checkpoint and config, loader, engine, kernels, quantization, cache. Each part can be correct on its own terms while the meaning of a value is lost between two of them: a declared property the chosen kernel ignores, a setting that arrives under a name nobody reads any more, a cache that silently loses a token. The output is then wrong, fluently and without a warning.

entail declares what a value means where it crosses a boundary, checks the declaration against the real thing, and when they disagree it resolves the mismatch first — routes the value to a consumer that honours it, or converts it to the form the consumer reads — and prints one line saying what it changed. It stops only when no fix exists.

The name is the logical sense of entail: what a checkpoint declares must entail what the engine executes. (ent·AI·L — an AI library.)

Status: research prototype (alpha). Measured on one RTX 4070 Ti with the versions under "Tested with".

Why: a case measured end to end

Restating a model's own rope_scaling at launch — the route model cards give for enabling YaRN — drops rope_theta under transformers 5, and the engine silently falls back to a RoPE base of 10,000.

Llama-3.2-3B-Instruct, greedy, GSM8K (first 500 on vLLM, first 200 on SGLang):

untouched same rope_scaling passed again at launch with entail
vLLM 0.30.0 --hf-overrides 379 / 500 279 / 500, no warning 378 / 500
SGLang 0.5.20 --json-model-override-args 161 / 200 106 / 200 161 / 200 (outputs identical)

The degraded runs are identical to an explicit rope_theta = 10000. Outputs stay fluent; the answers are wrong. Qwen3 dense models happen to be safe because those model files fill in 1,000,000; Llama, Qwen3-MoE, Gemma and others do not.

Install

pip install "git+https://github.com/wwoosshh/entail"

Install it into the same environment as your engine (vLLM, SGLang or transformers). entail has no dependencies of its own. Once it is on PyPI: pip install entail-ai (the import name stays entail). uv pip install works the same way.

Check what it sees:

entail doctor

Use

Turn it on with one environment variable; nothing else changes.

ENTAIL=load vllm serve meta-llama/Llama-3.2-3B-Instruct --hf-overrides '{"rope_scaling": {...}}'
ENTAIL=load python -m sglang.launch_server --model-path ... --json-model-override-args '{...}'
ENTAIL=load python your_transformers_script.py

When it changes something, it says so:

[entail] resolved LlamaConfig.rope_scaling was given after the config was built; it replaces rope_parameters and
would have dropped rope_theta=500000.0, ...; kept it, as config.json would

From inside a script:

import entail
entail.enable()          # mode="load", policy="resolve"; child processes inherit it

How it reaches engine worker processes

vLLM and SGLang run the model in processes they start themselves. pip install puts one file, entail-autoinstall.pth, into site-packages; Python reads it at every start-up. Its single line checks the environment and does nothing unless ENTAIL is set. entail hook status|install|uninstall shows or manages it (an editable install does not place it — run entail hook install).

What it does

Resolves

mismatch resolution measured
a RoPE value given under its transformers-4 name after the config is built (rope_theta, rope_scaling — keyword to from_pretrained, attribute, vLLM --hf-overrides, SGLang --json-model-override-args) written where config.json would have put it, including per-layer-type RoPE (asks the config class) equal to the config.json route on 4 model families × 2 routes × 3 values; GSM8K restored (table above)
an attention backend that drops a declared model property (e.g. Gemma 2 logit soft-capping on transformers sdpa, SGLang flashinfer) switched to a backend measured to honour it (eager, triton) tokens equal the reference run; cost 1.18× (transformers), 1.13× (SGLang, the backend's own price)

Checks (and stops, when nothing can resolve it)

  • attention properties against each engine's backends, before any weight is read
  • config keys that would be swallowed, and tied-embedding declarations against the checkpoint
  • vLLM weights after repacking: layout, stride and a value sample against the declared transform
  • weights in memory against the checkpoint file (ENTAIL_SOURCE=1)
  • the KV cache contract (a request holds what it needs, nothing shrank) on transformers, vLLM's paged cache and SGLang

entail preflight --model /path/to/model --engine sglang --list runs the start-up checks without starting a server.

Configuration

variable values meaning
ENTAIL off (default), load, debug load: start-up checks and resolvers; debug: also every declared boundary, and uncovered cases become errors
ENTAIL_POLICY resolve (default), refuse refuse stops at the first mismatch instead of resolving
ENTAIL_ONLY e.g. rope_alias,sglang_adapter install only these adapters
ENTAIL_VERBOSE 1 print each adapter as it is installed
ENTAIL_SOURCE 1 also compare loaded weights with the checkpoint file (vLLM, a little I/O at start-up)
ENTAIL_SEED test names fault injection used to test the checks themselves; never set it in production

Tested with

transformers 5.12.1 and 5.17.0, vLLM 0.30.0, SGLang 0.5.20, torch 2.13–2.14, Python 3.12, one RTX 4070 Ti (12 GB). Other versions may work; entail doctor prints what is installed. On transformers 4.x the RoPE resolver has nothing to do and stays out of the way.

The capability table (which backend honours what) records its evidence per entry, and only entries marked measured are used as resolution targets. The measurement scripts and raw results are kept in the author's research workspace and are not in this repository yet.

Development

git clone https://github.com/wwoosshh/entail && cd entail
pip install -e .
entail hook install          # editable installs do not place the start-up hook
PYTHON=python bash tests/run_all.sh

Tests that need a local model look in ENTAIL_TEST_MODELS (default ~/models) and skip when it is absent.

한국어 안내: README.ko.md

License

See LICENSE.

Release files for entail-ai 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for entail-ai 0.1.0
File Size Uploaded
entail_ai-0.1.0.tar.gz 57.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for entail-ai 0.1.0
File Interpreter ABI Platform
entail_ai-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 114.2 kB

Release files / entail_ai-0.1.0.tar.gz

Download URL entail_ai-0.1.0.tar.gz
Size 57.8 kB
Tags Source
SHA-256 checksum
How to use checksums
5ced0ed1d28fe8bf7cd33366773846952b59e875cf1287245b1cb9b7ff174123
BLAKE2b-256 checksum
How to use checksums
1414fb24d158147c8070fb7a1842c429e55b346b18534396a9efa57ac6a0bdef
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 23, 2026.

Transparency log

Release files / entail_ai-0.1.0-py3-none-any.whl

Download URL entail_ai-0.1.0-py3-none-any.whl
Size 56.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
524ea9ab33f120f566d7cf6de08b6fa3ffcea6fe13e64992347d81d1949afbfc
BLAKE2b-256 checksum
How to use checksums
f28cc26a63451ad082d945bf4d7799a62c8a93d76363ec08f1444ba3ec3e501d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 23, 2026.

Transparency log

Release history Release notifications | RSS feed

1.0.2

2 release files

1.0.1

2 release files

1.0.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page