chain-probe
Step-level semantic fault isolation for multi-step LLM pipelines.
Your 4-step LLM pipeline failed. Which step caused it? Existing tools (Langfuse, Arize, Promptfoo) trace metadata or evaluate final output — none do step-level semantic fault isolation. chain-probe does.
pip install chain-probe
Quick Start
from chain_probe import Pipeline
pipeline = Pipeline("my_rag_pipeline")
@pipeline.probe()
def retrieve(query):
return search_documents(query)
@pipeline.probe(
validator=lambda inp, out: (0.9, "ok") if not hallucinated(out) else (0.1, "hallucinated"),
threshold=0.5,
)
def generate(docs):
return call_llm(docs)
@pipeline.probe()
def format(answer):
return format_response(answer)
result = pipeline.cascade(initial_input="What is our refund policy?")
print(result.summary())
# Pipeline: my_rag_pipeline
# Verdict: FAILED
# Steps: 3 total, 1 failed
# Root cause: step 1 (generate)
#
# ✓ [0] retrieve: pass
# ✗ [1] generate: fail [root_cause] score=0.10
# reason: hallucinated
# ✓ [2] format: pass
CASCADE Fault Analysis
The key innovation: when multiple steps fail, chain-probe distinguishes root cause from inherited failure.
- ROOT_CAUSE — This step introduced the failure
- INHERITED — This step failed because it received bad input from an upstream failure
- INDEPENDENT — This step failed for its own reasons, unrelated to upstream failures
result = pipeline.cascade(initial_input="test")
for step in result.steps:
if step.verdict != "pass":
print(f"Step {step.step_name}: {step.fault_type.value}")
# "retrieve: root_cause"
# "generate: inherited"
# "format: inherited"
Features
@probedecorator — Zero-config step registration- CASCADE analysis — Automatic root cause vs inherited fault classification
- Validators — Per-step semantic validation with score + reason
- Framework-agnostic — Works with LangChain, LlamaIndex, raw API calls, anything
- Zero dependencies — Pure Python, nothing to install
- SQLite history — Track cascade results over time
- CI gate — Exit code 0/1 for pipeline health
Convenience API
from chain_probe import run_cascade
result = run_cascade(
steps=[retrieve, generate, format, deliver],
initial_input="user query",
pipeline_name="rag_v2",
)
if not result.passed:
print(f"Root cause: {result.root_cause.step_name}")
Store & History
from chain_probe import ProbeStore
store = ProbeStore("pipeline_runs.db")
store.save(result)
history = store.get_history("my_pipeline", limit=10)
License
MIT
Metadata
Release files for chain-probe 0.1.0
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 |
|---|---|---|---|---|
| chain_probe-0.1.0.tar.gz | 11.2 kB | Without provenance | Details for chain_probe-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| chain_probe-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for chain_probe-0.1.0-py3-none-any.whl |
Total release size: 20.2 kB
Release files / chain_probe-0.1.0.tar.gz
| Download URL | chain_probe-0.1.0.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd6fb9ccee87783322063bc9119635ac17152cf35ee3c630a198d037fefbf660
|
|
BLAKE2b-256 checksum How to use checksums |
dfb4b52f2424500323acff13a7d983b9f7f543313a50a62342a74d5445b5c866
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / chain_probe-0.1.0-py3-none-any.whl
| Download URL | chain_probe-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f57062cd9b730827b77e4cdcc31e98157b2579a2262dd3373adc1545bf59971
|
|
BLAKE2b-256 checksum How to use checksums |
2b4144f70b61de45e964c0ed008abdbf1889ef6445efc7a5b0dec0044779a499
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for chain-probe 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.