Anasemble v0.1.0-rc.3: Generic evidence envelopes

Anasemble v0.1.0-rc.3 publishes replayable traces, content-addressed snapshots and diffs, contract versions, and signed verification certificates as versioned crates so downstream reconstructors can check those artefacts independently.

Highlights

• Protocol crates: anasemble-trace, anasemble-semantic, anasemble-contract, and anasemble-verification join anasemble-core, anasemble-evidence, and anasemble-events.
• Independent checking: Trace, snapshot, diff, contract, and report digests can be rebuilt without trusting the stored digest field.
• Fail-closed bounds: Replay denies unmocked side effects, budget exhaustion is a refusal, and proven claims require evidence roots.
• Compatible recovery CLI: Existing fragment files, JSON certificate digests, and the anasemble command remain unchanged beside the new crates.
• Registry packages: The seven protocol crates and the anasemble CLI package publish to crates.io from this tag.

Installation

Add the protocol crates from crates.io, or build the CLI from the signed source tag:

cargo add anasemble-semantic@0.1.0-rc.3
rustup show
cargo fetch --locked
cargo build --release --locked
target/release/anasemble install /opt/anasemble-0.1.0-rc.3

Compatibility and claims

This candidate supports only rows marked Supported in Compatibility. The protocol crates cover generic evidence, traces, snapshots, diffs, contracts, and verification certificates; they do not reconstruct arbitrary software, replace ordinary backups, or prove a cross-backend distributed transaction. Independent reproduction and external security review are optional post-release assurance.

Source code and project-authored assets are available under Apache License 2.0. The licence does not grant trademark rights in the Anasemble name or Semantic Fit identity. See the detailed changelog, security policy, support policy, release artifacts and P4 evidence.

Anasemble v0.1.0-rc.2: Generic evidence envelopes

Anasemble v0.1.0-rc.2 publishes the generic EvidenceEnvelopeV1 protocol as versioned crates so downstream reconstructors can verify signed evidence without depending on the recovery CLI.

Highlights

• Protocol crates: anasemble-core, anasemble-evidence, and anasemble-events expose canonical digests, signed envelopes, revocation, replay windows, and gap-closed reconstruction events.
• Compatible recovery CLI: Existing fragment files, JSON certificate digests, and the anasemble command remain unchanged beside the extracted crates.
• Independent admission: Consumers verify Ed25519 signatures, XChaCha20-Poly1305 seals, tenant binding, and size limits before they persist anything.
• Registry packages: The three protocol crates and the anasemble CLI package publish to crates.io from this tag.

Installation

Add the protocol crates from crates.io, or build the CLI from the signed source tag:

cargo add anasemble-evidence@0.1.0-rc.2
rustup show
cargo fetch --locked
cargo build --release --locked
target/release/anasemble install /opt/anasemble-0.1.0-rc.2

Compatibility and claims

This candidate supports only rows marked Supported in Compatibility. The protocol crates cover generic evidence and reconstruction events; they do not reconstruct arbitrary software, replace ordinary backups, or prove a cross-backend distributed transaction. Independent reproduction and external security review are optional post-release assurance.

Source code and project-authored assets are available under Apache License 2.0. The licence does not grant trademark rights in the Anasemble name or Semantic Fit identity. See the detailed changelog, security policy, support policy, release artifacts and P4 evidence.

Anasemble v0.1.0-rc.1: Evidence-bound recovery

Anasemble v0.1.0-rc.1 provides a production-shaped, restart-safe path from independently retained semantic evidence to bounded, operator-approved recovery for its explicitly supported service and state profiles.

Highlights

• Durable operations: Recovery jobs survive interruption through atomic records, leases, bounded retries, queue backpressure, audit chains and derived metrics.
• State recovery: Filesystem, PostgreSQL 18, S3-compatible object storage and Redis Streams restore with verified rollback evidence; the exact AWS profile uses authenticated TLS and HTTPS.
• Isolated activation: Plan-bound OCI artifacts run under supported zero-egress Docker isolation, while the exact EKS 1.36 profile enforces strict VPC CNI network policy before activation.
• Operator lifecycle: Rust-native installation, configuration migration, exact uninstallation, diagnostics, redacted support bundles and a disaster runbook cover the supported macOS and exact Amazon Linux profiles.
• Retained evidence: Local CI executes destructive state and activation drills, a 128-job sustained scheduler test, dependency checks and the complete regression suite.
• Integrated evaluation: Public commands prepare state evidence, reconstruct and activate through OCI and Kubernetes, then accept or restore the prior deployment plus PostgreSQL, S3 and Redis state.

Installation

Install Rust 1.97.0 through rustup, fetch the locked dependencies, build from the signed source tag and install to a new owned prefix:

rustup show
cargo fetch --locked
cargo build --release --locked
target/release/anasemble install /opt/anasemble-0.1.0-rc.1

Compatibility and claims

This candidate supports only rows marked Supported in Compatibility. The supported AWS profiles are restricted to the exact Amazon Linux, RDS, S3, ElastiCache, EKS and VPC CNI versions retained in that contract; generic Linux, Kubernetes, S3-compatible and remote-state combinations remain experimental. Anasemble does not reconstruct arbitrary software, generate a live HTTP server, replace ordinary backups, or prove a cross-backend distributed transaction. Independent reproduction and external security review are optional post-release assurance.

Source code and project-authored assets are available under Apache License 2.0. The licence does not grant trademark rights in the Anasemble name or Semantic Fit identity. See the detailed changelog, security policy, support policy, release artifacts and P4 evidence.