@@ -619,15 +619,13 @@ zig fmt src/           # format
   producers, root slots, reentrant accumulators, pins, in-txn, per-tag traces,
   the `isGcManaged` membrane) + a moving-GC migration checklist. `GC-ROOT:`
   markers in source anchor each published-root site here.
-- [`.dev/zwasm_capabilities.md`](../.dev/zwasm_capabilities.md) — cljw's view of the
-  **embedded zwasm v2** runtime's embedding-API capabilities + cljw's adoption
-  status (F-001). zwasm is SHA-pinned but co-developed (`~/Documents/MyProducts/
-  zwasm`) and is growing a **JIT-backed engine** (ADR-0200) — the
-  north-star capability (ROADMAP §9.0 gap area II × III). **The loop MUST read this
-  ledger at every gap-area-unit start (Step 1a) and every Phase boundary**, refresh
-  it against zwasm's live status sources listed there, and flip the JIT row from
-  BUILDING→adoptable only when zwasm marks it ready AND the pin is (user-)bumped.
-  This is the always-on, git-tracked face of the CODEV co-dev protocol.
+- [`.dev/zwasm_capabilities.md`](../.dev/zwasm_capabilities.md) — cljw's record of
+  the **embedded zwasm v2** runtime's embedding-API capabilities + what cljw
+  adopted (F-001). **FROZEN as of 2026-08-12**: zwasm moved to its own org
+  (<https://github.com/zwasm/zwasm>) under separate maintainership, and v2.5.0 is
+  cljw's final pin — so the per-unit refresh duty and the CODEV mailbox protocol
+  that file used to carry are **retired**. Read it as background on what the
+  final pin embeds, not as a watch list.
 
 ## References
 
 
@@ -1704,7 +1704,12 @@ standing:
         - L6 monomorphization dedup (std.sort clones 0.22MB etc.): opportunistic.
         - L7 UCD two-stage packing (~-0.1MB): only when touching the generator.
         - L5 zwasm-side campaign (691KB arm64 emitter, unused component-model
-          surfaces): FILE via CODEV; defends the 4.0MB zwasm budget line.
+          surfaces): the 2026-07-16 round LANDED (zwasm ADR-0204 / D-522 stage 1,
+          -1,083KB measured here) and the budget line was re-set to 2.5MB. No
+          further round is fileable: zwasm left the org 2026-08-12
+          (github.com/zwasm/zwasm, separate maintainership), so the CODEV channel
+          this lever used is gone — a future size request is an ordinary
+          upstream report, not a co-dev handover.
       Method: scripts/binary_size_report.sh before/after each lever (reference
       platform = macOS arm64 ReleaseSafe -Dwasm stripped); component budget
       breach → attribute → lever or a conscious ADR-0172 revision, never silent.
 
@@ -13,8 +13,12 @@
   tier comes back. Commit **and** push (atomic
   Step 6). `build.zig.zon` `.zwasm` = tag pin **v2.5.0**
   (`278587f6`, 2026-08-12, FINAL — full WASI 0.3 + the `libzwasm.a` C-API
-  export fix; neither reaches cljw's Zig embedding surface. Tagging zwasm is
-  user-only, its ADR-0156). Latest release:
+  export fix; neither reaches cljw's Zig embedding surface). **zwasm now lives
+  at `github.com/zwasm/zwasm`** — its own org since 2026-08-12, separate
+  maintainership; the dep URL names it directly rather than riding the transfer
+  redirect, and the content `.hash` was unchanged by the move. Co-development
+  (the `dogfooding_handover` mailbox, `.dev/zwasm_capabilities.md`'s per-unit
+  refresh duty) is RETIRED — see F-001's 2026-08-12 entry. Latest release:
   **v1.10.0** (2026-08-12) — **the FINAL release**. CHANGELOG is the
   release-history SSOT.
 - **First task on resume**: nothing is pending. The wind-down is DONE:
@@ -33,6 +37,11 @@
   release create` is TOCTOU across the two matrix legs — if they reach it
   within the same instant, the loser fails on "already exists" under
   `set -e`. v1.10.0 missed it by 47 s. Never hit, never fixed.
+- **The v1.10.0 TAG still names `clojurewasm/zwasm`** (fixed after it; it is the
+  final release), and both demos' Dockerfiles build cljw from that tag — so
+  their future rebuilds ride GitHub's transfer redirect. Verified working
+  2026-08-12. It holds only while nothing claims the vacated name: **never
+  create a repo called `zwasm` under the `clojurewasm` org.**
 - **Forbidden**: bare `zig build test` without `-Dwasm`; bare `zig build` for a
   probe (use ReleaseSafe). The FULL gate runs `--serial-e2e`, ALONE; never a
   concurrent build during a gate. `.claude/**` edits + cross-repo publishes may
@@ -51,8 +60,7 @@
   own SSOT — read the script, not a list here.
 - **2026-08-12: the README declares ClojureWasm no longer maintained**
   (`1c8a9cbf`); the Sponsors badge, README footer line, and `.github/FUNDING.yml`
-  are gone with it. Issues/PRs were always disabled — Discussions is the one
-  channel. Wind-down context + the surveyed wording/transfer research:
+  are gone with it. Wind-down context + the surveyed wording/transfer research:
   memory `clojurewasm-wind-down-plan`, `private/notes/2026-08-11-{sunset-wording,
   transfer-risk}-survey.md`.
 - 2026-08-11/12: Discussions #12/#13/#14 (BuddhiLW) answered in code — three
@@ -68,10 +76,8 @@
 ## Standing units (tracked in .dev/debt.yaml)
 
 - **D-565** — external-contributor reproducibility sweep (Discussion #11).
-  Items (1)-(6) DISCHARGED 2026-08-04; the ledger row carries what each was.
   Residual: (7) survey-workflow setup notes, (8) handover pointing at
-  gitignored `private/notes/` recipes. Companion: zwasm D-526.
-
+  gitignored `private/notes/` recipes. The row carries the rest.
 - **Perf campaign (§9.2.S) — PAUSED** (D-520 / D-386 / D-005/006). **D-513**
   item (1) `clojure.core.reducers` is the only remaining piece (repl + var :doc
   landed); it is IN PROGRESS — its "take up on a real consumer" deferral is the
@@ -83,7 +89,8 @@
 
 cljw's differentiator = **Wasm interop (gap II) × VM-perf fusion→JIT (gap
 III)**. zwasm JIT (ADR-0200) is the cljw default; remaining =
-components-through-the-JIT (zwasm-side, D-500). Distal — needs a user nod.
+components-through-the-JIT — now wholly upstream's call (D-500, and zwasm is a
+separate project since 2026-08-12). Distal — needs a user nod.
 NOTE ADR-0177: "edge execution" is an AIM owned by D-552, not a capability.
 
 ## Reading order (resume)
 
@@ -226,6 +226,27 @@ the ADR); debt D-036 (Phase 16 inline-vs-Pod decision); ROADMAP
   build differentiation: **ADR-0133**. Mac full gate verified green; ubuntunote
   verification is the remaining step. `-Dwasm` everywhere (not mixed) per the
   user's "冒頭から -Dwasm" — a mixed wasm/non-wasm build sequence is what breaks.
+- **2026-08-12 (user chat — zwasm transferred out of the org; LOCATION amendment,
+  the invariant itself is unchanged).** zwasm moved from `clojurewasm/zwasm` to
+  its own org, **<https://github.com/zwasm/zwasm>**, where it is maintained
+  jointly by its author and an outside contributor. F-001's substance —
+  cljw embeds zwasm v2, unavoidably, resolved through the `build.zig.zon`
+  tag pin — is **untouched**; what changes is where the dep comes from and the
+  relationship around it:
+  - `build.zig.zon` `.url` now names the `zwasm` org **directly**. GitHub
+    redirects the old path, but a transfer redirect is only an alias until
+    something else claims the vacated name, so a dependency URL must never rest
+    on one. `.hash` is content-addressed and did not change (`zig fetch`
+    verified against both URLs).
+  - **Co-development is over.** The `dogfooding_handover` mailbox
+    (`from_cljw_NN` / `to_cljw_NN`), the "both repos are the user's" finding-
+    handling split recorded in the 2026-06-05 entry above, and
+    `.dev/zwasm_capabilities.md`'s per-unit refresh duty are all **retired** —
+    they were mechanisms between two repos under one owner. A zwasm-side finding
+    is now an ordinary upstream report.
+  - Earlier entries in this history keep their original wording: they record
+    where the tag was pushed and how the two repos related **at the time**, which
+    remains true of those dates.
 
 ---
 
@@ -1222,3 +1243,9 @@ namespace — the surface this invariant guarantees is always present), ADR-0158
   that ClojureWasm as a zwasm consumer forces the latest Wasm/WASI (Component Model
   always on); no Wasm-1.0-only downgrade axis. Recorded as law; operationalised by
   ADR-0135 Amendment 1 + ADR-0158.
+- 2026-08-12: the **invariant stands as shipped** — the `-Dwasm` build selects
+  zwasm's full modern surface (Wasm 3.0 + WASI 0.3 at the v2.5.0 pin) and exposes
+  no downgrade knob. What is moot is the *tracking* clause "when zwasm advances
+  WASI, cljw tracks it as the new floor": v2.5.0 is the final pin and zwasm now
+  lives in its own org under separate maintainership (F-001, same date). A forker
+  who bumps the pin inherits the invariant — never add the downgrade axis back.
@@ -75,8 +75,10 @@ Read the source for *why*; run `clj` for *what*.
   - Use: WebAssembly runtime reference (Phase 16+ Pod boundary design)
   - Not resident (multi-GB). `git clone --depth 1 https://github.com/bytecodealliance/wasmtime ~/Documents/OSS/wasmtime`
   - For Component Model / Canonical ABI questions the FIRST reference is zwasm
-    itself (`~/Documents/MyProducts/zwasm/`, co-developed and SHA-pinned into
-    `build.zig.zon`) — it is the implementation cljw actually runs on.
+    itself, tag-pinned into `build.zig.zon` — it is the implementation cljw
+    actually runs on. Upstream is <https://github.com/zwasm/zwasm> (its own org
+    since 2026-08-12, separate maintainership); a local clone of it, if present,
+    is read-only reference like everything else in this file.
 
 ## Quality-elevation corpora (interim-goal re-cut, 2026-05-29)
 
 
@@ -1,49 +1,38 @@
 # zwasm capability ledger — cljw's view of the embedded Wasm runtime (F-001)
 
-> **SSOT for "what does the zwasm we embed offer, and what has cljw adopted".**
+> **The record of what the zwasm we embed offers, and what cljw adopted.**
 > cljw embeds **zwasm v2** (F-001, unavoidable). The dep is a **tag pin** —
-> **v2.5.0** (see § Pin), pinned 2026-08-12, and this is cljw's **final** pin:
-> the runtime is no longer maintained (README), so this ledger stops tracking
-> zwasm's growth here. Prior pins: v2.4.1 (2026-08-04) the two cljw-found
+> **v2.5.0** (see § Pin), pinned 2026-08-12, and this is cljw's **final** pin.
+> Prior pins: v2.4.1 (2026-08-04) the two cljw-found
 > component/output fixes, v2.4.0 (2026-08-03) the external-consumer release,
 > v2.3.0 (2026-07-17) the WASI-0.3.0-official inventory sweep, v2.2.1
 > (2026-07-16) the binary-size campaign, v2.2.0 (`cf5d20d7`, 2026-07-09)
-> the AOT-full-fidelity release (ADR-0203). zwasm continues under active
-> co-development (`~/Documents/MyProducts/zwasm`) and its embedding API keeps
-> *growing* — notably a **JIT-backed
-> engine** (the cljw north star, ROADMAP §9.0 gap area II × III). cljw has **adopted
-> the JIT as its default** (`.auto`, D-488 discharged); the remaining north-star step
-> is components-through-the-JIT (zwasm-side, D-500). This file is the durable record
-> so the loop never re-derives "is zwasm's JIT ready yet?" from scratch.
+> the AOT-full-fidelity release (ADR-0203). cljw **adopted the JIT as its
+> default** (`.auto`, D-488 discharged); the north-star step it never reached is
+> components-through-the-JIT (zwasm-side, D-500).
 
-## The read-at-boundaries convention (why this file exists)
+## Status of this file: FROZEN (2026-08-12)
 
-The cljw loop **cannot infer zwasm's status from its own tree** — the pin is frozen
-at one commit while zwasm moves on. So, at every **gap-area-unit start** (CLAUDE.md
-Step 1a) **and every Phase boundary**, the loop MUST:
+This ledger existed to answer "what does zwasm have now, and has cljw adopted
+it?" for a **moving** dependency. Both halves of that question are closed:
 
-1. Read THIS file (cljw's recorded view + adoption status).
-2. Refresh it against zwasm's **live** status sources (below). If zwasm shipped a
-   capability cljw's north star needs, update the table here + decide adoption.
-3. Treat a capability as **adoptable only when zwasm marks it ready AND cljw bumps
-   the pin** (`build.zig.zon`) — never adopt against an unpinned/moving API.
+- **cljw is no longer maintained** (README), and v2.5.0 is its final pin.
+- **zwasm left the `clojurewasm` org** on 2026-08-12 for its own org,
+  <https://github.com/zwasm/zwasm>, where it continues under **separate,
+  joint maintainership**. It is no longer a project this repo co-develops.
 
-This is the cljw-side, git-tracked face of the **dogfooding handover protocol**
-(simplified, no-loop, 2-state — `dogfooding_handover/PROTOCOL.md` below). **Also at
-each unit boundary (after a commit, before the next Step 0), check the INBOX**
-(`to_cljw_*.md` with `Status: SENT`); handle it, then flip to `CONSUMED`. When cljw
-needs a not-yet-ready zwasm capability, the request goes out as a `from_cljw_NN.md`
-(finished-form, request-don't-workaround; mark the dependent cljw task PENDING), never
-a cljw-side shim.
+So everything below is a **record of what cljw's final pin embeds**, not a
+watch list. The obligations this file used to carry are retired: there is no
+per-unit refresh duty, no `dogfooding_handover` mailbox (the `from_cljw_NN` /
+`to_cljw_NN` channel was between two repos under one owner and ended with the
+transfer), and no adoption decisions pending. Capability rows are accurate as
+of the dates they carry and are **not** kept current against zwasm's ongoing
+development — read zwasm's own repo for that.
 
-## zwasm live status sources (read these to refresh the table)
-
-| Source                                                      | What it tells you                                              |
-|-------------------------------------------------------------|----------------------------------------------------------------|
-| `~/Documents/MyProducts/zwasm/private/dogfooding_handover/` | **the mailbox** — `PROTOCOL.md` + `from_cljw_NN`/`to_cljw_NN` |
-| `~/Documents/MyProducts/zwasm/.dev/ROADMAP.md`              | zwasm phase plan (p17 = JIT)                                   |
-| `~/Documents/MyProducts/zwasm/.dev/decisions/0200_*.md`     | ADR-0200 — JIT-DEFAULT engine + research-driven API           |
-| `git -C ~/Documents/MyProducts/zwasm log --oneline -15`     | recent JIT work (zwasm#477 multi-arg invoke arm64/x86_64)      |
+A forker who wants to move to a newer zwasm should treat this as background,
+bump `build.zig.zon` themselves, and re-verify against the five `phase16_wasm_*`
+e2e — the embedding surface cljw actually depends on is narrow (Engine / Module /
+Instance / `runWasmCapturedFull` / `wasi.host.Host`).
 
 ## Pin
 
@@ -95,10 +84,11 @@ a cljw-side shim.
 - `lazy` dependency: resolved only under `-Dwasm`. So a churning dep never
   breaks the day-to-day gate when the flag is off — it
   only gates what `cljw.wasm/*` can do.
-- Pin-bump (to a newer tag/SHA): zwasm `docs/consuming_prerelease_zwasm.md`. Re-pin is
-  **user-gated** (a moving north-star API; the loop proposes, the user confirms).
+- Pin-bump (to a newer tag/SHA): `zig fetch "git+https://github.com/zwasm/zwasm.git?ref=<tag>#<SHA>"`
+  prints the content hash; hand-edit `.url` + `.hash` + keep `.lazy` (`--save` mangles the
+  entry). No further bump is planned — v2.5.0 is final for this repo.
 
-## Capability table (refresh at each boundary)
+## Capability table (frozen; rows accurate as of the dates they carry)
 
 | Capability                            | zwasm status (as of 2026-06-22)                                                                                                                            | in cljw's tree? | cljw adoption                                                                                                                   | ref          |
 |---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------------------------------------------------------------------------------------------------------------------------|--------------|
@@ -117,10 +107,11 @@ a cljw-side shim.
 | guard-page bounds-check elision (JIT) | NEW in v2.2.0 (D-507/ADR-0202) — reservation-backed linear memory + fault→trap PC-redirect; bounds checks elided by default, diff-fuzz-gated (D-510)     | YES (pin)       | transparent — cljw's `.auto` guests get the faster JIT bodies; no embedding-API change                                         | zwasm D-507  |
 | .cwasm AOT + on-disk compile cache    | NEW in v2.2.0 (ADR-0203) — full-fidelity `.cwasm` v0.5 serialize/load (aot-diff 62/62) + transparent `--cache` (D-508); JIT helpers de-baked (D-516)      | YES (pin)       | NOT adopted — zwasm-CLI-side surface today; candidate for cljw cold-start (evaluate when an embedding API for the cache lands) | zwasm D-508  |
 
-## Forward plan — the JIT adoption unit (gap area II × III) — ACTIVE
+## The JIT adoption unit (gap area II × III) — CLOSED, partially reached
 
-The north-star capability is **running Wasm components through zwasm's JIT engine**
-from cljw. The trigger has FIRED (to_cljw_02, 2026-06-21) and adoption is in progress:
+The north-star capability was **running Wasm components through zwasm's JIT
+engine** from cljw. Scalar/SIMD function invocation got there; components did
+not (they stayed interp-pinned on the zwasm side, D-500). The record:
 
 1. **Trigger (DONE)**: zwasm shipped the embedder-stable JIT engine (`to_cljw_02`);
    cljw switched the dep to relative-path (user-directed experiment, no-push).
@@ -259,3 +250,13 @@ have surfaced it.
   behaviour follow (five phase16 wasm e2e + the full gate green on it). This
   ledger's watch duty ends here: cljw is no longer maintained, while zwasm
   continues under separate maintainership.
+
+- **2026-08-12 (same day)** — **zwasm transferred out of the `clojurewasm` org**
+  to its own org, <https://github.com/zwasm/zwasm>, to be maintained jointly by
+  its author and an outside contributor. cljw's dep URL now names that org
+  directly rather than riding GitHub's transfer redirect (a redirect is only an
+  alias until something else claims the old name — the RepoJacking shape). The
+  `.hash` is content-addressed and did not change, verified by `zig fetch`
+  against both URLs. This file is FROZEN as of this entry; the co-development
+  protocol it used to carry (per-unit refresh, `dogfooding_handover` mailbox)
+  is retired with the transfer, since the two repos no longer share an owner.
@@ -30,8 +30,15 @@
         // (`-Dcompiler-rt`, sub-3.0 DCE); v2.3.0 (2026-07-17) WASI-0.3.0 sweep;
         // v2.2.1 (2026-07-16) binary-size campaign; v2.2.0 (2026-07-09) AOT
         // full fidelity.
+        //
+        // zwasm moved out of the `clojurewasm` org to its own `zwasm` org on
+        // 2026-08-12, where it continues under separate maintainership. The URL
+        // below is the canonical one; do NOT rely on GitHub's transfer redirect
+        // from `clojurewasm/zwasm`, which stops being an alias the moment
+        // anything else claims that name. The `.hash` is content-addressed, so
+        // the move did not change it (verified by `zig fetch` on both URLs).
         .zwasm = .{
-            .url = "git+https://github.com/clojurewasm/zwasm.git?ref=v2.5.0#278587f608a7564d8f2dfa53f567aab70f661296",
+            .url = "git+https://github.com/zwasm/zwasm.git?ref=v2.5.0#278587f608a7564d8f2dfa53f567aab70f661296",
             .hash = "zwasm-2.5.0-FT1Fv4KPkgCaKsDmsn05BTYsoEhH7RCUreSX8a3mwFha",
             .lazy = true,
         },
 
@@ -1,6 +1,6 @@
 # WebAssembly as an FFI — polyglot demo
 
-ClojureWasm can embed a WebAssembly engine ([zwasm](https://github.com/clojurewasm)
+ClojureWasm can embed a WebAssembly engine ([zwasm](https://github.com/zwasm/zwasm)
 v2) and call modules compiled from **other languages** as if they were Clojure
 namespaces. This is the "WebAssembly as an FFI" idea: a Clojure REPL loads a
 sandboxed `.wasm` and invokes its exports.