Skip to content

Logic-Loom v0.2.0

Logic-Loom graduates out of alpha. The headline change is the Failure Memory workspace — a read-only inspection surface for .failure-memory lesson registries, plus an explicit, off-by-default operator mode for recording and compiling them. Everything else in this release is smaller fixes accumulated since v0.1.0-alpha.7.

New: Failure Memory workspace (read-only) + operator mode

Logic-Loom is now a consumer of akms-failure-memory: a project-owned lesson registry (.failure-memory/lessons.json) that records real failures — what broke, where, and why — and resolves them back to an agent working in the affected area. This release adds the product surface on top of the CLI adoption that shipped earlier.

Read-only workspace (/failure-memory/* in the app, /api/failure-memory/* on the sidecar) — inspect, preview, and diagnose one or more configured .failure-memory projects: lesson inventory, compiled route index with graph overlay, per-lesson detail, and a resolve/check preview. The package remains the sole recorder, compiler, and provider; Logic-Loom only reads. This is structural, not a feature flag switched off — the read path calls the package with a literal write_artifacts=False at the call site, so there is no name anywhere in the read-only adapter that could be rebound to enable writing, and a dedicated AST audit fails the build if that ever changes.

Operator mode — record, refresh, and compile, always through the package's own public API or CLI; Logic-Loom never opens lessons.json directly. Off by default: turning it on is a config.toml / LOGIC_LOOM_FAILURE_MEMORY_MODE decision, not something reachable over HTTP, because it grants write access to every configured project. Writes run as background jobs — a 202 hands back a job id, and the outcome (success or failure) comes only from polling it, never from the fact that the request was accepted.

Both surfaces sit behind their own extra, independent of the existing akms extra:

uv sync --all-packages --extra failure-memory

Without it, Logic-Loom is unaffected — the tab renders an install hint and every endpoint degrades to a typed envelope instead of failing. Projects are never auto-discovered by walking the filesystem; each one is listed explicitly under [[failure_memory_projects]].

Full write-up: dev/docs/failure-memory.md (Product integration + Operator mode sections) and dev/architecture/failure-memory.html.

Review record. Reviewed independently before merge: stream review APPROVED 9.0/10, final cross-repo program review PASS 9/10. This release pins akms-failure-memory to AKMS commit 72494ac4 and the shared consumer-contract conformance pack to sha256:8efa2a01….

Fixed: node-extraction batch runs hung forever in the packaged app

GUI-launched AKMS node-extraction runs stayed in pending indefinitely — the route wasn't wired to the live node-gen executor. Fixed by wiring akms.node_extraction through the real executor; a batch with no NotebookLM notebook id now creates one automatically (and persists it back onto the batch) instead of failing silently.

Also in this fix: the default Assistant workspace no longer lives under ~/Documents (macOS TCC can silently deny access there for a packaged app), and batch/workflow reads now degrade instead of raising when a PermissionError does occur.

Known issues

Backend E2E on windows-latest exits 1 after all tests pass. All 819 backend tests pass, but the job still reports failure — JobRegistry's ThreadPoolExecutor (introduced by the Failure Memory operator's background job queue) leaves non-daemon worker threads parked in Condition.wait() at interpreter shutdown, so Python can't exit cleanly. Two partial fixes (lazy pool creation, an atexit shutdown hook) are already in this release and neither resolved it. Product behaviour is unaffected — this is a CI exit code, not an app defect — and a follow-up will fix the shutdown path. The failure is being tracked in this repository's own failure-memory ledger.

Everything since v0.1.0-alpha.7

v0.1.0-alpha.7 (2026-07-22) already shipped the frozen-sys.executable pipeline fix and the local installer; nothing about that release changes here. If you're upgrading from an earlier alpha, see v0.1.0-alpha.7 and the notes before it for the full path.

Platform availability

Built by the public build-binaries.yml workflow on real macOS, Linux, and Windows runners.

  • macOS Apple Silicon — .dmg
  • Linux x86_64 — .deb and .AppImage
  • Windows x86_64 — .msi and NSIS .exe installer

A single SHA256SUMS.txt manifest covering every asset ships alongside the binaries.

Verifying downloads

shasum -a 256 -c SHA256SUMS.txt