Judgment Boundary
A Responsibility Layer for Automated Systems
"This is not a system that manages AI. This is infrastructure that makes judgment unavoidable."
What This Is
Judgment Boundary is a pre-action governance gate that sits between model output and organizational action. It enforces responsibility checkpoints before any automated system can act.
Purpose: Document and enforce the boundary between what an organization will and will not automate with AI.
What This Is NOT
- ❌ An AI model or LLM platform
- ❌ A decision automation system
- ❌ A training or fine-tuning framework
- ❌ A machine learning system
What This DOES
- ✅ Declares execution readiness (STOP / HOLD / ALLOW / INDET)
- ✅ Records organizational boundaries as immutable attestations
- ✅ Generates regulatory evidence (EU AI Act Article 14 compliance)
- ✅ Maintains external judgment state (no model modification)
Where This Applies
Regulatory Context:
- EU AI Act Article 14 (Human Oversight Requirements)
- GDPR Article 22 (Automated Decision-Making)
- High-risk AI systems requiring accountability checkpoints
Technical Context:
- Pre-action governance gates
- Responsibility documentation
- Audit trail generation
Documentation
- System Specification: Whitepaper v1.0
- EU AI Act Reference: Architecture Documentation
- Live Demonstrations: Regulatory Demos
Installation
pip install judgment-boundary
Or via Docker:
docker pull judgment-boundary:latest
Quick Start
from judgment_boundary import JudgmentRuntime
runtime = JudgmentRuntime(
memory_store_path="./judgment_memory.jsonl",
enable_organizational_memory=True
)
result = runtime.process(
prompt="What is the CEO salary?",
model_output="The CEO salary is $500,000.",
rag_sources=None,
domain_tag="hr"
)
print(f"Decision: {result.decision}") # STOP
print(f"Reason: {result.reason}") # EVIDENCE_MISSING
Core Architecture
[ Organizational Action ]
↑
[ Judgment Boundary Layer ] ← Responsibility checkpoint
↑
[ Model Output ]
Key Properties:
- External state only (no model weights modified)
- Model-agnostic (works with any LLM/automation)
- Deterministic and reproducible
- Verifiable and auditable
Demos
Regulatory Compliance:
Live Execution:
License
MIT
Status
This is a public baseline release documenting a working system. For technical specification, see Whitepaper v1.0.
Metadata
Release files for judgment-boundary 0.4.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 | Provenance | Actions |
|---|---|---|---|---|
| judgment_boundary-0.4.3.tar.gz | 46.6 kB | Without provenance | Details for judgment_boundary-0.4.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| judgment_boundary-0.4.3-py3-none-any.whl | Python 3 | none | any | Details for judgment_boundary-0.4.3-py3-none-any.whl |
Total release size: 104.4 kB
Release files / judgment_boundary-0.4.3.tar.gz
| Download URL | judgment_boundary-0.4.3.tar.gz |
|---|---|
| Size | 46.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8b4c17d6b71f45a373803d99ab9ad8418271057ee0ac84e9eb85876bf64d619f
|
|
BLAKE2b-256 checksum How to use checksums |
8e0bb52a1a9c68ad13e5097f4f2c9e287e15ae59f9a7c17f3f347440d7377fac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / judgment_boundary-0.4.3-py3-none-any.whl
| Download URL | judgment_boundary-0.4.3-py3-none-any.whl |
|---|---|
| Size | 57.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a11015b691eb3f95ed970423e23863849b0732e69803fc09297d9dce3c6e9677
|
|
BLAKE2b-256 checksum How to use checksums |
ef091d3d733a9267c99e55faacd3e9012c87300d1a525fe3829378babd458fed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for judgment-boundary 0.4.3
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.