Skip to content

Parity with drowse 6.1.3: typed frames, hook ABI v6, catalog 12 - #3

Merged
a9lim merged 16 commits into
mainfrom
parity-6.1/main
Nov 12, 2026
Merged

a9lim merged 16 commits into
mainfrom
parity-6.1/main

Conversation

@a9lim

@a9lim a9lim commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Brings drowse.ai to parity with drowse 6.1.3 (pinned at d47bf536) and Ledger 0.1.5.

What 6.1 changed, and how the browser follows

  • Typed manifold frames. A fitted subspace now carries write rows (basis, orthonormal in the Mahalanobis metric) and read rows (read, their Σ⁻¹ duals). A full ! ablation is now LEACE.
    • The browser fit (Rust/WASM kernel and TS workers) writes typed frames: fit policy 2, layer_<L>.read tensors, and the monopolar fold.
    • Steering synthesis and lowering follow _ortho_frame, synthesize_subspace and _orthogonalize_affine_against; the curved frames and geometry probes read through read.
  • Hook ABI v6. The GPU kernels used to read and write along one shared basis.
    • affine_read and curve_read now come right after each basis in every entry point. The kernels read coordinates through them and write along the basis.
    • Renamed: block-sites-v6, drowse-structured-v5, standard-v5, drowse-web-runtime-v3; the bridge is @drowse/web-llm 0.2.84-drowse.50.
    • All nine libraries are recompiled.
  • Gains: affine 16 → 8, curved along 4 → 2.
  • Lens atoms are reads: jlens/ and slens/ atoms steer along the raised vector Σu. Unit find solves its pursuit in fp64 and stops early.
  • Tolerant persisted formats: readers require only the fields they use. files maps, share_metric and subspace_metric are gone. A stale fit installs as a miss and refits. The browser's own download-integrity checks (signed catalog, per-download digests) are unchanged.
  • Goldens: drowse no longer ships browser goldens, so the tests that read them are deleted. The port was checked once against 6.1.0's goldens and the pinned engine in scratch. Codex also reviewed the numerics independently and ran seven edge-case comparisons against native (max difference 2.2e-6).

Release

  • Models: nine model repos republished (only model.wasm and drowse-build.json changed).
  • Packs:
    • R/S/units packs rebound to the v6 runtime identities, with tensors byte-identical to 6.0's.
    • SAE packs re-imported.
    • Cores rebuilt in the browser (policy-2 fits).
  • Catalog and locks: catalog 12 is signed and published at the new v3/ path, so the live site keeps reading v2/ (catalog 11) until this deploys. The runtime lock is adopted, and the distribution lock points at v3/ with minimum sequence 12.

Upgrade fixes found by the smoke test

  • Stale model installs. A model installed under 6.0 counted as installed, so the redownload skipped the model and then failed on its packs. A model install the accepted catalog no longer describes now counts as not installed; it downloads again, reusing stored objects.
  • Stale working sessions. A model's working session saved under an older runtime blocked loading the model. It now resets; the saved-chat library keeps the conversation.
  • Both were verified on a browser profile holding real 6.0 state (the Nov 2 chat reopens on the 6.1 runtime) and have worker tests.

Checks

  • check, check:hosted, test:hosted, pytest tests (132) and e2e (Chromium, 286) pass.
  • build:hosted:release passes.
  • Smoke on the release build on WebGPU, with Gemma 3 1B from catalog 12: generation, a typed-frame steer, the Units room, and the Lens room (S and R).

Follow-up for drowse: the shared contracts.ts still types StructuredHookProfileId as the v4 ids. The hosted code casts v6 ids through sharedProfileId(); rename the type in the next drowse release and drop the cast.

a9lim added 16 commits November 11, 2026 22:00
…s read rows beside its write rows

The fixture runtime's tiny models move into the site (drowse no longer ships them). Affine groups
and curves take read rows dual to their basis (read @ basisT = I, native's synthesized-frame check):
the CPU reference reads coordinates with them and writes along the basis. The core pack still
passes its basis as its reads until the typed lowering lands.
…ich no longer carry integrity digests or a files map; the lens pack manifest keeps its own shard digests
…onormal write rows Xᵀa/√μ with their exact dual reads, reduced coordinates, DLS, node covariances and the monopolar fold read through them, fits stamp policy 2 and carry layer_<L>.read tensors
…te/read pairs, fitted read rows for curves and geometry probes, gains 8 and 2, lens atoms raised to Σu, and the units pursuit solved in fp64 with an early stop.
…e the fields they use and ignore the rest, pack.json and manifold.json lose their integrity files maps (fitted pairs are found beside the manifest, digests are the browser's own record of what it staged), sidecars drop share_metric and subspace_metric, and a fit of an edited corpus installs as a miss that refits
# Conflicts:
#	webui/src/hosted/artifacts/drowseArchive.ts
…te rows (affine_read and curve_read after each basis in every entry point), the MLC kernels read coordinates through them and write along the basis (the affine kernel now updates the residual in place to stay within 8 storage bindings), the bridge uploads and passes them (@drowse/web-llm 0.2.84-drowse.50), and the names move to block-sites-v6, drowse-structured-v5, standard-v5 and drowse-web-runtime-v3 (descriptor PROFILE 5, ABI 6, format 5). verify-mlc-hook checks a typed affine and a typed curve case; drowse's shared StructuredHookProfileId still names the v5 profiles, so v6 ids cross it through sharedProfileId
…of the write row, so the tool compiles v6 programs
…ools go (the units-* script tests, sampling/structured/steering-term parity, the WebGPU and C VM units harnesses, record-cvm-goldens, the fixture builders and their fixtures), mixed tests lose their golden cases, the C VM harness verify-production-library needs moves to units_vm.py, the tiny-models input reads from its vendored copy, the topology table is inlined, and AGENTS.md says there are no parity goldens.
…lish revisions) and point the distribution lock at catalog 12, published at v3/ for runtime v3 builds; v2/ keeps catalog 11 for deployed v2 builds
…tall whose objects the accepted catalog no longer lists counts as not installed, so the shell downloads it again (stored objects reused) instead of adding new-runtime packs onto it; and a working session bound to an older runtime opens on a fresh session (the saved-chat library keeps the conversation) instead of refusing the model
@a9lim
a9lim merged commit 352361d into main Nov 12, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant