SE verification profile for judicial accountable record systems.
SE Verification for Judicial Record checks whether a judicial accountable record system preserves the structural distinctions required for durable inspection, contestation, audit, and continued use under disagreement.
The verifier operates on exported judicial record bundles and checks:
- record structure
- reference integrity
- layer separation
- prohibited inferences
- traceability to Accountable Record and Structural Explainability constraints
The verifier does not determine legal correctness, binding authority, or judicial legitimacy.
The purpose of SE Verification for Judicial Record is to verify whether judicial record systems preserve SE-relevant distinctions.
The verifier defines checks for:
- record identity and reference integrity
- judicial record type constraints
- citation and dependency separation
- later treatment and historical record separation
- authority and correctness separation
- interpretation and explanation non-mutation
- judicial-specific prohibited category collapse
- verification report traceability
The verifier helps protect judicial record systems from a specific failure mode:
- Using convenient legal data fields in ways that collapse citation, dependency, authority, interpretation, treatment, validity, and proof.
Current versions are pre-v1. The contract is being co-developed with its implementations and verifiers; dependencies track main during this phase. Versioned releases will follow once the contract stabilizes.
v1 will commit to:
- the verification profile shape
- check traceability to AR, SE, or explicit engineering requirements
- separation of core AR checks from judicial-specific checks
- verification report structure
v1 does not claim completeness over all possible judicial record failures.
Extension policy applies once v1 stabilizes. Until then, the contract is in active development and changes occur on main. Extension is permitted under a new version of the record model or through declared profile extensions.
Any extension MUST:
- preserve conformance with Structural Explainability
- preserve the Accountable Record verification model
- identify whether checks are formal-result checks, specification-derived checks, or engineering checks
- provide traceability from each check to the constraint it implements
- avoid adding legal correctness, legal advice, authority, legitimacy, or enforcement determinations
- be explicit, justified, and testable
This verifier defines:
- judicial record verification rules
- judicial-specific failure-mode checks
- verification reports
- source traces for failed checks
- separation checks for citation, dependency, treatment, interpretation, explanation, authority, and correctness
- engineering checks required for export-bundle integrity
This verifier does NOT define:
- legal advice
- legal correctness
- binding authority
- judicial legitimacy
- judicial record ingestion
- replacements for court record publication or legal research platforms
- judicial record implementation
- source data hosting
- This verifier checks systems that implement the Accountable Record contract.
- This verifier specializes SE verification for Judicial Record exports.
- This verifier may be run against
judicial-recordor compatible third-party judicial accountable record systems. - This verifier does not replace Judicial Record or its source systems; it checks exported artifacts.
- Failed checks should trace to Accountable Record constraints, SE specifications, formal results where applicable, or declared engineering requirements.
SE Verification for Judicial Record verifies structural discipline, not legal outcome correctness.
A passing verification report means the exported judicial record system preserved declared distinctions and avoided checked category collapses. It does not mean the legal reasoning was correct, the authority was binding, or the judicial outcome was legitimate.
This verifier exists so that judicial accountable record systems can remain inspectable across disagreement, reinterpretation, and time.
- README.md - Project overview
- VERIFICATION_RULES.md - Verification rules
- FAILURE_MODES.md - Judicial record failure modes
- SE_ALIGNMENT.md - Alignment to SE constraints
- ANNOTATIONS.md - Annotation standards
- LICENSE - Licensing terms
- CITATION.cff - Citation metadata
- CHANGELOG.md - Version history
- data/verification - Verification fixtures and rules
- data/reports - Example verification reports
Show command reference
Open a machine terminal where you want the project:
git clone https://github.com/structural-explainability/se-verification-judicial-record
cd se-verification-judicial-record
code .uv self update
uv python pin 3.15
uv sync --extra dev --extra docs --upgrade
# install git hooks once per clone
uvx pre-commit install
# autofix and manual fix issues
git add -A
uvx pre-commit run --all-files
# repeat if changes were made
git add -A
uvx pre-commit run --all-files
# validate Markdown sources and generated specification artifacts
uv run se-validate
# generate machine-readable specification artifacts under data/spec/
uv run se-ref-export
# check that generated data/spec/ artifacts are current
uv run se-ref-export --check
# validate reference artifacts and registry consistency
uv run se-ref-validate
# run strict validation, including all standard source and export checks
uv run se-validate --strict
# run verification tests
uv run se-verify data/fixtures/bundles/valid/empty-bundle.json
uv run se-verify data/fixtures/bundles/valid/empty-bundle.json
uv run se-verify data/fixtures/bundles/valid/minimal-judicial-record-bundle.json
uv run se-verify data/fixtures/bundles/invalid/citation-dependency-collapse.json
# do chores
uv run python -m pyright
uv run python -m pytest
# save progress
git add -A
git commit -m "update"
git push -u origin main