NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
Nomos 2 Dart client — generated domain values, intent payloads and application lifecycle types over the typed Nomos kernel protocol and USDA custody model.
Latest stable
0.72.21
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
Nothing withdrawn
no release was ever pulled
5 months old
134 releases · first in 2026
Drag across the ruler to compare, or tap a release to open it.
Resolve framework-private first-device offers through the application law's concrete home route, and distinguish a merely installed model from the mod
Preserve cross-replica foreign-read identity with the canonical USDA state root while treating the Git commit as a replica-local custody hint; the sha
Preserve a clean resident unborn workspace across successive offers so framework genesis remains colocated until its first durable push; only an actua
Your coding agent can read these notes before it upgrades. Set up the MCP server →
One column per month.
Single-flight each generated child open on the process-wide kernel plane, reuse resident sibling custody for foreign reads, and restore every generate
Deduplicate structurally identical workspace and application status snapshots while still seeding every new listener, preventing periodic metrics refr
Bound generated application startup and referenced-workspace opens, preserving typed custody failures and retryable custody while keeping law adoption
Publish the complete generated-application runtime already present in the coordinated source release, including typed operation receipts, model change
Consume nomos_types 0.8.3 so custody object identities remain typed through generated clients.
nomos_types 0.8.3 so custody object identities remain typed through generated clients.Require generated applications to seed explicit child-birth and workspace policies before first use; missing law remains a typed kernel refusal instea
Single-flight generated child-workspace acquisition and continuous sync so concurrent references share one open, one lifecycle result and one error ra
Execute generated applications through the typed USDA-native kernel boundary, including native read recipes, sealed offer diagnostics and lawful self-
Resolve a compiled OpenUSD application as one ordered package set in generated offline and connected scenarios, keeping reference-only control law off
Generate one self-documenting application object: intent-shaped business actions at the root, typed aggregate collections for reads and navigation, ag
NomosRef<T>; secondary ensures keep their aggregate identity through
compilation and admission.Make automatic sync a truthful client-owned lifecycle: local acceptance is durable, offline/restored sessions remain usable, reconnect converges paren
Generated clients now expose business-first conflict policy, schema-aware merge continuation and recursive organisation descriptions. The client priva
Make NomosTestHarness own a complete, verifiable local trust lineage. Tests still bind a business actor and call the generated birth method; the harne
NomosTestHarness own a complete, verifiable local trust lineage. Tests still bind a business actor
and call the generated birth method; the harness privately mints its test root, seats the signer and
delegation, lands the warrant in order, and refuses any child whose full chain does not replay to that root.Align the public Dart documentation with the one Flutter application entry point: identity comes from the token passed to NomosScope.home(application:
NomosScope.home(application:, authToken:); application code no longer supplies a subject
or device-token callback.Generated business clients expose one birth(payload) method. The bound session supplies its verified principal from the authentication token, and Nomo
birth(payload) method. The bound session supplies its verified
principal from the authentication token, and Nomos owns the identity, provenance, persistence, and
recovery ceremony beneath the business call.cloudBound seeds the KEYLESS enroll-once delegation (mintKeylessDelegation) so a keyless private home is born with a well-formed cert chain (was: plat
cloudBound works against PRIVATE platforms/homes (declared read caps — the co2 shape): the device ceremony uses a LOCAL scratch session (never clones
Runner entry resolution prefers the BUILT @githolon/client/runner/node-entry.mjs (published consumers: node refuses type-stripping under node_modules,
@githolon/client/runner/node-entry.mjs (published consumers:
node refuses type-stripping under node_modules, so the raw .ts entry only booted in-repo — DEFECT P3-002).ERA-0 cloud-bound harness — NomosTestHarness.cloudBound now runs the full WARRANTED onboarding ceremony against the test cloud: the platform is BORN w
NomosTestHarness.cloudBound now runs the full WARRANTED onboarding
ceremony against the test cloud: the platform is BORN warranted+attested at cloud boot
(NomosTestCloud.start(platform:, deployJsonPath:)), the owner's device enrols through the REAL
first-device lane (/dev/mint-token → enrollFirstDevice), and birthHome is device-signed +
attested with ownerKeyHash (the born home is SIGNER-READY — it births estates/catalogues offline
from intent 0). Six named phases, all deadlined.NomosTestCloud.start(platform:, deployJsonPath:) — the dev cloud stands the platform up at boot
(era-0: the host does not create workspaces; the harness's old POST-create refuses 409 by design).
/health gates on platformReady: true so clients never race the ceremony.acquireSession(…, authorSecret:) — sign a locally-born (warranted) child session's writes with
its owner's device key; deviceSecret(workspace)/devicePublicKey(workspace) expose the harness
device (the harness IS the device) for .births() payload ownerKeyHash derivation.githolon/@githolon/client ≥ the era-0 release (the client auto-signs self-serve birth
certs on the kernel's typed birth-unattestable refusal — apps never hand-roll certs).Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
NomosTestCloud (co2 #4) — a headless, cloud-BOUND real-sync test harness: start/stop a local githolon cloud dev (the same engine plane production runs
githolon cloud dev (the same engine plane production runs), an online/offline PARTITION proxy
(setOnline) for deterministic link sever/heal, and remote head/commit inspection (remoteHead).
Sessions connect cloud-bound to cloud.origin; sync/convergence uses the existing bridge.sync.snapshotWorkspace/snapshotPlane and
restoreWorkspace/restorePlane over the per-workspace export()/connect(restoreFrom:)
primitives, with typed WorkspaceSnapshot/PlaneSnapshot (JSON round-trip, session/workspace
metadata). Migrate staged AppSim snapshots mechanically — no reaching into custody internals.assertCompatible surfaces a projection read failure (co2 #2) as a distinct projectionReadFailed
cause (carrying the failed query) instead of reclassifying an evicted/failed session as trulyNotDeployed.Session-state DX (co2): explicit workspace lifecycle state on listWorkspaces() — connected | resident | parked — so a listed-but-unopened workspace (e
state on listWorkspaces() —
connected | resident | parked — so a listed-but-unopened workspace (e.g. a locally-born
child) is distinguishable at a glance, ending the "listed but session(ws) fails on first op"
footgun.NomosRef.acquire(bridge) — open a born/resident ref directly:
await outcome.bornRefs.single.acquire(bridge) (sugar over acquireSession, keyed by the
ref's workspace).NomosSession.isConnected + assertConnected() — the fail-at-bind guard: a clear, actionable
StateError instead of an opaque "session is not connected" on the first read/write.^0.55.0 pins valid, no generated-client re-pin needed.Add deriveWorkspaceName(namespace, key) — re-derive the workspace name a keyed birth (birth.keyed) produced, so a born workspace is addressable from i
deriveWorkspaceName(namespace, key) — re-derive the workspace name a keyed birth
(birth.keyed) produced, so a born workspace is addressable from its key with zero persistence
(byte-identical to @githolon/dsl + @githolon/client; contract-tested vectors). Replaces hand-rolled
<x>WorkspaceFor<Id> helpers.bridge.issueDelegationCert({signerSecret, grantorId, relation, subject, epoch, certChain}) —
issue a role-delegation cert (the .delegatedRole() lane) from the public client; deliver via
acceptDelegatedRole. Runner bundle rebuilt.Security: enrollSigner self-binds (device can only enroll itself; cross-principal forgery closed by construction, offline-secure). Client lifecycle fi
nomos.session.disposed, and query()/queryById() throw on a read-forbidden
verdict. Per-offer authorSecret threads to the signing path. Requires bundle >= 0.80.0.Runner-bundle floor -> 0.79.0 (the fixed-group npm lift; 0.54.1 was published mid-release with the 0.78.1 floor — runtime-equivalent, this aligns the
Fix: principal normalization mismatch in signer recovery — enrollment wrote identity:user: #signer (the kernel-canonical captured principal) while the
identity:user:<uid>#signer (the kernel-canonical captured principal) while the posture/preflight
reads stripped user: and reported false missing-signer-enrollment immediately after a
successful repair. One canonical normalizer now routes every surface; co2's five-step acceptance
(repair → immediate enrolled:true → canAuthor ok → birth admits) is the regression test, with
user:-shaped principals, proven failing-then-passing. Typed authz diagnosis now also rides the
createWorkspace relay (no more generic 422).Parent-signer recovery (the reborn-parent scar): ensureParentSignerEnrollment(...) — idempotent verify-and-repair of identity: #signer on a configured
ensureParentSignerEnrollment(...) —
idempotent verify-and-repair of identity:<uid>#signer on a configured parent (one relation read
when healthy; lawful repair via the discovered signing directive — enrollSigner pre-warrant, the
keyless enrollFirstDevice lane on a warranted parent); parentSignerEnrollment(...) posture read;
devicePublicOf(secret).canAuthor(directiveId, ...) preflight — evaluates the gate's premises read-only and returns
the typed verdict ({actor, keyHash, cause}) BEFORE the user fills a form;
NomosSession.canAuthorTyped throws the typed error.nomos.authz.* typed errors (see nomos_types 0.4.0). Requires the
paired runner bundle >= 0.78.0.Stale-baked-bundle detection. The runner bundle stamps its release version into the ready frame (build-time injected — it cannot lie); the bridge refu
ready
frame (build-time injected — it cannot lie); the bridge refuses an older or pre-stamp bundle at
boot with the typed StaleRunnerBundle naming found/expected and the flutter clean remedy.
Flutter silently keeping an old baked bundle across a pub upgrade is now a one-line error at app
start instead of behavioral archaeology. allowStaleRunnerBundle: true is the deliberate
mixed-version escape hatch. Requires the paired runner bundle >= 0.77.1 (nomos_flutter 0.53.7).Offer ack decoupled from watch fan-out (co2's 2.08s 3×3-grid report): the durable acknowledgement (plan + gate + fold + git write) resolves before any
recentSpans/spanEvents with no new API: payload-encode,
compat-preflight, bridge-ipc, gate-fold, watch-nudge, response-delivery (git-write is not
separable client-side — plan+gate+fold+write is ONE wasm call). Older runner bundles degrade cleanly
(no bridge-leg spans).The burn-down wave. Dead-letter queue surface on the session plane: deadLetters(), retryDeadLetter(), discardDeadLetter(), salvage(), absorbSalvage()
deadLetters(),
retryDeadLetter(), discardDeadLetter(), salvage(), absorbSalvage() — with the local-only
retry/absorb fixes and the salvage-shape parking fix (refused work is NEVER silently dropped).
nomos_headless.dart exports the full session surface. Requires Nomos Cloud ≥ the 2026-07-11
burn-down deploy for the fleet DLQ sweep lanes (/dlq-summary, /dlq-sweep) and the
content-addressed large-deploy staging lane.Structural: the session-delegation-gap class is closed. All event-dispatch registries (watch subscriptions, compat watches, custody/sync/signal/flame/
_eventPlane seam that
resolves to the plane owning the message loop — the base class is correct for NomosSession
automatically, and all 17 hand-written per-method session overrides are DELETED (including the
0.48.1 watchPendingConflicts fix, whose regression test still passes — the proof). Five
latent unreported instances of the same bug fixed en passant: session.custodyEvents (dead
stream), connectedSessions (empty), connect()-on-session state stamping, checkCompat()
caching, noteLocalSpan() (dead buffer). A source-level tripwire test fails the suite if a
future Stream-returning method bypasses the seam.No silent hangs — the standing harness property. Every NomosTestHarness lifecycle phase now has a deadline (overridable via the new phaseTimeout param
NomosTestHarness lifecycle phase now
has a deadline (overridable via the new phaseTimeout param) and throws a typed
HarnessPhaseTimeout naming the phase (e.g. "3b: keyed reconnect of 'catalogue'"), workspace,
elapsed time, the awaited bridge op, and likely causes — a wedge is a 30-second named exception,
never a 40-minute bisection. Every phase logs terse enter/exit diagnostics. Disposal deadline
breaches are logged, not thrown — teardown always completes.deviceKeyed cluster hang report): harness phase 3b
(keygen + keyed reconnect) had no timeout and no diagnostics — any wedge there hung silently
after "4 session(s) connected". Additionally two runner/realm defects fixed: the stale session
record stayed routable during an async re-open (concurrent ops could hit the disposed holon —
now an atomic replace with a fast typed refusal in the window), and a re-open with new
credentials but no restoreFrom silently kept the OLD identity (the fresh authorSecret was
never installed) — an identity-bearing option change now forces an in-place re-mount over
resident custody.cluster(deviceKeyed:) completes, devicePublicKey
populated, colocated attested read signed by the re-opened key, disposal completes.Fix: local-only `autoSync()` deadlocked the multi-workspace plane. A local:// session's autoSync registered the full cloud machinery (doorbell WebSock
autoSync() deadlocked the multi-workspace plane. A local:// session's
autoSync registered the full cloud machinery (doorbell WebSocket retry loop, fallback timers,
intent-offer POSTs that could never land) — the future never completed, the runner dispatcher
starved, sibling queries and listWorkspaces() hung, and teardown wedged. autoSync() on a
local-only session now registers nothing and returns immediately; sync() is a true no-op
(localOnly: true summary); a local:// holon performs ZERO network attempts. (co2's acceptance
test implemented verbatim; failed before, passes after.)acquireSession(workspace, {ifAbsentCredentials}) — atomic single-flight session
acquisition: reuses a connected session, joins an in-flight open (concurrent calls yield the
same handle, one connect), opens local-only for workspaces the plane already knows
(mounted/parked/resident custody — credentials never invoked), and only calls
ifAbsentCredentials (exactly once) when a genuine cloud open is required.Fix: `NomosSession.watchPendingConflicts()` never emitted. The session overrode every other reactive read to register on the parent plane (which owns
NomosSession.watchPendingConflicts() never emitted. The session overrode every other
reactive read to register on the parent plane (which owns the message loop) but omitted this one —
a session-bound generated client's conflict stream registered on the session's own dead controller
registry and never delivered an event. Now delegates like watch/watchById/watchActivity.
Regression test: a session-level subscription must emit its first snapshot. (Reported by co2 with
the exact fix — thank you.)Root-bridge generic writes (offer/offerDirective/offerIntent/offerCreates/createWorkspace) are @Deprecated in app code — kept for CLI/admin tooling; t…
NomosSession: XClient.bind(session) async preflight factory (structural interface
compat, typed DomainClientSessionMismatch at construction), all dispatch through the session,
births infer the parent from the session (no loose parent strings), engine.follow(NomosRef)
mounts by ref, NomosOfferOutcome.bornRefs. The kernel's generic "no active installed law declares
domain 'x'" is wrapped into the context-rich DomainNotInstalledForSession (session identity, both
workspaces, active domain keys/hashes, the four possible causes).offer/offerDirective/offerIntent/offerCreates/createWorkspace)
are @Deprecated in app code — kept for CLI/admin tooling; the session-bound generated surface is
the path.NomosSession.pendingConflicts() / watchPendingConflicts() — the maintained Surfaced-conflict
"decisions needed" read (derived, not drained).resetWorkspaceCustody, seedWorkspaceFromDeployJson, assertDomainInstalled,
session.assertCompatible(XClient.interface).@githolon/dsl 0.72.0 codegen.Fix: `NomosBridge.createWorkspace` hardcoded `domain: "workspaces"` in the underlying signed offer — a tenant birthing through their OWN platform's cu
NomosBridge.createWorkspace hardcoded domain: "workspaces" in the underlying signed offer —
a tenant birthing through their OWN platform's custom law (e.g. a birthEstateWorkspace directive under a
co2_platform domain) was refused, because the sealed intent always claimed domain: "workspaces"
regardless of which law actually declares the requested directiveId. Added a domain parameter
(default "workspaces", fully back-compatible) — call
bridge.createWorkspace(domain: 'co2_platform', directiveId: 'birthEstateWorkspace', domainHash: ..., ...)
to birth through a custom platform law. This release was overdue: the fix landed in nomos_flutter
0.52.2's bundled JS runtime, but this Dart-level API surface lives in nomos_client and was never
republished alongside it — a real release-process gap, not a client-side workaround. Requires
nomos_flutter >= 0.52.2 to match the bundled runtime behavior.Custody lifecycle on NomosBridge/NomosSession: connect(..., onCustodyBreak: CustodyBreakPolicy), custodyStatus(), the custodyEvents stream, resolveCus
NomosBridge/NomosSession: connect(..., onCustodyBreak: CustodyBreakPolicy),
custodyStatus(), the custodyEvents stream, resolveCustodyBreak() (the ask lane — put the decision in
front of the user), salvagedIntents/reofferSalvaged/discardSalvaged. A rebirth/supersession is a
first-class typed event: named truthfully, decided by the app, local work never silently adopted nor lost.
Requires nomos_types >= 0.1.4.offerOutcome(...) — the one outcome-returning offer lane generated clients now call for EVERY directive: returns NomosOfferOutcome with workspace-stam
offerOutcome(...) — the one outcome-returning offer lane generated clients now call for EVERY directive:
returns NomosOfferOutcome with workspace-stamped created (NomosCreated gains workspace + a
NomosRef get ref view). Activity raw rows carry created + workspace. Requires nomos_types >= 0.1.3.Activity-feed runtime reads on NomosBridge/NomosSession: activityLog({base, limit}) — the committed intent log as raw rows {intentId, domain, directiv
NomosBridge/NomosSession: activityLog({base, limit}) — the committed
intent log as raw rows {intentId, domain, directiveId, actorSubject, occurredAt, payload} (decoded
payload; the verified author; the physical HLC) — and watchActivity({base}), a stream re-deriving the
feed on every sync tick. Generic (raw Maps); the generated renderActivity (from directives' declared
.activity() metadata) types them into ActivityEvents. Requires nomos_types >= 0.1.2.NomosBridge.foreignReader({cloud}) — a NomosForeignReader backed by the device's multi-workspace bridge plane, so a generated ForeignRef (t.foreignRef
NomosBridge.foreignReader({cloud}) — a NomosForeignReader backed by the device's multi-workspace bridge
plane, so a generated ForeignRef (t.foreignRef) resolves against real data: it mounts the foreign
workspace on demand (connect(session: ws, allowUnborn: true), idempotent) and reads it
(session(ws).queryById(id)); watch re-reads on each sync tick. A locator resolver, not a foreign key —
the foreign holon is mounted only when you resolve. Requires nomos_types >= 0.1.1 (the ForeignRef types).Nothing published for this version
NomosTestHarness emits named phase-progress diagnostics (install → spawn runner → await ready → connect, plus per-session progress in cluster) and eac
NomosTestHarness emits named phase-progress diagnostics (install → spawn runner → await ready → connect, plus per-session progress in cluster) and each connect() carries a connectTimeout (default 120s) that throws a NAMED remedy instead of hanging — so a multi-test AppSim run can tell install vs runner-wait vs session-block vs deadlock (co2 feedback).connect(maxMounted: …) — the realm's mounted-workspace budget (LRU park/remount above it); useful on memory-constrained devices holding many local wor
connect(maxMounted: …) — the realm's mounted-workspace budget (LRU park/remount above it); useful on memory-constrained devices holding many local workspaces.NomosTestHarness.ephemeral now connects a DECOY session alongside the workspace under test, and harness.bridge is a NomosSession HANDLE pinned to it (existing tenant tests work unchanged). Sole-session inference therefore never silently passes under the harness — an op that forgot its session refuses in your first test with the same multiple sessions connected — pass session a real multi-workspace app raises. Opt out with decoySession: false.NomosBridge.open(...) — connect + pinned NomosSession handle in one call (final home = await bridge.open(workspace: …); HomeClient(home)): the recommended plane/handle shape; the bare bridge methods remain one-workspace sugar.Multi-session compat surface: watchCompatibility takes an optional session; NomosSession pins its compat watch, compat, and onLawChanged to ITS worksp
watchCompatibility takes an optional session; NomosSession pins its compat watch, compat, and onLawChanged to ITS workspace (per-session lawChanged scoping — previously a multi-session plane's compat verdict was whichever session synced last, and a session's compat watch refused on a >1-session plane).SPLIT: the pure data core (wire types, offer codec, NomosReads, aggregate meta, schema validation, error info) moved to the new nomos_types package; n
nomos_types package; nomos_client depends on and re-exports it, so existing imports are unchanged. Frontend/UI code can now depend on nomos_types alone.Doc fix: NomosBridge.attestedRead docs now match the runtime — the call answers { entry: {queryId, result, attestation: …} }; pass result['entry'] as
NomosBridge.attestedRead docs now match the runtime — the call answers { entry: {queryId, result, attestation: …} }; pass result['entry'] as one offerDirective attestations element.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
SPATIAL READS: NomosBbox + NomosBridge.spatialWithin(spatialId, bbox) + watchSpatial(...) — the R*Tree probe surfaces on the bridge; generated clients
NomosBbox + NomosBridge.spatialWithin(spatialId, bbox) + watchSpatial(...) — the R*Tree probe surfaces on the bridge; generated clients (tooling ≥0.46) emit typed sitesByBounds({required NomosBbox bbox}) + watch accessors.NomosFieldMeta.fromBirth — the registry surfaces BIRTH-PRESENCE LAW (.fromBirth() fields, tooling ≥0.42): a gate invariant guarantees the field presen
NomosFieldMeta.fromBirth — the registry surfaces BIRTH-PRESENCE LAW (.fromBirth() fields, tooling ≥0.42): a gate invariant guarantees the field present on every row, and the generated read models type it non-nullable.RUNTIME AGGREGATE METADATA: NomosAggregateMeta / NomosFieldMeta / mergeAggregateMeta (src/aggregate_meta.dart) — the support types for the generated p
NomosAggregateMeta / NomosFieldMeta / mergeAggregateMeta (src/aggregate_meta.dart) — the support types for the generated per-domain const Map<String, NomosAggregateMeta> <domain>AggregateMeta registry (nomos-compile ≥0.41 tooling). Generic surfaces (history/audit UIs, op renderers, in-app agents) resolve NomosAggregateMeta.typeOfId(op.aggregate) → field kinds, enum wire values, VO/variant names, and the typed fromJson decoder — the compiler's knowledge emitted as data, derived from the law's own declarations.