Nahuali v0.8.0-beta.0

Nahuali v0.8.0-beta.0 is a prerelease of the local trust layer for agent memory.
Every recall can carry its evidence and a deterministic verdict, and the ledger
can prove whether its recorded history was rewritten.

Why upgrade

This release makes the product's original promise usable without external
services: memory can be recorded, inspected, recalled with evidence, and given a
deterministic trust verdict from one local installation.

New

• Embedded local storage for the default CLI, MCP, and HTTP workflows. Docker is
  no longer required to try or operate the core memory path.
• A trust-first nahuali explore terminal interface for browsing memory,
  evidence, store health, and ledger integrity.
• nahuali demo, nahuali init, evidence-required recall, self-inspection,
  review queues, trust reports, governed repair, snapshots, and migration tools.
• Official MCP Registry metadata and a multi-architecture MCP container image.

Changed

• Tamper-evident SHA-256 chaining and Ed25519 tip attestation are enabled in
  normal builds. An unchained legacy build now requires an explicit opt-out.
• Strict validation rejects unchained or partially chained ledgers unless the
  caller deliberately selects the legacy-permissive path.
• Self-inspection distinguishes unsupported, stale, contradictory, and malformed
  memory more precisely and reports deduplicated affected-record counts.
• All shipped components now share one product version and one public release
  tag. The earlier 1.0.0-beta.0 and 1.1.0-beta.0 publications were premature
  automation errors and are superseded by this pre-1.0 release.

Breaking changes and migration

• Strict validation now fails closed for unchained ledgers. Use
  --allow-unchained only while migrating a legacy store.
• New records use envelope version 2 and SHA-256 checksums. Existing version 1
  records remain readable and valid; they are not rewritten.
• The former --require-chained opt-in was replaced by the explicit
  --allow-unchained compatibility flag.

Fixed

• Database names that would previously be normalized into a different name are
  rejected with a useful error.
• Configuration precedence is deterministic: command-line flag, environment,
  then built-in default.
• Same-observation multi-value facts are no longer misreported as contradictions.
• Embedded storage uses SurrealDB 3.1.5, which fixes the upstream cold-start
  session race that could intermittently abort a fresh local database.

Security and integrity

• New ledger records use SHA-256 checksums and bind the preceding record hash.
• Install archives require SHA-256 verification and include Sigstore bundles and
  GitHub artifact attestations.
• Signed tip verification detects a fully recomputed ledger suffix that a hash
  chain alone cannot distinguish from a legitimate rewrite.

Beta limits

• No stable 1.0 API guarantee yet.
• No hosted service, accounts, teams, billing, managed sync, or managed uptime.
• Nahuali evaluates evidence and memory health. It does not claim that recalled
  information is objectively true.

Install

curl -fsSL https://raw.githubusercontent.com/Arakiss/nahuali/main/scripts/install.sh | sh
nahuali demo
nahuali explore

To pin this release, set NAHUALI_VERSION=v0.8.0-beta.0 before running the installer.

Verify the release

bash scripts/check-release-assets.sh --tag v0.8.0-beta.0 --require-sbom
bash scripts/verify-release.sh --tag v0.8.0-beta.0

The release contains four platform archives, mandatory SHA-256 checksums,
Sigstore bundles, GitHub artifact attestations, and one CycloneDX SBOM.

Full changelog

See CHANGELOG.md
for the product history. Crate changelogs are technical appendices only.

Upgrade note

Restart your MCP host after upgrading so a long-lived nahuali-mcp process and the CLI do not open the embedded store with different engine versions.