nomos_flutter library

nomos_flutter — supply Flutter platform capabilities to the shared Nomos Peer Office.

A domain dev writes a powerful, polymorphic TypeScript domain, runs nomos compile, and gets a typesafe Dart facade. Peer Office owns lifecycle; this package supplies Flutter-specific credentials, storage, networking and native execution ports without generating a second application runtime.

The platform shell obtains a Peer Office binding, then binds the generated facade. No generated widget opens custody, installs law, or starts a kernel.

Classes

NomosApprovedModel
The law model an application release approves, supplied once at the application's Reception. Every field is required: the office refuses to adopt without the package identity, the domain keys it observes, the attributed reason the kernel's transition demands, or the package bytes a child must stage — none of them can be invented later.
NomosClientInstallation
App-owned metadata; the runtime never guesses a package version or channel.
NomosClientInventoryReporter
One coalesced, bounded heartbeat. send supplies auth/HTTP using the app's configured console; it must impose its own transport timeout/cancellation. This class holds no credentials and persists no business data.
NomosConsoleEnrolment
Where an enrolled principal's device key is enrolled: the application's console enroller, its tenant and the enrolled provider scope declared in law. Application configuration, never authority.
NomosLocalCopies
This device's local workspace copies, for the application bound by the nearest NomosReception: which were re-founded remotely, what dropping a copy would lose, and the drop itself (the copy is refetched from its provider; device keys, credentials and other workspaces are untouched).
NomosLocalCopyDropPreview
What dropping a workspace's local copy would discard. Obtain it from ReceptionLocalCopies.preview; pass it back to ReceptionLocalCopies.drop, which drops exactly the previewed copy and nothing newer.
NomosLocalWorkspaceCopy
One workspace this device holds or follows, as its local copy stands.
NomosPeerRuntimeHost
The process-local Peer Runtime lifetime for a Flutter application.
NomosPreservedLocalCopy
A local copy replaced by a refetch and kept aside under refs/heads/custody-preserved/: never deleted, never merged.
NomosReception<TApplication>
Stateless Flutter projection of one peer-owned application binding.
NomosRuntimeIdentity
What this device's resident peer is actually running, observed from the peer itself: the linked native kernel and installed Peer Office runtime identities, and every workspace in the peer's local inventory with the law its own custody currently serves. The app build never decides a workspace's law; this reports it.
NomosSpanEvent
NomosWorkspaceRebirth
The provider now serves this workspace from a different genesis than this device's local copy: it was re-founded ("reborn") remotely. Sync refuses to merge, rebase or offer across geneses and schedules no retry. Dropping the local copy (ReceptionLocalCopies.drop) is the fix.
ReceptionLocalCopies
Fixed Reception capability over this device's local workspace copies. A local copy is a droppable cache of the provider's custody: dropping one replaces only that workspace's local custody, projections and indexes, then refetches it from the current provider. Device keys, credentials, the identity store and every other workspace are untouched.
SyncStatus
Disposable UI projection of typed peer-runtime sync observations.
WorkspacePreparationReport

Enums

CustodyBreakPolicy
The mount's declared response to a custody discontinuity.
NomosSpanPhase
One typed, authority-free observation of peer work.
SyncPhase
WorkspacePreparationStep
A disposable, read-only projection of work reported by the Peer Office. Absence means unobserved, not ready. No application action is driven by it.

Functions

nomosRunInBackground<T>(Future<T> body()) → Future<T>
Runs body as background work on the resident peer. Every runtime request it makes, including the continuations it awaits, queues behind the application's own requests and waits for the foreground to be quiet (see NativeWorkerQueues). For work the user did not ask for on this screen, such as prefetching the estates a Home lists.