digline-anthropic
An Anthropic target and judges for
digline: a prompt file goes in, a priced
Response comes out.
pip install digline-anthropic
Requires Python 3.12+, like digline itself.
from pathlib import Path
from digline_anthropic import AnthropicTarget
target = AnthropicTarget(
prompt_file=Path(__file__).parent / "prompts/answer.md",
system_file=Path(__file__).parent / "prompts/system.md",
model="claude-sonnet-5",
max_tokens=1024,
prefill="{", # put JSON in the model's mouth
)
Both files are recorded in every run, so the committed baseline carries the
prompt that produced it. Cost comes from a price list declared in code and
replaceable in one argument; an unknown model raises rather than costing
nothing. The key is never named here — the SDK reads ANTHROPIC_API_KEY.
The judges
A plugin is a target and a judge (ADR 0004): whoever generates can judge, with the same key and the same price list, and the twenty lines of SDK-and-JSON leave your suite.
from digline.core import LlmRubric
from digline_anthropic import AnthropicJudge
judge = AnthropicJudge(model="claude-haiku-4-5")
rubric = LlmRubric(
rubric="The answer is one sentence and cites the passage it came from.",
judge=judge,
threshold=0.8,
tolerance=0.05,
)
Faithfulness asks a judge to decompose rather than to score — how many claims
the output makes, how many the context supports — so it takes the other one:
from digline.core import Faithfulness
from digline_anthropic import AnthropicClaimJudge
faithful = Faithfulness(
judge=AnthropicClaimJudge(model="claude-haiku-4-5"),
threshold=0.9,
tolerance=0.05,
)
Both put { in the model's mouth and prepend it before parsing, and both read a
reply the model wrapped in a fence or a sentence. What judging cost is counted
on the judge and never reset:
from digline_anthropic import AnthropicJudge
judge = AnthropicJudge(model="claude-haiku-4-5")
print(f"{judge.calls} judgements, {judge.spent_usd:.4f} USD, {judge.latency_ms:.0f} ms")
A suite with samples=5 and Repeated(n=3) makes fifteen judging calls per
case, so this is not a rounding error. For a per-run figure, read it before and
after and subtract. It is in-process only today, and ADR 0004 §3 says what it
would take to put it in the report.
Apache-2.0. Docs: digline/digline.
Metadata
Release files for digline-anthropic 0.5.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| digline_anthropic-0.5.3.tar.gz | 20.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| digline_anthropic-0.5.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.0 kB
Release files / digline_anthropic-0.5.3.tar.gz
| Download URL | digline_anthropic-0.5.3.tar.gz |
|---|---|
| Size | 20.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
515d2ae09c4513c6cc43ce07cb8072e0982facf8b2f2997710efcc02c2942cea
|
|
BLAKE2b-256 checksum How to use checksums |
2515c18afc3589991ec74fedfbb72aa07d22cf3d867c4f674c0ff8c27dcd961e
|
| 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 20, 2026.
Transparency logRelease files / digline_anthropic-0.5.3-py3-none-any.whl
| Download URL | digline_anthropic-0.5.3-py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6e9c93c03365d0a46e3d6c3ec226a486e66034a58310e1705d56776a5d9e5dce
|
|
BLAKE2b-256 checksum How to use checksums |
a3741ef05e046669b9f756e7bc254f8a7b40095df0ffe59bb18ff6b55c5b9182
|
| 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 20, 2026.
Transparency log