JACKAL Omarchy Edition 2.6.3

JACKAL Omarchy Edition 2.6.3

This release keeps the requirements-complete SPARK assurance-policy component,
exhaustive JavaScript conformance, deterministic release reproduction, and
public pinned assurance automation from 2.6.2, while correcting the manual-copy
migration procedure discovered during live deployment. Operator backups now
live outside Omarchy's plugin catalog, preventing an old manifest with the same
permanent plugin ID from blocking the replacement Git clone. The mathematical
JACKAL runtime remains a separate, pinned dependency with its own release epoch
and assurance model.

Highlights

• Professional graphite, steel, white, and crimson evidence surface.
• Stable, pixel-aligned scrolling plane without green status semantics or
  animated interference behind text.
• Fresh function probes separated from installed capability and runtime
  integrity.
• Bundled portable operator CLI; no fixed username, checkout, or runtime epoch.
• Optional transparent MCP ledger with concurrent-write protection, bounded
  retention, outward decimal rendering, and retained formal receipts.
• Verification router that keeps operator expectations structurally separate
  from the artifact under review.
• Assurance-aware graph and linked-workspace previews whose pixels are
  explicitly non-evidentiary.
• Component-scoped SPARK Platinum proof for the pure finite assurance-policy
  kernel, with fail-closed rejection of unproved or justified checks.
• Exhaustive SPARK-to-JavaScript policy vectors and explicit bridge residuals.
• Bidirectional machine-readable requirements and traceability enforcement.
• Byte-identical clean-checkout release reproduction after removing volatile
  POSIX PAX metadata.
• Exact local commit archive, deterministic independent repository creation,
  and pre-execution Git tree-identity equality in both reproduction trees.
• No remote, fetched, or shared-worktree source executes in release
  reproduction.
• Pinned GitHub assurance automation and standards-facing proof documentation.
• Proof-tool installations isolated from the repository checkout in hosted CI.
• Fail-closed doctor behavior when any canonical function probe is undeclared.
• Catalog-safe migration from a manually copied plugin, with a regression test
  that rejects duplicate-ID backup guidance.

Compatibility

• Omarchy Quattro shell plugin interface.
• Plugin ID: khephri.jackal.
• JACKAL runtime: discovered dynamically through the installed Codex plugin and
  runtime locator.
• Python 3.10 or newer.

Verification boundary

The release proves the requirements allocated to Jackal_Assurance_Policy and
tests presentation, parsing, routing, refusal behavior, operator diagnostics,
ledger transparency, concurrency, outward rendering, repository policy,
release reproduction, and live Omarchy validation on the development host. The
complete mixed-language plugin is not claimed as Platinum. These checks do not
establish universal correctness, security certification, mathematical
soundness of every JACKAL lane, flight qualification, or organizational
endorsement.

Install

omarchy plugin add https://github.com/AnubisQuantumCipher/jackal-omarchy.git --enable

Review the source and exact release commit before installation. Omarchy plugins
run unsandboxed as the current user.

Remove

omarchy plugin remove khephri.jackal

Removal does not delete JACKAL runtimes, operator expectations, ledger rows, or
retained receipts.

JACKAL Omarchy Edition 2.6.2

JACKAL Omarchy Edition 2.6.2

This release keeps the requirements-complete SPARK assurance-policy component,
exhaustive JavaScript conformance, deterministic release reproduction, and
public pinned assurance automation from 2.6.0, while tightening the clean-
checkout reproduction harness to eliminate fetched-source execution. It now
materializes two independent repositories from the validated local commit and
requires exact Git tree-identity equality before either build. The mathematical
JACKAL runtime remains a separate, pinned dependency with its own release epoch
and assurance model.

Highlights

• Professional graphite, steel, white, and crimson evidence surface.
• Stable, pixel-aligned scrolling plane without green status semantics or
  animated interference behind text.
• Fresh function probes separated from installed capability and runtime
  integrity.
• Bundled portable operator CLI; no fixed username, checkout, or runtime epoch.
• Optional transparent MCP ledger with concurrent-write protection, bounded
  retention, outward decimal rendering, and retained formal receipts.
• Verification router that keeps operator expectations structurally separate
  from the artifact under review.
• Assurance-aware graph and linked-workspace previews whose pixels are
  explicitly non-evidentiary.
• Component-scoped SPARK Platinum proof for the pure finite assurance-policy
  kernel, with fail-closed rejection of unproved or justified checks.
• Exhaustive SPARK-to-JavaScript policy vectors and explicit bridge residuals.
• Bidirectional machine-readable requirements and traceability enforcement.
• Byte-identical clean-checkout release reproduction after removing volatile
  POSIX PAX metadata.
• Exact local commit archive, deterministic independent repository creation,
  and pre-execution Git tree-identity equality in both reproduction trees.
• No remote, fetched, or shared-worktree source executes in release
  reproduction.
• Pinned GitHub assurance automation and standards-facing proof documentation.
• Proof-tool installations isolated from the repository checkout in hosted CI.
• Fail-closed doctor behavior when any canonical function probe is undeclared.

Compatibility

• Omarchy Quattro shell plugin interface.
• Plugin ID: khephri.jackal.
• JACKAL runtime: discovered dynamically through the installed Codex plugin and
  runtime locator.
• Python 3.10 or newer.

Verification boundary

The release proves the requirements allocated to Jackal_Assurance_Policy and
tests presentation, parsing, routing, refusal behavior, operator diagnostics,
ledger transparency, concurrency, outward rendering, repository policy,
release reproduction, and live Omarchy validation on the development host. The
complete mixed-language plugin is not claimed as Platinum. These checks do not
establish universal correctness, security certification, mathematical
soundness of every JACKAL lane, flight qualification, or organizational
endorsement.

Install

omarchy plugin add https://github.com/AnubisQuantumCipher/jackal-omarchy.git --enable

Review the source and exact release commit before installation. Omarchy plugins
run unsandboxed as the current user.

Remove

omarchy plugin remove khephri.jackal

Removal does not delete JACKAL runtimes, operator expectations, ledger rows, or
retained receipts.

JACKAL Omarchy Edition 2.6.1

JACKAL Omarchy Edition 2.6.1

This release keeps the requirements-complete SPARK assurance-policy component,
exhaustive JavaScript conformance, deterministic release reproduction, and
public pinned assurance automation from 2.6.0, while tightening the clean-
checkout reproduction harness to bind the exact full commit before any fetched
source executes. The mathematical JACKAL runtime remains a separate, pinned
dependency with its own release epoch and assurance model.

Highlights

• Professional graphite, steel, white, and crimson evidence surface.
• Stable, pixel-aligned scrolling plane without green status semantics or
  animated interference behind text.
• Fresh function probes separated from installed capability and runtime
  integrity.
• Bundled portable operator CLI; no fixed username, checkout, or runtime epoch.
• Optional transparent MCP ledger with concurrent-write protection, bounded
  retention, outward decimal rendering, and retained formal receipts.
• Verification router that keeps operator expectations structurally separate
  from the artifact under review.
• Assurance-aware graph and linked-workspace previews whose pixels are
  explicitly non-evidentiary.
• Component-scoped SPARK Platinum proof for the pure finite assurance-policy
  kernel, with fail-closed rejection of unproved or justified checks.
• Exhaustive SPARK-to-JavaScript policy vectors and explicit bridge residuals.
• Bidirectional machine-readable requirements and traceability enforcement.
• Byte-identical clean-checkout release reproduction after removing volatile
  POSIX PAX metadata.
• Exact full-commit fetch, detached checkout, and pre-execution identity
  readback in both independent reproduction trees.
• Pinned GitHub assurance automation and standards-facing proof documentation.
• Proof-tool installations isolated from the repository checkout in hosted CI.
• Fail-closed doctor behavior when any canonical function probe is undeclared.

Compatibility

• Omarchy Quattro shell plugin interface.
• Plugin ID: khephri.jackal.
• JACKAL runtime: discovered dynamically through the installed Codex plugin and
  runtime locator.
• Python 3.10 or newer.

Verification boundary

The release proves the requirements allocated to Jackal_Assurance_Policy and
tests presentation, parsing, routing, refusal behavior, operator diagnostics,
ledger transparency, concurrency, outward rendering, repository policy,
release reproduction, and live Omarchy validation on the development host. The
complete mixed-language plugin is not claimed as Platinum. These checks do not
establish universal correctness, security certification, mathematical
soundness of every JACKAL lane, flight qualification, or organizational
endorsement.

Install

omarchy plugin add https://github.com/AnubisQuantumCipher/jackal-omarchy.git --enable

Review the source and exact release commit before installation. Omarchy plugins
run unsandboxed as the current user.

Remove

omarchy plugin remove khephri.jackal

Removal does not delete JACKAL runtimes, operator expectations, ledger rows, or
retained receipts.

JACKAL Omarchy Edition 2.6.0

JACKAL Omarchy Edition 2.6.0

This release adds a requirements-complete SPARK assurance-policy component,
exhaustive conformance to the shipped JavaScript model, deterministic release
reproduction, and public pinned assurance automation. The mathematical JACKAL
runtime remains a separate, pinned dependency with its own release epoch and
assurance model.

Highlights

• Professional graphite, steel, white, and crimson evidence surface.
• Stable, pixel-aligned scrolling plane without green status semantics or
  animated interference behind text.
• Fresh function probes separated from installed capability and runtime
  integrity.
• Bundled portable operator CLI; no fixed username, checkout, or runtime epoch.
• Optional transparent MCP ledger with concurrent-write protection, bounded
  retention, outward decimal rendering, and retained formal receipts.
• Verification router that keeps operator expectations structurally separate
  from the artifact under review.
• Assurance-aware graph and linked-workspace previews whose pixels are
  explicitly non-evidentiary.
• Component-scoped SPARK Platinum proof for the pure finite assurance-policy
  kernel, with fail-closed rejection of unproved or justified checks.
• Exhaustive SPARK-to-JavaScript policy vectors and explicit bridge residuals.
• Bidirectional machine-readable requirements and traceability enforcement.
• Byte-identical clean-checkout release reproduction after removing volatile
  POSIX PAX metadata.
• Pinned GitHub assurance automation and standards-facing proof documentation.
• Proof-tool installations isolated from the repository checkout in hosted CI.
• Fail-closed doctor behavior when any canonical function probe is undeclared.

Compatibility

• Omarchy Quattro shell plugin interface.
• Plugin ID: khephri.jackal.
• JACKAL runtime: discovered dynamically through the installed Codex plugin and
  runtime locator.
• Python 3.10 or newer.

Verification boundary

The release proves the requirements allocated to Jackal_Assurance_Policy and
tests presentation, parsing, routing, refusal behavior, operator diagnostics,
ledger transparency, concurrency, outward rendering, repository policy,
release reproduction, and live Omarchy validation on the development host. The
complete mixed-language plugin is not claimed as Platinum. These checks do not
establish universal correctness, security certification, mathematical
soundness of every JACKAL lane, flight qualification, or organizational
endorsement.

Install

omarchy plugin add https://github.com/AnubisQuantumCipher/jackal-omarchy.git --enable

Review the source and exact release commit before installation. Omarchy plugins
run unsandboxed as the current user.

Remove

omarchy plugin remove khephri.jackal

Removal does not delete JACKAL runtimes, operator expectations, ledger rows, or
retained receipts.

JACKAL + THOTH 2.5.0

JACKAL Omarchy Edition 2.5.0

This is the first standalone open-source release of the JACKAL Omarchy desktop
integration. The mathematical JACKAL runtime remains a separate, pinned
dependency and retains its own release epoch and assurance model.

Highlights

• Professional graphite, steel, white, and crimson evidence surface.
• Stable, pixel-aligned scrolling plane without green status semantics or
  animated interference behind text.
• Fresh function probes separated from installed capability and runtime
  integrity.
• Bundled portable operator CLI; no fixed username, checkout, or runtime epoch.
• Optional transparent MCP ledger with concurrent-write protection, bounded
  retention, outward decimal rendering, and retained formal receipts.
• Verification router that keeps operator expectations structurally separate
  from the artifact under review.
• Assurance-aware graph and linked-workspace previews whose pixels are
  explicitly non-evidentiary.
• Detailed open-source documentation, threat model, engineering pilot guide,
  contribution policy, deterministic packaging, and GitHub automation.

Compatibility

• Omarchy Quattro shell plugin interface.
• Plugin ID: khephri.jackal.
• JACKAL runtime: discovered dynamically through the installed Codex plugin and
  runtime locator.
• Python 3.10 or newer.

Verification boundary

The release tests presentation, parsing, routing, refusal behavior, operator
diagnostics, ledger transparency, concurrency, outward rendering, repository
policy, and live Omarchy validation on the development host. These checks do not
establish universal correctness, security certification, mathematical soundness
of every JACKAL lane, flight qualification, or organizational endorsement.

Install

omarchy plugin add https://github.com/AnubisQuantumCipher/jackal-omarchy.git --enable

Review the source and exact release commit before installation. Omarchy plugins
run unsandboxed as the current user.

Remove

omarchy plugin remove khephri.jackal

Removal does not delete JACKAL runtimes, operator expectations, ledger rows, or
retained receipts.