judgment-pack MCP sunucusu
Commit 14 Kas 2026Belgeleri doğrulamak ve Judgment Pack Specification (JPS) ile uyumluluğu değerlendirmek için çevrimdışı bir referans çalışma zamanı sağlar.
Ayrıca bilinen adı Judgment-Pack/judgment-pack-runtime, judgment-pack-runtime
- Yıldızlar
- 2
- Araçlar
- —
- İndirmeler, 30 gün
- —
- En son sürüm
- 0.46.0
- Son commit
- 14 Kas 2026
- Lisans
- Apache-2.0
judgment-pack MCP nedir?
judgment-pack bir MCP sunucusudur. Belgeleri doğrulamak ve Judgment Pack Specification (JPS) ile uyumluluğu değerlendirmek için çevrimdışı bir referans çalışma zamanı sağlar.
Özet, projenin README dosyasından oluşturuldu
judgment-pack MCP sunucusu hakkında
Bu çevrimdışı referans çalışma zamanı, geliştiricilerin ve AI agent'ların belgeleri Judgment Pack Specification ile doğrulamasına olanak tanır. 0.1.0-draft, 0.2.0-draft ve Core 0.3.0 dahil olmak üzere çeşitli spesifikasyon sürümleri için uyumluluğu değerlendirmek üzere satıcıdan bağımsız bir uygulama sunar. Kullanıcılar bunu jpack binary dosyası ile yerel olarak çalıştırabilir veya stdio üzerinden Model Context Protocol kullanarak bir AI istemcisine bağlayabilir.
Sunucu; bir agent'ın belge doğrulamasını bir tool call olarak gerçekleştirebilmesi için experimental_evaluate, experimental_test_packs, experimental_test_cases ve experimental_test_graphs gibi belirli araçlar sunar. Harici kaynaklar getirmeye veya kurumsal yetki tesis etmeye değil, belgelerin yapısını ve uyumluluğunu doğrulamaya odaklanır. Bir referans uygulama olduğu için, belgelerin beyan edilen sürüm ve profil gereksinimlerine uymasını sağlamak amacıyla spesifikasyonda tanımlanan çözüm modelini uygulamak için ortak bir evaluator kullanır.
Neler yapabilirsiniz
- 1Belirli bir belgeyi doğrulayınBir AI agent, bir belgenin belirli bir judgment pack ile uyumlu olup olmadığını kontrol etmek için experimental_evaluate aracını kullanabilir.
- 2Uyumluluk test paketlerini çalıştırınGeliştiriciler, çalışma zamanının uyumluluğunu doğrulamak için bir AI'ya paketlenmiş değerlendirme külliyatını (evaluation corpus) çalıştırması talimatını verebilir.
- 3Graf bileşimlerini test edinDeneysel graf yapılarının spesifikasyon gereksinimlerini karşıladığından emin olmak için bir AI'ya bu yapıları test etme görevi verebilirsiniz.
Projenin README dosyasından alınmıştır. Her kullanım durumu, oradaki bir alıntı ile kontrol edilir.
judgment-pack MCP nasıl yüklenir
Biçimler 10 Kas 2026 tarihinde doğrulandıCursor'a ekleGoose'a eklejudgment-pack MCP'yi Claude Code içine yükleyin
$ claude mcp add judgment-pack-runtime -- docker run -i --rm ghcr.io/judgment-pack/judgment-pack:0.46.0judgment-pack MCP'yi Cursor içine yükleyin
~/.cursor/mcp.json
{
"mcpServers": {
"judgment-pack-runtime": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/judgment-pack/judgment-pack:0.46.0"
]
}
}
}judgment-pack MCP'yi VS Code içine yükleyin
.vscode/mcp.json
{
"servers": {
"judgment-pack-runtime": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/judgment-pack/judgment-pack:0.46.0"
]
}
}
}judgment-pack MCP'yi VS Code CLI içine yükleyin
$ code --add-mcp '{"name":"judgment-pack-runtime","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/judgment-pack/judgment-pack:0.46.0"]}'judgment-pack MCP'yi Claude Desktop içine yükleyin
claude_desktop_config.json
{
"mcpServers": {
"judgment-pack-runtime": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/judgment-pack/judgment-pack:0.46.0"
]
}
}
}judgment-pack MCP'yi Codex içine yükleyin
$ codex mcp add judgment-pack-runtime -- docker run -i --rm ghcr.io/judgment-pack/judgment-pack:0.46.0judgment-pack MCP'yi Codex config.toml içine yükleyin
~/.codex/config.toml
[mcp_servers.judgment-pack-runtime] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/judgment-pack/judgment-pack:0.46.0"]
judgment-pack MCP'yi Gemini CLI içine yükleyin
$ gemini mcp add -s user judgment-pack-runtime docker -- run -i --rm ghcr.io/judgment-pack/judgment-pack:0.46.0judgment-pack MCP'yi Gemini settings.json içine yükleyin
~/.gemini/settings.json
{
"mcpServers": {
"judgment-pack-runtime": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/judgment-pack/judgment-pack:0.46.0"
]
}
}
}Yapılandırma
JPACK_CONFIGPath to a jpack.json project configuration (ADR-0012). Optional: without it the server reads jpack.json from its launch directory (/project in this image; mount a project there), and a project that does not use the convention still validates and evaluates pack documents passed over the wire.
| Ad | Açıklama | Sunucu |
|---|---|---|
| JPACK_CONFIG | Path to a jpack.json project configuration (ADR-0012). Optional: without it the server reads jpack.json from its launch directory (/project in this image; mount a project there), and a project that does not use the convention still validates and evaluates pack documents passed over the wire. |
Otomatik kontroller
Çalıştırıldı 13 Kas 2026Tam rapor →Henüz doğrulanmadı. Bir sunucunun 80 puana, ciddi bir bulgu olmamasına ve kontrol edebilmemiz için yeterli veriye ihtiyacı vardır. Kontroller nasıl çalışır · Daha fazla puan için nelerin düzeltileceği
- Kaynak deposu bağlantılı ve erişilebilirjudgment-pack/judgment-pack-runtime is public and reachablegithub.com/judgment-pack/judgment-pack-runtime ↗Geçti
- Paket, bu depoyu kaynağı olarak gösteriyorKontrol edilmedi
- Derleme kökeni (Sigstore onayı)Kontrol edilmedi
- Açık kaynak lisansı (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Geçti
- Son bir yıl içinde commit veya sürüm mevcutLast commit or release 2026-11-13github.com/judgment-pack/judgment-pack-runtime ↗Geçti
- OpenSSF ScorecardKontrol edilmedi
- Paket adı popüler bir pakete yakın değilKontrol edilmedi
- Pakette veya bağımlılıklarında kritik uyarı yokKontrol edilmedi
- Modele yönelik gizli talimat yok0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersGeçti
- Yıkıcı araçlar etiketlenmişKontrol edilmedi
- Uzak uç nokta MCP el sıkışmasına yanıt veriyorKontrol edilmedi
judgment-pack
Status: pre-1.0
Tagged binaries are official only when they appear on this repository's GitHub Releases page with
checksums.txt. Development checkouts may temporarily embed unreleased JPS snapshots, but the release workflow rejects them.
judgment-pack is the vendor-neutral reference runtime for the Judgment Pack Specification
(JPS). It is a reference implementation, not the only valid one: the normative specification,
schemas, and conformance corpus are owned by the separate
judgment-pack-spec repository, and an
independent implementation is judged against the complete normative requirements of the conformance
class it claims — not against this runtime. Results from the corpus published for the exact version
it names are required evidence for such a claim and are not exhaustive evidence of it (§3.4.1).
The runtime validates documents. It does not fetch a source, authorize an action, or establish
truth, organizational authority, safety, or operational fitness. It bundles 0.1.0-draft,
0.2.0-draft, and Core 0.3.0, and validates a document against its exact declaration.
It also admits, EXPERIMENTALLY and with the base profile only, the staged draft selector
0.4.0-draft of Draft RFC 0031 (annotations and value sets), vendored from an unreleased
specification commit; the specification may rename or change it, and no claim covers it
(ADR-0075).
Core 0.3.0 resources are imported from the published Spec tag v0.3.0, commit
27cb29bf13e4a2d58d69fe19c7ebfeb762b014fc. Core 0.3.0 support is base-only. Runtime discovery reports
evaluatorCapabilities separately from document supportedSpecVersions, with
supportedProfiles: ["base"] scoped to the Core 0.3.0 evaluator entry. This says
nothing about Policy or Dialect profile support.
For the version covered by the claim in CONFORMANCE.md, one shared
evaluator applies the specification's §§7–8 resolution model per
ADR-0007, and eleven surfaces reach it: jpack experimental evaluate and evaluate-corpus, the project walk jpack packs test, the graph verbs
jpack experimental graph evaluate and graph test, the version comparison
jpack experimental compare, the in-process Go API sdk.Pack.Evaluate
(ADR-0073), and the experimental_evaluate,
experimental_test_packs, experimental_test_cases and experimental_test_graphs MCP tools. The experimental namespace is a stability
statement: such a surface may change or be removed without compatibility promise. It is not a statement
about conformance. That evaluator implements the evaluator conformance class Core 0.2.0-draft adds —
the §8.2 input preflight, the §8.3 portable disposition with its RFC 8785 byte agreement, the §8.4
error classes and their fixed precedence, and the §10 limits — per
ADR-0010 and
ADR-0011.
Pack-aware operations select the evaluator contract from the exact pack's
specVersion: 0.2.0-draft or 0.3.0, or, experimentally, the staged 0.4.0-draft, whose packs
are evaluated as their evaluation form (annotations removed, value-set references expanded).
Graph evaluation, the dialect check and the policy check refuse the staged selector with
JPS-STAGED-DRAFT-UNSUPPORTED. Internal legacy entry points and standalone
authoring tools retain their 0.2.0-draft default; standalone tools accept explicit
spec_version: "0.3.0". Selection never infers a version from a routes member.
See ADR-0063 for the compatibility decisions.
This runtime's conformance claim is stated, in full and only, in
CONFORMANCE.md. JPS §3.4.1 fixes the entire form such a claim may take — the class,
one exact specVersion, the corpus version, the results obtained, and in the claim's own words that
every row of that corpus version passed — so this README states no part of it and neither does any
other surface: a partial restatement would be the partial claim §3.4.1 forbids. Read that file for the
claim, its version scope, its evidence, and everything it does not assert, which includes anything at
all about a pack, its facts, or the wisdom of acting on a disposition (§3.5).
jpack experimental evaluate-corpus runs the bundled evaluation corpus and reports its rows —
the evidence §3.4.1 requires of a claim of this class, and explicitly not exhaustive evidence of one;
see CONFORMANCE.md.
That command carries one further opt-in, --rfc0008-quantifiers, which is a draft-RFC
prototype per ADR-0009: it admits the
collection quantifiers exists, every, and uniform proposed by the specification's RFC 0008
(Draft). Those operators belong to no published JPS version. A pack using one is not valid under
JPS 0.1.0-draft, spec validate rejects it, the evaluator without the flag refuses it, and every
successful evaluation payload produced under the flag says so in band through a draftPrototype
member — a refusal is an operational error and carries none. The flag is CLI only; the MCP tool does
not expose it.
A second opt-in, --rfc0016-outcome-values, is a draft-RFC prototype on the same terms, per
ADR-0039. It admits the value declarations
proposed by the specification's RFC 0016 (Draft): an outcome declares named values under
org.judgmentpack.outcome-values, each a constant or a copy of one fact, and the disposition of that
outcome carries them in a value member. That member is the draft's and no member of §8.3. A
declared value that does not resolve withholds the outcome, and the result is unresolved with
reason unknown. The name is reserved, so a pack carrying a declaration is not valid under any
published JPS version, spec validate rejects it, and the evaluator without the flag refuses it.
A value drawn from a fact is a copy of that fact and is not verified. The two flags are mutually
exclusive, and this one is CLI only too.
The command binary is jpack. The project, repository, and release archives keep the
judgment-pack name; the executable they carry is jpack.
Implemented commands
jpack version
jpack artifact version --base <x.y.z> [--candidate <x.y.z>]
jpack dialect contract
jpack dialect init [--dialect-version 2|3]
jpack dialect canonicalize <dialect-or->
jpack dialect digest <dialect-or->
jpack dialect validate <dialect-or->
jpack dialect schema [--dialect-version 2|3]
jpack dialect reference
jpack dialect check <dialect-or-> --pack <pack-or->
jpack spec validate <pack-or->
jpack spec test-conformance [suite] [--strict]
jpack spec schema <spec-version>
jpack spec examples [name] [--spec-version V]
jpack packs list (jpack.json project convention; ADR-0012, not part of the spec)
jpack packs validate [--id X]
jpack packs test [--id X] [--require-matrix] (EXPERIMENTAL SURFACE; claim: CONFORMANCE.md)
jpack packs suggest [--id X] [--base ROW] [--write F|-] [--max N] [--include-hugs] (candidate row INPUTS, never rows; ADR-0024)
jpack packs lock (declare the current documents as the project's reviewed set; ADR-0019)
jpack packs verify (check the project against that reviewed set)
jpack packs covers --lock F (--id X --pack F | --graph-id X --graph F) [--config F] (does the lock's entry pin these exact bytes? opens no project; ADR-0072)
jpack packs lint [--producers M] (every consulted pointer has a producer; ADR-0022)
jpack packs schema
jpack packs describe <pack-or-> [--format markdown|json] (EXPERIMENTAL; the whole pack as written, for review; opens no project; ADR-0074)
jpack packs describe <pack-or-> --filter key=value ... (EXPERIMENTAL; only the outcomes and rules of a 0.4.0-draft pack whose annotations match; ADR-0075)
jpack mcp
jpack experimental evaluate <pack-or-> (EXPERIMENTAL SURFACE; claim: CONFORMANCE.md)
jpack experimental evaluate --pack-id X (EXPERIMENTAL SURFACE; resolves one decision id through jpack.json)
jpack experimental evaluate <pack-or-> --rfc0008-quantifiers (DRAFT-RFC PROTOTYPE; not an input the class defines)
jpack experimental evaluate <pack-or-> --rfc0016-outcome-values (DRAFT-RFC PROTOTYPE; a pack that declares values is not an input the class defines)
jpack experimental evaluate-corpus (EXPERIMENTAL SURFACE; corpus results, the evidence §3.4.1 requires)
jpack experimental compare <old-pack> <new-pack> --inputs <file> (EXPERIMENTAL SURFACE; the inputs two versions decide differently; ADR-0045)
jpack experimental graph list (EXPERIMENTAL: the configured graphs, resolved; ADR-0029)
jpack experimental graph validate <graph-or-> (EXPERIMENTAL composition prototype; spec RFC 0002, Draft; ADR-0015)
jpack experimental graph evaluate <graph-or-> [--inputs <file-or->] [--rehearsal] (EXPERIMENTAL SURFACE; claim: CONFORMANCE.md)
jpack experimental graph explain <graph-or-> (the evaluation plan; nothing is evaluated)
jpack experimental graph test <graph-or-> --rows <file-or-> (EXPERIMENTAL SURFACE; claim: CONFORMANCE.md)
jpack experimental graph schema
jpack experimental policy contract
jpack experimental policy init --kind policy --format-version 0.0.2 --id <id> --version <artifact-version>
jpack experimental policy schema --kind policy --format-version 0.0.2
jpack experimental policy canonicalize <document-or->
jpack experimental policy digest <document-or->
jpack experimental policy validate <document-or->
jpack experimental policy check <document-or-> --materials <materials-or->
The pack argument and --pack-id are mutually exclusive: one pack, one source, and supplying both
or neither is an invocation error rather than a precedence rule. --pack-id honors --config and
JPACK_CONFIG like every other command that reads a configuration.
The namespace is jpack spec, not jpack jps. JPS remains the name of the
specification and the prefix of its provisional diagnostic codes.
The mcp command serves the same offline operations to a Model Context Protocol client over stdio,
so an agent can validate documents as a tool call; see
docs/mcp-clients.md for per-client setup and
docs/agent-testing.md for the agent-driven testing protocol.
Install a tagged release
Download the archive for your operating system and architecture from
GitHub Releases. Each archive
includes the jpack binary, README, the CONFORMANCE.md claim the source it was
built from carries, Apache-2.0 license, attribution notice, and third-party notices.
Asset names follow this pattern:
judgment-pack_<version>_<os>_<arch>.tar.gz
judgment-pack_<version>_windows_<arch>.zip
For example, release v0.1.0 uses judgment-pack_0.1.0_linux_amd64.tar.gz. Linux and macOS users
can extract an archive and install the binary into a user-owned directory already on PATH:
tar -xzf judgment-pack_0.1.0_linux_amd64.tar.gz
install -m 0755 jpack "$HOME/.local/bin/jpack"
jpack version
On Windows, expand the .zip, move jpack.exe into a directory on your user PATH, and
run:
jpack version
Verify the archive before extracting it. On Linux:
grep ' judgment-pack_0.1.0_linux_amd64.tar.gz$' checksums.txt | sha256sum --check
On macOS:
grep ' judgment-pack_0.1.0_darwin_arm64.tar.gz$' checksums.txt | shasum -a 256 --check
On Windows PowerShell:
(Get-FileHash .\judgment-pack_0.1.0_windows_amd64.zip -Algorithm SHA256).Hash
Select-String -Path .\checksums.txt -Pattern ' judgment-pack_0.1.0_windows_amd64.zip$'
The two Windows hashes must match. Release archives also carry GitHub build-provenance attestations, which a current GitHub CLI can verify:
gh attestation verify judgment-pack_0.1.0_linux_amd64.tar.gz --repo Judgment-Pack/judgment-pack-runtime
Packages for Homebrew, Scoop, apt, and go install are not published yet. In particular, source
installation with go install does not receive the release linker metadata, so use a release
archive when you need an accurately reported runtime version.
Evaluate one decision
With jpack on your PATH, this is the whole loop: a pack, a facts document, and a disposition.
Save a pack that approves an expense unless its amount is over 5000:
cat > pack.json <<'EOF'
{
"specVersion": "0.2.0-draft",
"id": "https://example.invalid/judgment-packs/expense-approval",
"version": "0.1.0",
"title": "Expense approval",
"decision": {
"intent": "Approve ordinary expenses without review.",
"question": "May this expense be approved?"
},
"outcomes": [
{ "id": "approve", "label": "Approve" },
{ "id": "decline", "label": "Decline" }
],
"rules": [
{
"id": "over-limit",
"description": "An amount over 5000 is declined.",
"when": { "op": "fact", "path": "/expense/amount", "operator": "greater-than", "value": "5000" },
"outcome": "decline",
"onUnknown": "escalate"
}
],
"fallbackOutcome": "approve",
"escalation": {
"triggers": ["unknown"],
"target": { "kind": "human-role", "name": "Finance reviewer" }
}
}
EOF
jpack spec validate pack.json
Give it the facts of one expense and evaluate. The amount is a decimal string, as the specification requires for a number a rule compares:
$ echo '{"expense": {"amount": "120"}}' > facts.json
$ jpack experimental evaluate pack.json --facts facts.json
EXPERIMENTAL SURFACE evaluation (claim and scope: CONFORMANCE.md; this result authorizes nothing)
disposition: outcome approve
trace: rule over-limit: false
artifacts: immutable-git-ref · sha256 081cf18af9fe667a5da5acab465f4cf6118a00742bb6e5527d4d45fc09f25185
Now remove the amount. The rule cannot be decided, its onUnknown is escalate, and the pack
names who takes the case, so the answer is a handoff rather than a guess. The trace line names the
fact that was missing:
$ echo '{"expense": {}}' > facts.json
$ jpack experimental evaluate pack.json --facts facts.json
EXPERIMENTAL SURFACE evaluation (claim and scope: CONFORMANCE.md; this result authorizes nothing)
disposition: unresolved (unknown)
handoff: requested -> human-role "Finance reviewer" (triggered by unknown)
trace: rule over-limit: unknown onUnknown=escalate [fact /expense/amount absent]
artifacts: immutable-git-ref · sha256 081cf18af9fe667a5da5acab465f4cf6118a00742bb6e5527d4d45fc09f25185
Releases up to 0.23.1 print the last trace line without the bracket naming the missing fact.
Both runs exit 0: producing a disposition is success, whichever it is. --format json gives the
same result as a payload, with the disposition in its canonical form. A disposition is data. It
authorizes nothing, and acting on it is the caller's decision.
From here, docs/building-with-packs.md covers a project of several
packs, their test matrices, and the audit trail; jpack spec examples --spec-version 0.2.0-draft
lists larger starting points the evaluator accepts, from 0.24.0.
From a Go program
Package sdk runs the same evaluator in-process
(ADR-0073). It takes every input as bytes and
reads no project directory, file, environment variable or network:
pack, err := sdk.Load(ctx, packBytes, sdk.LoadOptions{})
// err is a *sdk.Refusal for a pack the evaluator refuses, with its validation diagnostics.
evaluated, err := pack.Evaluate(ctx, factsBytes, nil) // nil: no evidence document
// err is a *sdk.Refusal with the §8.4 class and phase for an input it refuses.
fmt.Println(evaluated.Disposition.Kind, string(evaluated.CanonicalDisposition()))
A loaded pack is immutable, safe for concurrent use, and never validated again. The contract,
options and limits are those of jpack experimental evaluate run outside a project. The package is
experimental and may change in any minor release before 1.0 (VERSIONING.md).
sdk/example_test.go is a runnable example.
pack.Identity() names the loaded pack: its id, version, specVersion, stated profile, and the
sha256: digest of the exact bytes given. pack.View() describes the whole document without
evaluating it (ADR-0074), as a view.PackView of package
sdk/view: every member as typed data, in
document order and as written, with a canonical JSON encoding (view.JSON()) and a Markdown
rendering for a reviewer (view.Markdown()). jpack packs describe writes the same bytes. The
view is experimental and carries its own viewVersion. For a pack under the staged draft selector
0.4.0-draft, the view shows its value sets and annotations, and pack.FilteredView(criteria)
returns only the outcomes and rules whose annotations match every criterion, as a
view.FilteredView that says it is not the pack and carries its own filteredViewVersion
(ADR-0075).
Build and try it locally
Go 1.24 or newer is required to build from source: internal/fssecure binds every project file
read to a directory handle through os.Root, which is a Go 1.24 standard-library type.
If an older WSL setup has persisted GO111MODULE=off, clear it once with
go env -u GO111MODULE. The commands below explicitly enable module mode as a compatibility
measure.
env GO111MODULE=on CGO_ENABLED=0 go build -trimpath -o ./bin/jpack ./cmd/jpack
./bin/jpack --help
./bin/jpack version
From a sibling checkout of judgment-pack-spec, validate a synthetic example:
./bin/jpack spec validate ../judgment-pack-spec/examples/minimal-expense-approval.json
./bin/jpack spec validate --format json ../judgment-pack-spec/examples/minimal-expense-approval.json
Standard input is accepted explicitly with -:
./bin/jpack spec validate --format json - < pack.json
Core 0.3.0 semantic validation also reports recommended JPS-RULES-OVERLAP
warnings for pairs naming different outcomes. The diagnostic points at
/rules/<index>/when, identifies both rules/outcomes, includes an exact region
or witness when decidable, and supplies suggestedRewrite: {ruleId, when} when
the complete rewritten pack fits the applicable carrier and generation limits.
Otherwise rewriteUnavailable explains why no pasteable replacement is supplied.
Generated facts are checked against the same carrier limits before publication;
if no admissible witness or supported exact region is available, certainty stays
not-excluded. Ascending bands use all of the lower comparison and an exclusive upper bound;
other pairs use all of the first condition and not of the second. Missing or
incomparable facts preserve unknown, including under not. Plain validation
still passes. Same-outcome pairs are silent. Analysis limits or independent paths
produce not-excluded; output bounds set diagnosticsTruncated without cutting
an exact region or rewrite. See ADR-0066.
Run a bundled document-conformance corpus — 0.1.0-draft by default, or an exact bundled version:
./bin/jpack spec test-conformance
./bin/jpack spec test-conformance --format json
./bin/jpack spec test-conformance --spec-version 0.2.0-draft
./bin/jpack spec test-conformance --spec-version 0.3.0
./bin/jpack spec test-conformance --strict
By default a case passes when its expected diagnostic is among those reported; --strict also fails a case that reports a diagnostic its manifest entry does not expect, naming each one, which is what the corpus's single-defect rule needs. Core 0.3.0 optional expectedAdvisories assertions are checked, with per-row advisoryStatus and separate advisories totals; the aggregate summary includes all checked manifest rows. Exact rule overlap fails strict mode even when its advisory expectation matches; normative document actualStatus stays valid. not-excluded remains a warning in every mode. Advisory-only suites are supported.
Run the bundled evaluation corpus of JPS 0.2.0-draft through the experimental evaluator. Every
row is compared by disposition equality as §8.3 defines it — both the row's expectation and the
produced disposition go through the same RFC 8785 canonicalizer, so a set's stored order is not a
difference — or by its expected §8.4 error class and phase.
This reports results: the required, non-exhaustive evidence for the claim in
CONFORMANCE.md, and not that claim. A mismatching row decides nothing by itself,
because §3.4 makes a divergence as likely to be a defect in the row as in this implementation, and only
a project-issued erratum can excuse a row:
./bin/jpack experimental evaluate-corpus
./bin/jpack experimental evaluate-corpus --format json
./bin/jpack experimental evaluate-corpus --spec-version 0.2.0-draft
./bin/jpack experimental evaluate-corpus --spec-version 0.3.0
Inspect or copy the bundled schema without network access:
./bin/jpack spec schema 0.1.0-draft
./bin/jpack spec schema 0.2.0-draft
./bin/jpack spec schema 0.3.0
./bin/jpack spec schema 0.1.0-draft --write schema.json
./bin/jpack spec schema 0.1.0-draft --write -
The schema command refuses to overwrite an existing file. It is a different write from the audit trail below, which appends to a file the project's own configuration named and never replaces one.
Validation behavior
Validation short-circuits in this order:
- strict UTF-8 JSON carrier parsing, including duplicate-member rejection;
- exact
specVersiondispatch; - Core
0.3.0profile negotiation, defaulting an absent declaration tobasewithout changing input bytes; - Draft 2020-12 structural validation with URI, date, and date-time assertions;
- normative semantic reference and extension-declaration checks; and
- required-extension capability negotiation.
A known unsupported Core profile is refused before schema interpretation or facts/evidence admission,
with exactly {"code":"profile-unsupported","profile":"extended"}. Unknown, empty, null,
and non-string profile declarations are structural errors; malformed carrier input remains a carrier error.
An unknown but syntactically usable specVersion is unsupported, not invalid. The conformance
runner deliberately pins each case to the suite's declared specification version, so a fixture that
violates that pinned schema remains a structural negative case.
--through carrier and --through structural produce explicitly partial results. They never print
an unqualified “valid document” message.
The public MVP supports no JPS extensions. A structurally and semantically conforming document that
requires an extension is therefore reported as unsupported. Extension code is never discovered,
downloaded, installed, or executed during validation.
judgment-pack MCP soruları
judgment-pack MCP'yi Claude Code'a nasıl eklerim?
Terminalinizde claude mcp add judgment-pack-runtime -- docker run -i --rm ghcr.io/judgment-pack/judgment-pack:0.46.0 komutunu çalıştırın. Her projede kullanılabilir olması için --scope user ekleyin.
judgment-pack MCP'yi Cursor'a nasıl eklerim?
~/.cursor/mcp.json dosyasını açın ve yukarıdaki yükleme bölümünde gösterilen Cursor yapılandırmasını kullanarak sunucuyu mcpServers altına ekleyin.
judgment-pack runtime ne işe yarar?
Belgeleri doğrulamak ve uyumluluk testi gerçekleştirmek için kullanılan, Judgment Pack Specification (JPS) için satıcıdan bağımsız bir referans çalışma zamanı görevi görür.
Bir AI agent bu aracı kullanabilir mi?
Evet, mcp komutu bir agent'ın stdio üzerinden tool call kullanarak belge doğrulaması gibi çevrimdışı işlemleri gerçekleştirmesine olanak tanır.
Değerlendirici (evaluator) kararlı mı?
experimental namespace altındaki araçlar kararsız kabul edilir; değişebilir veya uyumluluk sözü verilmeden kaldırılabilir.