Aleph Skill v2.1.1
Aleph 2.1.1 is a focused bundled-component update. It moves the internal D Research runtime from 3.2.0 to 3.2.1 while keeping Aleph workspace schema_version and formula_version at 2.0.0. Hosts still install and load one Aleph skill; D Research remains available internally as aleph-component://d-research.
Highlights
- Updates the byte-locked D Research component to
3.2.1. - Adds production-capable semantic retrieval through optional
sentence-transformers, with deterministiclocal-hashingfallback when that extra is unavailable. - Improves BibTeX and CSL export for articles, books, proceedings, structured personal names, and literal corporate authors while failing closed on conflicting identities.
- Adds optional local
langdetectsupport and preserves the dependency-free trigram language detector. - Keeps the D Research ledger, research gateway, sealed roleplay boundary, external HMAC refusal, and assurance rules unchanged.
- Forces optional Hugging Face/Transformers model resolution into cache-only mode unless the caller explicitly grants network access.
No new mandatory dependency is introduced. Aleph does not bundle or auto-install sentence-transformers, langdetect, Node.js, Playwright, Chromium, browser binaries, credentials, or node_modules.
Compatibility
- Aleph package and validator versions advance to
2.1.1. - Workspace
schema_versionremains2.0.0. - Numerical
formula_versionremains2.0.0. - D Research workspaces require no schema migration.
- Previously finalized Aleph workspaces must be revalidated because validation, quality, finalization, and component-binding receipts are version-bound.
- The seven Aleph domain packs remain
experimental; this release does not authorize probability claims.
Upgrade from v2.1.0
Install or extract v2.1.1 into a clean skill directory, keep the v2.1.0 package and workspace as rollback copies, and resolve all commands from the installed Aleph root.
Bash preflight
export ALEPH_SKILL_ROOT="$(cd "/absolute/path/to/aleph-skill" && pwd -P)"
export ALEPH_WORKSPACE="/absolute/path/to/workspace"
python "$ALEPH_SKILL_ROOT/scripts/preflight.py" --json
python "$ALEPH_SKILL_ROOT/scripts/research_gateway.py" research:preflight --jsonPowerShell preflight
$env:ALEPH_SKILL_ROOT = (Resolve-Path 'C:\absolute\path\to\aleph-skill').Path
$env:ALEPH_WORKSPACE = (Resolve-Path 'C:\absolute\path\to\workspace').Path
python "$env:ALEPH_SKILL_ROOT\scripts\preflight.py" --json
python "$env:ALEPH_SKILL_ROOT\scripts\research_gateway.py" research:preflight --jsonRequire package preflight status: pass and D Research status: available, source: bundled, package_version: 3.2.1, path: aleph-component://d-research, and lock_ok: true.
For a finalized workspace that contains D Research 3.2.0 component-binding receipts, use the non-mutating check first, then create a sibling workspace with refreshed 3.2.1 binding. The source workspace is not modified, and the destination <workspace>-bundled-bind must not already exist.
Bash component rebind
python "$ALEPH_SKILL_ROOT/scripts/migrate_workspace.py" --source "$ALEPH_WORKSPACE" --bind-bundled-d-research --check --json
python "$ALEPH_SKILL_ROOT/scripts/migrate_workspace.py" --source "$ALEPH_WORKSPACE" --bind-bundled-d-research --json
export ALEPH_TARGET_WORKSPACE="${ALEPH_WORKSPACE}-bundled-bind"PowerShell component rebind
python "$env:ALEPH_SKILL_ROOT\scripts\migrate_workspace.py" --source "$env:ALEPH_WORKSPACE" --bind-bundled-d-research --check --json
python "$env:ALEPH_SKILL_ROOT\scripts\migrate_workspace.py" --source "$env:ALEPH_WORKSPACE" --bind-bundled-d-research --json
$env:ALEPH_TARGET_WORKSPACE = $env:ALEPH_WORKSPACE + '-bundled-bind'The rebinder verifies retained research ledgers with both Aleph and the locked upstream canonicalizer, refreshes portable component identity, and invalidates stale finalization and assurance receipts. If the ledger has an HMAC sidecar, provide D_RESEARCH_LEDGER_KEY through the environment only. Do not put secrets in the workspace or command line.
Re-run every affected import, compile/run/replay, sensitivity, hindcast, and report step against the sibling, then finalize and require clean validation. Workspaces that never imported D Research do not need component rebinding, but finalized copies still need new 2.1.1 receipts; set ALEPH_TARGET_WORKSPACE to a separate non-overwriting working copy before running the lifecycle commands below.
python "$ALEPH_SKILL_ROOT/scripts/validate_simulation_artifacts.py" --workspace "$ALEPH_TARGET_WORKSPACE" --mode draft --write-report --json
python "$ALEPH_SKILL_ROOT/scripts/render_simulation_report.py" --workspace "$ALEPH_TARGET_WORKSPACE"
python "$ALEPH_SKILL_ROOT/scripts/finalize_simulation.py" --workspace "$ALEPH_TARGET_WORKSPACE" --json
python "$ALEPH_SKILL_ROOT/scripts/validate_simulation_artifacts.py" --workspace "$ALEPH_TARGET_WORKSPACE" --mode final --require-report --write-report --json
python "$ALEPH_SKILL_ROOT/scripts/evaluate_simulation_quality.py" --workspace "$ALEPH_TARGET_WORKSPACE" --threshold 90 --enforce --jsonRollback to v2.1.0
Restore the verified v2.1.0 skill package together with the untouched v2.1.0 workspace. Aleph v2.1.0 contains D Research 3.2.0 and cannot validate receipts bound to the 3.2.1 component lock. There is no automatic reverse migration; do not hand-edit component paths, hashes, or signed receipts.
Provenance and release scope
The D Research snapshot is derived from the upstream verified annotated tag v3.2.1:
- Tag object:
4f797f0cb0f75539edfc9bc9332ca4dd041e881c - Commit:
dc07d4902361ddf15ff0dd093faa0784b2fd47ab - Git tree:
4943fec2d4fa6bda1f4beecfd9177a630af0ab8b - Canonical
git archiveSHA-256:e91837e6d2d38cde4f055f54d382e58c7b2094220b87e77dff695f92a63cdd71 - Bundled component-tree SHA-256:
0276b3f4b6230b65e75c664edd642b9b2b7ce30e534a88a8328899b3d6fc7edd - Boundary: 730 upstream tracked files, 529 exact repository-only CI/release/dogfood-evidence exclusions, and 201 locked runtime files
- Upstream package boundary: 199 paths
Aleph release CI independently fetches the pinned tag and verifies its tag object, peeled commit, Git tree, reproducible archive, exact exclusion recipe, package manifest, and every bundled byte. It then runs the cross-platform Python and Node matrices, no-browser acceptance, real Chromium gateway smoke, strict static checks, lifecycle/replay/adversarial gates, and two byte-identical release builds before publication.
Per maintainer direction, no new model dogfood or manual multi-model forward-test campaign is claimed for this dependency patch. This omission does not skip deterministic package, security, provenance, browser, lifecycle, or reproducibility gates.
Verify the release
Download aleph-skill-v2.1.1.zip, distribution-manifest.json, and SHA256SUMS.txt into one directory:
sha256sum -c SHA256SUMS.txt
gh attestation verify aleph-skill-v2.1.1.zip \
--repo d-init-d/aleph-skill \
--signer-workflow d-init-d/aleph-skill/.github/workflows/release.yml \
--source-ref refs/tags/v2.1.1
for asset in distribution-manifest.json SHA256SUMS.txt; do
gh attestation verify "$asset" \
--repo d-init-d/aleph-skill \
--signer-workflow d-init-d/aleph-skill/.github/workflows/release.yml \
--source-ref refs/tags/v2.1.1
doneThe build-provenance records are stored by GitHub's attestation service rather than attached as separate release files.
See the full changelog, the Aleph comparison, and the upstream D Research comparison for the complete change set.