NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev, #5643 most downloaded on 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 10 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.
A FAILED BOOT REFUSES AS ITSELF — a transient fault can no longer destroy good local custody. 0.63.36 reclassified EVERY boot failure that happened wh
nomos.custody.snapshot_corrupt, whose recommended action is quarantine-and-reclone. Boot does
network work, so a cold container or any transient fault threw the device's local custody away and
forced a full re-clone — plus a foreign-source clone to satisfy the kernel's colocated reads —
which is how a LOCAL-FIRST app came to hang 30s in openingCustody and repeat it on every retry.
"Boot failed" is not evidence about the bytes on disk. Only the code that actually read those bytes
may condemn them, and those sites now carry their own custody code and quarantine action.AN ESTATE CAN BE OPENED AGAIN. Opening an estate failed with "generated application cannot identify the active 'estate' model it would supersede" — th
Realm.snapshot(name) now exports mounted, parked, AND born-but-unopened residents,
so the estate persists locally and reopens with its own law.nomos.custody.snapshot_corrupt) that quarantines the bytes — never discards them
— and performs one clean authenticated reconnect. A corrupt v2 envelope is likewise refused
instead of being fed to the tree decoder as though it were legacy binary custody.Your coding agent can read these notes before it upgrades. Set up the MCP server →
One column per month.
THE SEATED BARRIER GATES WRITING, NOT OPENING. A device seating into an existing home had to prove its enrollment against cloud truth BEFORE the appli
THE LOCAL-FIRST GATE — a cold, slow or absent cloud can no longer stop a home from opening. The home lifecycle used to hold the first frame until sync
seated (identity, custody, and the right to author); the tail runs in the
background behind the new REQUIRED runConvergenceTail callback and reports as
status, never as a gate.HomeBootstrapStage.syncAttempted moved below seated, so a v1
cursor at that stage — which meant "synced but NOT seated", the opposite of what
the new index implies — is read down to homeAvailable rather than trusted
verbatim. Honouring it would let an upgrading device skip the seating barrier.
Re-seating is an idempotent ensure, so the cost is one redundant check.A late lawful open BEATS a stale startup deadline. The startup-timeout overlay paints over the still-mounted application scope; when the open then com
_startupComplete now clears the deadline error and
rebuilds. Diagnosed live 2026-08-07 from device telemetry: synced sites and
a live estate map underneath the failure surface.THE SEATED BARRIER (architecture/seated_barrier_and_seal_obligation.md Part 3): a new REQUIRED seated stage in the home ceremony (HomeBootstrapStage.s
seated stage in the home ceremony (HomeBootstrapStage.seated + proveSeated on
resumeHomeBootstrap). A device seating into an EXISTING home must now PROVE — by reading the
cloud's canonical state, never by trusting an ack — that its signer enrollment is durably on the
judging chain before the app may author sync-dependent work. A fresh offline home birth is
unaffected (enrollment rides the genesis; local truth suffices — offline-first preserved). An
unproven seat fails typed + retryable (NomosSeatingPendingFailure, code
nomos.client.seating_pending) and resumes at the barrier. This closes the 2026-08-06 class of
loss where work signed by a not-yet-durably-enrolled key was doomed at the shared gate.NomosHomeSetupFailure.toString() now includes the underlying technicalDetail instead of only a generic recommended-action sentence — a real error visi
NomosHomeSetupFailure.toString() now includes the underlying technicalDetail instead of
only a generic recommended-action sentence — a real error visible on screen, not a dead-end
"try again" (diagnosed live 2026-08-06 against build 1178's smoke gate, which surfaced only
the generic message for a genuine, specific failure).@githolon/client's ensureParentSignerEnrollment routing fix (this same session):
the existing-home device-recovery fallback added in 0.63.29 was itself blocked by a separate
routing bug that failed before ever reaching the (already-handled) security refusal — verified
live, the fallback now actually runs end-to-end.Fix a genuine device-loss dead end: a founded receiving group whose one enrolled device is lost had NO lawful recovery lane (every enrolment door corr
architecture/guardian_device_recovery.md) but is the only way a
genuinely locked-out owner recovers today; seatDeviceInExistingHome now falls back to it,
scoped to exactly the named receiving-group-additional-device-requires-current-device-or-guardian
refusal so a healthy home's security posture is unaffected.Rebuild and release the embedded runner assets from @githolon/client 0.105.1; 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.0; 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.104.1; 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.103.19; 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.103.18; 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.103.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.103.16; 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.103.15; 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.103.14; the pub.dev archive now carries the exact npm release stamp proved by t
ApplicationModelApproval.package/.domain gain an optional dispositions field; ApplicationModelDecision.accept, DomainClientModelAdoptionRequired.accept and the generated NomosModelAdoption.accept thread it through the current-frontier transition and promoteDomain — a tenant can acknowledge a genuine field/aggregate removal ({"retired": [sid, ...]}) from model.adopt() instead of only via a raw adapter script.@githolon/client's fix for a compiler bug where a shared enum's cosmetic export-binding name leaked into its field's business-value-contract hash, manufacturing false-positive evolve refusals.Rebuild and release the embedded runner assets from @githolon/client 0.103.13; the pub.dev archive now carries the exact npm release stamp proved by t
nomos_client 0.64.14 with the matching generated application lifecycle.Rebuild and release the embedded runner assets from @githolon/client 0.103.12; the pub.dev archive now carries the exact npm release stamp proved by t
3c5ea6976ea135dfee7d2dbe41f43a715c78eeb69dacdf185ab85dbc392e49c3 kernel and
runner, preserving semantic cross-workspace residency across independently resealed replicas.nomos_client 0.64.13 with the matching typed state-position protocol.Rebuild and release the embedded runner assets from @githolon/client 0.103.11; the pub.dev archive now carries the exact npm release stamp proved by t
nomos_client 0.64.12, preserving clean resident unborn workspaces between genesis and their
first durable push while keeping failed cold mounts retryable.Rebuild and release the embedded runner assets from @githolon/client 0.103.10; the pub.dev archive now carries the exact npm release stamp proved by t
nomos_client 0.64.10 with the matching generated runner custody.Rebuild and release the embedded runner assets from @githolon/client 0.103.9; the pub.dev archive now carries the exact npm release stamp proved by th
nomos_client 0.64.8 so periodic metrics refreshes do not fan out unchanged aggregate
application status or rebuild tenant UI while preserving seeded status for newly attached listeners.Rebuild and release the embedded runner assets from @githolon/client 0.103.8; the pub.dev archive now carries the exact npm release stamp proved by th
171bd538ffccfbf248b2b25962d44676cf78466d5da2dfa32c8618ba5f38bf45 kernel.Rebuild and release the embedded runner assets from @githolon/client 0.103.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.103.6; the pub.dev archive now carries the exact npm release stamp proved by th
Consume nomos_client 0.64.6, whose published archive now matches the generated application lifecycle and typed operation surface compiled by this rele
nomos_client 0.64.6, whose published archive now matches the generated application lifecycle
and typed operation surface compiled by this release.Consume nomos_types 0.8.3 throughout the coordinated Flutter release.
nomos_types 0.8.3 throughout the coordinated Flutter release.Bound generated application startup to 45 seconds across identity credentials, home custody and typed client binding. A stalled phase now reaches the
NomosApplicationStartupTimeout instead of leaving an immortal loading indicator.Coalesce identical home connection requests onto one in-flight open while serializing real credential changes on the same native kernel, preventing re
Cross the one-time USDA custody boundary without restoring pre-USDA local snapshots, while retaining the device identity and re-running the normal off
Ship the coherent USDA-native kernel candidate across Apple, web and test-mint runtimes, with immutable kernel identity checks and native typed offer/
Run the generated application against the release-pinned external kernel while retaining that verified runtime for offline restart; a fresh-but-wrong
Mount the generated domain application as the one Flutter application state. Product code supplies sign-in and business facts, then calls intent-shape
commissionAsset; framework runtime hosts,
repositories and serialization helpers are no longer alternate public lanes.NomosRef<T> identities across WebView/WASM snapshots and the production Apple kernel, while
Nomos privately seals owned fields and restores their custody after process restart.Fetch the hash-pinned Apple framework during CocoaPods installation without embedding it in the pub package. Its libuv and uvwasi inputs are now sourc
Keep the kernel executable out of the pub/npm-facing Flutter package. The runner carries only the production + dev-test release descriptors; Android/W
Keep parent-before-child custody ordering inside Nomos: an offline-born child remains retryable framework work until its parent birth reaches custody,
Release the full business-first model surface as one Flutter runtime: aggregate conflict policy, deterministic schema evolution, recursive organisatio
Ship the exact verified-birth kernel now deployed by cloud and web (d8ee1a70fdaa…) in the Apple xcframework. Cloud deployment, the served wasm, native
d8ee1a70fdaa…) in the Apple
xcframework. Cloud deployment, the served wasm, native source identity and both podspec pins now agree;
the published client cannot silently run the older pre-lineage kernel.Ship the framework-owned birth-lineage ceremony used by the headless harness and the corrected kernel verifier for a root-signed, one-link platform pa
Reject a malformed birth certificate chain at the parent admission gate before any birth record or child custody can land. The Apple framework is rebu
Replace configurable home-birth profiles with one public application contract: NomosScope.home(cloud:, application:, authToken:, builder:). Nomos deri
NomosScope.home(cloud:, application:, authToken:, builder:). Nomos derives the canonical subject from the
token, discovers the active framework/home laws, and owns routing, enrollment, provenance, recovery and
persistence internally.NomosHomeSetupFailure while retaining technical detail for support.ca687c59887…) in the Apple xcframework. Dart verifies the
linked binary's full source-wasm identity at startup; CI, pub release and cloud deploy now refuse any
JavaScript/native/cloud skew. There is no engine fallback for a broken package.Bundle the one-call business birth runtime and require nomos_client 0.62.0, whose session-bound generated clients derive the verified principal automa
nomos_client 0.62.0, whose session-bound
generated clients derive the verified principal automatically.nomos_client floor ^0.61.0 (the era-0 release: signer-ready births — birthHome requires ownerKeyHash; the client auto-signs self-serve birth certs on
ownerKeyHash;
the client auto-signs self-serve birth certs on the kernel's typed refusal; follow/acquireSession
accept authorSecret for warranted locally-born children).Nothing published for this version
Nothing published for this version
Nothing published for this version
Runner assets carry the colocated attested-read fix: a generated directive's foreign read(q, {from}) now resolves from the mounted source session in-e
read(q, {from}) now resolves from the mounted source session in-engine (signed envelope, zero HTTP) — the session-alias vs workspace-name keying bug that made it fall through to a 31s HTTP fetch on Flutter. Adds fast-fail SourceSessionNotMounted. Depends on nomos_client ^0.58.0.Nothing published for this version
Pin nomos_client: ^0.56.0 (was a wider range in 0.55.8) to match the generated-client pin convention (NOMOS_CLIENT_DEP) — nomos_client 0.56.0 and nomo
nomos_client: ^0.56.0 (was a wider range in 0.55.8) to match the generated-client
pin convention (NOMOS_CLIENT_DEP) — nomos_client 0.56.0 and nomos_flutter move together.Widen the nomos_client dependency to >=0.55.0 <0.57.0 so nomos_client 0.56.0 (NomosTestCloud, typed snapshot lifecycle, projectionReadFailed) resolves
nomos_client dependency to >=0.55.0 <0.57.0 so nomos_client 0.56.0 (NomosTestCloud,
typed snapshot lifecycle, projectionReadFailed) resolves alongside nomos_flutter — the caret ^0.55.0
wrongly excluded 0.56.0, so the two could not coexist. Bundled JS runner assets are rebuilt from the
compound-key-capable @githolon/client at publish.Carry the @githolon/client fix: sync() now surfaces a typed pushError (endpoint, status, body) with pushFailed:true / stillAhead:true on a non-2xx/inv
sync() now surfaces a typed pushError (endpoint, status,
body) with pushFailed:true / stillAhead:true on a non-2xx/invalid direct offer, instead of
a silent pushed:null that hangs the app waiting on custody that never advances. Runner bundle
rebuilt. Patch bump — keeps the nomos_client: ^0.55.0 pin valid.Export NomosRefAcquire (the ref.acquire(bridge) extension) from the barrel, carrying the nomos_client 0.55.2 session-state DX: explicit workspace stat
NomosRefAcquire (the ref.acquire(bridge) extension) from the barrel, carrying the
nomos_client 0.55.2 session-state DX: explicit workspace state on listWorkspaces(), openable
born/resident refs (await outcome.bornRefs.single.acquire(bridge)), and the
NomosSession.isConnected/assertConnected() fail-at-bind guard.nomos_client: ^0.55.0 pin valid.Fix NomosScope snapshot persistence for multiple sessions: _exportAndSave now binds head()/export() to bridge.session(workspace) instead of the bare p
NomosScope snapshot persistence for multiple sessions: _exportAndSave now binds
head()/export() to bridge.session(workspace) instead of the bare plane-level calls, which
refuse "multiple sessions connected — pass session" once an estate/catalogue sibling session
mounts — previously silently stopping home snapshot persistence.Runner bundle rebuilt to carry issueDelegationCert (the public role-delegation cert lane) and the deriveWorkspaceName addressing helper reachable thro
issueDelegationCert (the public role-delegation cert lane) and the
deriveWorkspaceName addressing helper reachable through the bridge. Native kernel unchanged (efff5199).Native iOS/macOS kernel re-pinned to wasm efff5199 (delegated-authority offline births — the delegation-cert gate verifies a platform's grant to K_roo
nomos_client: ^0.55.0 floor unchanged.Native iOS/macOS kernel re-pinned to wasm f4e05b47 (the Surfaced read-collapse fix — replica as string for RFC-8785 canonicalization; byte-identity pr
nomos_client: ^0.55.0 floor.Fix: the `nomos_client` dependency floor was `^0.54.2`, not `^0.55.0` — 0.55.0 shipped with a stale floor (a release-process no-op), so a Flutter app
nomos_client dependency floor was ^0.54.2, not ^0.55.0 — 0.55.0 shipped with a
stale floor (a release-process no-op), so a Flutter app using a client generated by
@githolon/dsl 0.80.0+ (which pins nomos_client: ^0.55.0) could not pub get without an
override. Floor corrected to ^0.55.0. (A pins tripwire now ties this floor to the generated-client
floor so they can't diverge again.)Bundled runner rebuilt with the adversarial-sweep client fixes (watch rebind, DLQ salvage, self-binding enrollSigner recovery lane). nomos_client floo
nomos_client floor -> ^0.55.0; bundle stamp 0.80.0.Signer-recovery principal normalization fix (see nomos_client 0.54.1); home scope passes the canonical actor. Bundled runner rebuilt. Floors: nomos_cl
`NomosScope.home` recovers parent authority: the born+keyed fast path now verifies the stored device signer is enrolled on the configured parent (one
NomosScope.home recovers parent authority: the born+keyed fast path now verifies the stored
device signer is enrolled on the configured parent (one relation read per open) and lawfully
repairs after a parent custody rebirth — sibling births no longer refuse with an opaque gate
error on a reborn parent. Posture exposed via onParentAuthority / parentAuthorityOf; an
unreachable parent records posture and never bricks offline use. Bundled runner rebuilt
(enrollment + canAuthor ops, authz diagnosis classification).