JACKAL v1.6.0 — Mathematical Evidence Kernel

JACKAL v1.6.0 — Mathematical Evidence Kernel

JACKAL is now a deterministic, offline mathematical evidence kernel: an epistemic claim compiler whose every answer carries its assurance class (exact / checked / estimated / bounded / formal-bounded / model-based) — or a named refusal.

Tool inventory: 33

• 31 legacy v1.5.0 tools, unchanged — names, parameters, return/status meanings, and accepted legacy evidence are mechanically locked by release/compat/v150_floor.json + tools/compat_floor.py --check (additive-only floor; COMPAT_FLOOR_PASS frozen_tools=31 live_tools=33 errors=0).
• 2 new claim-kernel front doors:
  • jackal_claim — compiles a typed claim request into a content-addressed jackal-claim-bundle-v1 evidence graph (15 registered inference rules; multidimensional assurance axes propagated by pointwise meet; consequence-class floors; deterministic rendering — never a bare VERIFIED).
  • jackal_verify_bundle — independent, dependency-light, caller-pinned replay: recomputes every hash, rule application, assurance axis, floor, and rendering; producer-authored statuses/digests are never accepted merely because they are present.

Compatibility

Migrating from a v1.4.2 (10-tool) or v1.5.0 (31-tool) epoch: both surfaces are strict subsets of the 33-tool surface; previously emitted formal receipts keep verifying under their original expected epoch/request. See release/claim/MIGRATION-v1.6.0.md. Hermes callers need a new session after upgrading.

Evidence (local full aggregate, Apple Silicon macOS)

release/tools/run_gates_v160.py on the exact release bytes: GATES: PASS (38 gates) — including lake-build (Lean proof closures), black-box acceptance 200/200, claim hostile matrix 108/108, claim A→B→A tamper gates over 7 trust layers, receipt-semantic mutations 42/42, and claim-package parity 47/47 (all 33 tools exercised from the fresh-extracted package). Full per-gate log: jackal-v1.6.0-evidence.tar.gz (sha256 b568b728e72468b6cc1fb09196add5123f4ce58f47bd751eca51148f4961eb5f).

Hosted CI (scope stated exactly)

The Formal proof identity gate workflow ran green on the exact PR head (5773931, runs 31980005167 / 31980003007) and the exact merge commit (19b763e, run 31980165734): Lean source closures + proof-identity/axiom audits (--proof-only) and the engine-free claim-kernel admission job (mechanical 33-tool lock, compat floor, committed-fixture replay to verified, one semantic tamper refusing node-id-mismatch). Hosted CI does not run the macOS engine or the full 38-gate aggregate; those are local sealed evidence above.

Package

• jackal-v1.6.0-macos-arm64.tar.gz — sha256 0cdacf56bb83d65454330973280cde7da0b9262d6163ccd7efbbbb47bc88e39a, 79,519,523 bytes, two consecutive builds byte-identical (deterministic USTAR + fixed mtimes).
• Apple Silicon macOS only; no cross-platform native execution is claimed.
• Verify: shasum -a 256 -c SHA256SUMS, then inside the extracted package shasum -a 256 -c SHA256SUMS again (packaged checksums), ./jackal-native self-test (104/104).
• JACKAL execution is local/offline after download; no first-call network fetch.

Security / TCB boundary (non-claims preserved)

No source→native formal refinement; no end-to-end formally verified executable; no one-time replay prevention without an external nonce store; no claim that supplied inputs are true in the world; no probabilistic confidence from intervals; no universal soundness outside admitted fragments; composed interval graphs remain bounded; SHA-256 identifies exact bytes only; finite hostile campaigns are strong bounded evidence, not universal theorems.

Install / migrate

GETTING-STARTED.md (install + first commands) · release/claim/MIGRATION-v1.6.0.md (epoch migration) · release/claim/SPEC.md (claim-kernel data model + assurance matrix §4) · PROVENANCE.md (full seal, frozen identities, hosted-CI scope).

The Hermes plugin epoch derived from this exact release is published separately at AnubisQuantumCipher/hermes-jackal-verified; the trust chain is acyclic (core release → package hash → plugin commit).