Repository navigation
Tribunal 1.0.2 strengthens local and operator-controlled decision evidence while preserving the v1 CLI, library API and evidence formats.
Changes
- Serialize conditional store publication and preserve governance history under concurrent updates.
- Reject malformed publication conditions, unreadable event projections and incomplete retention metadata before state changes.
- Screen constructed context, validate encrypted inventories and bound secondary artifact readers.
- Handle transient index-lock contention without weakening live/dangling symlink refusal.
- Package only clean, committed release inputs and verify exact source revisions.
- Avoid redundant existing-directory parent traversal.
Runtime and verification
Use current Kujo 1.8.0 for the additionally verified macOS Intel profile: the unchanged tagged source passed 104 verification commands (including the full test suites, release gates and 20 Eval cases) and the tagged archive smoke test. No assertions, budgets or safety checks were weakened. The committed supplemental receipt is linked from the repository README.
The original release reproduction matrix remains pinned to Kujo 1.5.0 source cc2d7dbb59a8dc05f00d629e100932f56f4062f6, with passing Linux x86_64, macOS Intel and macOS arm64 gates. This distinction preserves historical provenance; it does not claim that every 1.8 platform has been certified.
Release source: 567518a2d9d39ff77da52b5fb1fca4546984c197. The release workflow rebuilds the pinned runtime, reruns all release gates, and smoke-tests the reproducible archive. Verify the attached release-archive-receipt.json against the ZIP before installation. Tagged-commit Workcell success and intentional-failure evidence both have verified manifests and complete cleanup.
Install and scope
Use the attached source archive or clone this exact tag. Put the appropriate verified Kujo runtime on PATH or set KUJO_BIN; then run ./bin/tribunal version and ./bin/tribunal doctor --json. Mock mode is offline and credential-free by default. Kennel registry artifacts have independent publication/versioning.
No hosted or regulated deployment certification, independent security-review completion, live-provider certification, or managed signing/notarization is claimed.
Full changelog · Operator guide
Complete publication and deployment receipt · Repository audit record