# Judgment Pack Specification (JPS)

> Judgment Pack (JPS) is an open, vendor-neutral specification for making AI judgment explicit, testable, portable, and governable separately from any runtime.

- Current draft: `0.2.0-draft`
- Status: research preview; no compatibility, production-readiness, certification, truth, safety, or authorization claim
- License: Apache-2.0
- Canonical site: https://judgmentpack.org/

This experimental file is a navigation aid, not a crawler-control policy or a source of normative
text. `robots.txt` controls crawling. The versioned Core prose and named artifacts below control JPS
conformance.

## Normative specification and artifacts

- [JPS Core 0.2.0-draft](https://judgmentpack.org/spec/0.2.0-draft/): normative prose for the four named conformance classes
- [Core JSON Schema](https://judgmentpack.org/schema/0.2.0-draft/judgment-pack-core.schema.json): normative structural schema
- [Document-conformance corpus](https://judgmentpack.org/conformance/): carrier, structural, and semantic cases
- [Evaluation corpus](https://judgmentpack.org/conformance/evaluation/): normative only for evaluator conformance
- [Versioning policy](https://judgmentpack.org/project/versioning/)

## Explanations and direct answers

- [Why Judgment Pack?](https://judgmentpack.org/why/)
- [Field guide](https://judgmentpack.org/field-guide/)
- [Frequently asked questions](https://judgmentpack.org/faq/)
- [How Judgment Pack compares](https://judgmentpack.org/concepts/comparison/)
- [Synthetic examples](https://judgmentpack.org/examples/)

## Project boundaries and participation

- [Implementations and claim boundaries](https://judgmentpack.org/implementations/)
- [Governance](https://judgmentpack.org/project/governance/)
- [Proposals (RFCs)](https://judgmentpack.org/rfcs/): not normative unless accepted and landed in a release
- [Specification repository](https://github.com/Judgment-Pack/judgment-pack-spec)
- [Public repositories](https://github.com/Judgment-Pack)
- [Community Slack](https://join.slack.com/t/judgment-pack/shared_invite/zt-44qrd47ok-o_~Vk3BFDzsN~EGAPkeQBw)

## Interpretation boundary

A conforming document or evaluator result never establishes that evidence is true, that a pack is
authorized, that an outcome is safe or fit, or that an action may be taken. The specification,
reference runtime, demo, gateway, and research repositories have separate authority and release
boundaries.