NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
pub.dev
Drive the real Nomos Peer Office from a Flutter app. Apple runs the shared Peer Office in JavaScriptCore over its release-linked native AOT kernel; WASM peers execute the same typed runtime contract with their own shell. Write TypeScript domains, get a typesafe Dart client, build Flutter widgets.
Latest stable
0.71.14
Last release 11 days ago
11 Nov 2026
Ships fairly regularly
a new release about every 9 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
1 version withdrawn
withdrawn after publishing
5 months old
176 releases · first in 2026
Drag across the ruler to compare, or tap a release to open it.
Uses nomos_types 0.18.1 and nomos_client 0.72.21.
Rebuild for the pending npm changesets cap-1111-reception-coordinator-keeps-complete-source and opening-is-retryable, which change the embedded runtim
Rebuild for the pending npm changeset hosted-reception-coordinator-alarm-never-wedges, which change the embedded runtime.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
One column per month.
Select native hosts 0.69.6, the builds that embed kernel d78a0d25 (0.69.24 was never published: its release found the 0.69.5 hosts still embedded the
Restage the bundled runtime with the coordinated compiler release that keeps each founded domain's FoundingPrincipal aggregate in place, so laws using
FoundingPrincipal aggregate in place, so laws using the CAP-1011 founding read upgrade existing workspaces instead of being refused for removing it.Restage the bundled runtime with the coordinated compiler release that selects founded business births from the durable founding record, so console de
Restage the bundled runtime with the coordinated compiler release that selects founded business births from the durable founding record, so console device re-enrolment keeps a founded workspace able to birth children (CAP-1011).
Release the runtime bundle restaged with CAP-892 and the matching nomos_client dependency floor.
The bundled runtime refuses a live offer frame over 25 MiB before encoding it and never records a refused frame as sent: the write goes to the HTTP round at once instead of waiting 15 s for an answer that cannot come, and the transient allocation for an oversized change falls from about 125 MiB to the change itself. A publisher's oversized batch still announces its head, so subscribers converge even when it was the last write (CAP-1008).
The bundled runtime's post-rebase "anything left to offer?" check asks the kernel for one commit above the custodian's head instead of every unsent change (CAP-1007; 5,001 local commits: 3.6 s and 70.6 MB before, 21–29 ms and 14 KB now). A custodian head off the offered head's chain offers nothing in that round rather than the whole history.
The native worker resets the application realm only when the Peer Office confirms the close (realmClosed). A close the office refuses with nomos.runtime.custody_retention_pending or nomos.runtime.preparation_io_pending used to reset the realm anyway: the event pump that settles retention stopped and the typed runtime was dropped, so DartReception.dispose's close retries could never succeed and gave up after 10 s. The realm now stays until a retried close is confirmed (CAP-1009).
The native shell forwards the typed read signals it holds as rate-limited [nomos-read …] console lines (a kernel query's readMode and result size, fro
[nomos-read …] console lines (a kernel query's readMode and result size, frontier-attachment readReady, held local reads), so they reach crash-report breadcrumbs. No payloads; no proto or kernel change.Selects native hosts 0.69.4, the builds that embed Nomos 2026.10.4's kernel: the kernel that has a workspace open composes its law itself, so opens no
- Uses nomos_client 0.70.27.
Selects native hosts 0.69.2 (Apple XCFramework and Android Maven), the builds that embed this release's Kernel 02f654b3; the 0.69.1 hosts carry Kernel
Selects native hosts 0.69.1 (Apple XCFramework and Android Maven), the builds that embed this release's Kernel ddf9aa95; the 0.68.2 hosts carry the ea
Selects native hosts 0.68.2 (Apple XCFramework and Android Maven), the builds that embed this release's Kernel 92575f40; the 0.68.1 hosts carry the 20
- Uses nomos_client 0.70.2.
The WebView/loopback host (Linux, Windows) now uses a downloaded kernel only if it is signed (CAP-813). The kernel store checks the kernel's DSSE atte
The WebView/loopback host (Linux, Windows) now uses a downloaded kernel only if it is signed (CAP-813). The kernel store checks the kernel's DSSE attestation against a release-key certificate. A pinned trust root must have signed that certificate, and it must be valid now. The check runs before the kernel's bytes are fetched, and again when a retained kernel boots offline. If the check fails, the store throws a typed KernelAttestationRefused that uses the same codes as TypeScript, including certificate-expired. The store keeps the attestation and certificate set beside the kernel's bytes.
Local development: a debug build may also trust a local-dev root, if you name it with --dart-define=NOMOS_LOCAL_DEV_KERNEL_TRUST_ROOT=<root>. That root applies only to a cloud on this machine, and release builds ignore it.
New direct dependency: ed25519_edwards, which was already in the graph through nomos_client.
Native hosts no longer read Git leases or speak Git smart-HTTP (native_git_smart_http.dart is gone). Each
workspace's custody arrives over its own live socket from the cloud peer that holds it: a resumable checkpoint,
then batches of the offers after the device's head, then live offers (CAP-826). Git transport, stream and
history effects reaching the native host are refused, and its origin fence grants no storage origin.
Uses nomos_client 0.69.0 and nomos_types 0.14.0; regenerate generated clients. Native hosts 0.68.0 run the Kernel restaged at this release's stack tip, which judges nested wire allocations (CAP-681), qualifies a law release without installing it (CAP-789), refuses a second parent for a business child (CAP-788), indexes a received pack in place (CAP-802) and imports it in bounded steps (CAP-806), keeps one law version per identity named by its unit set (CAP-809), writes the v2 command frontier (CAP-810) and warns when an install does not move its law's claimed version forward (CAP-811). Its digest and the native archive digests are stamped into the published package at assembly from the qualified hosts; the source names only the native versions.
NomosApprovedModel.domainRequirements reaches
the model-adoption desk and the client inventory (NmsClientInventory reports them per domain), so the console
can qualify a release against the contracts actually in the field and record a support policy for the series.[birth-child-already-parented], a birth whose child
already records a different parent. Names are fixed at birth (CAP-803): a business child keeps the name it was
born with, workspaceNameForKey(namespace, key) as in 0.67, so estates, catalogues and directories born
before this release open under their real names. The parent-scoped naming proposed with CAP-788 is withdrawn.REFUSED birth outcome,
quarantines its local child (never followed, pushed or retried; custody kept) and settles the parent's sync
round instead of retrying forever. Birth keys are minted by default; see nomos_client 0.69.0.isA<JSPromise>() instead
of is JSPromise<...>. An is test between JS interop types is not platform-consistent under dart2wasm, so
flutter build web reported three invalid_runtime_check_with_js_interop_types Wasm dry run findings. Under
dart2js the check is now an instanceof Promise test; the runner's boot, frame and dispose ports already
return native promises. nomos_flutter now compiles with flutter build web --wasm; the web consumer gate builds
both.package:nomos_flutter/testing.dart compiles for the web again (CAP-790). It exported the Apple native test peer host unconditionally, which reaches da
package:nomos_flutter/testing.dart compiles for the web again (CAP-790). It exported the Apple native test
peer host unconditionally, which reaches dart:ffi, so any Flutter web app that imported generated scenario
code (which imports testing.dart) failed dart2js with "Dart library 'dart:ffi' is not available on this
platform". Where dart:ffi does not exist, the same names now resolve to a host that cannot start:
registerNomosNativeTestPeerHost() does nothing there, so NOMOS_TEST_PEER_HOST=native is still refused
loudly by the harness, and NomosNativeTestPeerHost.start throws UnsupportedError. Native platforms are
unchanged. Native hosts stay 0.67.0 on Kernel 061cbd5b….Requires Flutter 3.41 or later (platform-scoped assets). Uses nomos_client 0.68.0 and nomos_types 0.13.0; regenerate generated clients (the law is nam
Requires Flutter 3.41 or later (platform-scoped assets). Uses nomos_client 0.68.0 and nomos_types 0.13.0; regenerate generated clients (the law is named by its unit set).
061cbd5b… and its stage-zero law 0419d015…, the
Kernel the dev cloud runs.nomos_background_paper_abandoned (CAP-694, CAP-695).--dart-define=NOMOS_TRACE=true writes an opt-in [nomos-trace] timeline across the save path (CAP-741).sealed_main reports what is durable. Only a sealed main advances the saved
recovery bookmark; after a reconnect the unsealed offers are offered again.LiveLinkClosure,
PeerSocketReceipt.closure).lawUnitSet and
lawPackageSha256 in place of applicationBirthContract, offers carry no law expectation, and a
provider-token Home is born under the law the platform serves.shorebird patch needs no --allow-asset-diffs.Web: a peer that boots before the application attaches (a prewarmed peer) no longer loses its readiness announcement. The page holds runtime events un
flushReady, then delivers them in order;
0.66.x could leave the application unable to open after a reload, a navigation or a browser restart.drive() turn re-reads one owed query group
and still runs maintenance, so live streams and readiness keep advancing during a cold start (0.66.3 regression).Watches refresh after a write on iOS and Android again. 0.66.0–0.66.2 deferred watch re-reads with a timer the native JavaScript engines do not have,
drive() turns on every platform (CAP-687).URL global, which neither native engine provides.nomos_background_paper_abandoned, instead of holding its workspace for five minutes (CAP-695).A browser peer waits for a custody lock another page holds only when its page is a reload or back/forward navigation (its predecessor may still be rel
Ship the stage-zero bootstrap law (a11b0f52…) that a clean checkout reproduces. 0.66.0 carried a law whose bundled runtime comments named the build ma
a11b0f52…) that a clean checkout reproduces. 0.66.0 carried a law whose bundled
runtime comments named the build machine's node_modules path, so the release workflow could not reproduce it.
The Kernel is unchanged (69e87227…); only the law's comments differ.NomosPeerRuntimeHost.prewarm(cloud:) starts a Flutter web peer's boot (worker, custody restore, kernel selection and compile) at application launch, b
NomosPeerRuntimeHost.prewarm(cloud:) starts a Flutter web peer's boot (worker, custody restore, kernel selection and
compile) at application launch, before sign-in; the application's transport shares that boot.nomos-runner-web.js?v=<sha>,
nomos-runner-worker.js?v=<sha>), so hosts may cache them immutably and a deploy never pairs stale assets.69e87227… and its stage-zero law e45e6dd8…, the
Kernel the cloud and browser select.runtime/interface-offer.cbor), so peers composed it instead of mounting it.Bind Apple and Android native distributions to the selected cloud/browser Kernel and stage-zero law. Inspect actual native archives and packaged consu
Ship browser custody checkpoint recovery, explicit Kernel repository selection, boot diagnostics and the completed socket-driven runtime; preserve loc
Fetch the current browser kernel repository and controller law without the HTTP cache, while retaining a verified Cache API copy for offline boot. Thi
Keep the browser worker alive across incomplete outbox history and unexpected background selection faults; the peer asks its shell for bounded history
Run the Flutter web peer and WASM Kernel in a dedicated Web Worker. The page carries only Runtime v2 frames, events, Flutter-owned effects and diagnos
Restaged the generated runtime bridge: a lower layer of the Dart release stack moved. Published pub.dev archives are immutable, so regenerated bytes r
Expose bounded typed Kernel work snapshots and active-call transitions in browser peers, including per-operation call, failure and synchronous wall ti
Store browser custody as bounded file and peer-record chunks in atomic IndexedDB transactions. Migrate existing format-1 workspaces without losing Git
Give every physical sync offer a unique effect identity so inline recovery and rebase can finish without repeating the same request forever. Preserve
Retry a refused physical peer startup when an application retries, replacing the failed readiness future and disposing the failed shell. Keep an estab
Keep browser Git custody and peer control records in atomic IndexedDB transactions, with one writer per origin/provider and recovery after tab termina
Add an optional, bounded client inventory reporter that consumes runtime identity reports and uses a host-supplied authenticated transport. Collection
Package the unchanged Apple native code as a static-library XCFramework, avoiding an invalid embedded framework for apps targeting newer iOS versions.
Retain the complete native host ABI in Swift Package Manager release archives so Dart FFI can resolve it after App Store export.
Recover sync after loss of the upstream bookmark by fetching provider history and allowing the kernel to verify a shared ancestor. Preserve pending lo
Pair with nomos_client 0.66.6 for bounded reception teardown.
nomos_client 0.66.6 for bounded reception teardown.Let authenticated parent-workspace cold opens use the application's bounded startup budget instead of incorrectly reporting a healthy provider as offl
Open trusted checkpoint custody without blocking foreground work on a full-history verification pass.
nomos_client 0.65.3.Resolve the current generated Nomos application call surface through nomos_client 0.65.1 while retaining the independently selected runtime kernel lif
nomos_client 0.65.1 while retaining
the independently selected runtime kernel lifecycle.Consume nomos_types 0.9.0 and nomos_client 0.65.0 so Flutter hosts use the same generated typed offer-admission ABI as the kernel and other hosts.
nomos_types 0.9.0 and nomos_client 0.65.0 so Flutter hosts use the same generated
typed offer-admission ABI as the kernel and other hosts.Declare the generated protobuf messages' direct fixnum runtime dependency so the exact qualified package passes pub.dev validation.
fixnum runtime dependency so the exact qualified package passes pub.dev validation.Expand the deterministic Pulley call-fuel envelope so authenticated first-device birth can complete, and retain the underlying Wasmtime trap reason in
Resolve the resident Pulley host from Flutter's real macOS ephemeral plugin-symlink directory, while retaining the existing iOS CocoaPods path.
Resolve, verify, and retain the provider-selected kernel through a schema-valid OSGi Repository document. The loopback broker serves only the selected
Add the Android application runner used to produce and compose deterministic CycloneDX Pub, Gradle, and CocoaPods dependency evidence for the example
Rebuild and release the embedded runner assets from @githolon/client 0.105.19; the pub.dev archive now carries the exact npm release stamp proved by t
nomos_client 0.64.34 for the corrected generated runner lifecycle.Rebuild and release the embedded runner assets from @githolon/client 0.105.18; the pub.dev archive now carries the exact npm release stamp proved by t
nomos_client 0.64.33 for progress-aware model convergence.Rebuild and release the embedded runner assets from @githolon/client 0.105.17; the pub.dev archive now carries the exact npm release stamp proved by t
Rebuild and release the embedded runner assets from @githolon/client 0.105.16; the pub.dev archive now carries the exact npm release stamp proved by t
nomos_client 0.64.32 so Flutter applications prove durable device enrolment before generated writes become available.Rebuild and release the embedded runner assets from @githolon/client 0.105.15; the pub.dev archive now carries the exact npm release stamp proved by t
nomos_client 0.64.31 so Flutter applications use the restaged, type-safe intent-offer gate and deterministic signer posture.Rebuild and release the embedded runner assets from @githolon/client 0.105.14; the pub.dev archive now carries the exact npm release stamp proved by t
Rebuild and release the embedded runner assets from @githolon/client 0.105.13; the pub.dev archive now carries the exact npm release stamp proved by t
Rebuild and release the embedded runner assets from @githolon/client 0.105.12; the pub.dev archive now carries the exact npm release stamp proved by t
nomos_client 0.64.27 so the Flutter package and its Dart runtime use
nomos.cafe as the sole default cloud surface.Rebuild and release the embedded runner assets from @githolon/client 0.105.11; the pub.dev archive now carries the exact npm release stamp proved by t
Rebuild and release the embedded runner assets from @githolon/client 0.105.9; the pub.dev archive now carries the exact npm release stamp proved by th
nomos_client 0.64.25 and rebuild the embedded runner, keeping the Flutter host on the
same immutable runtime bytes as the generated Dart client.Rebuild and release the embedded runner assets from @githolon/client 0.105.7; the pub.dev archive now carries the exact npm release stamp proved by th
Rebuild and release the embedded runner assets from @githolon/client 0.105.6; the pub.dev archive now carries the exact npm release stamp proved by th
THE OWNER CAN NUKE LOCAL CUSTODY — an inoperable app is not an acceptable resting state. The startup failure surface now offers "Reset local data and
FileSnapshotStore gains purgeAll(); the web store REFUSES loudly rather than
silently purging nothing (quarantine there needs IndexedDB key enumeration, which is not built).THE STARTUP DEADLINE MEASURES A STALL, NOT THE WHOLE CEREMONY. It was armed ONCE for all of startup, so a FIRST open — the one path that must do the e
restore_main 8.2s, of which 8.08s is chain replay
across ~40 intents), then materialises genesis and enrols the device. Every subsequent open imports
the checkpoint in ~0.3s. The deadline now re-arms on each phase transition — progress resets it —
so a startup that stops advancing still fails loudly and typed, naming the phase it died in, while
one that is genuinely working is left alone.