nomos_client 0.66.6

Nomos 2 Dart client — generated domain values, intent payloads and application lifecycle types over the typed Nomos kernel protocol and USDA custody model.

nomos_client

Dart frontend types for Nomos — the hand-written kernel wire types plus the code-generated per-domain aggregate + directive-payload types. (De)serializes the exact typed protocol the Rust kernel + projection produce/consume, and defines Dart Reception protocol the runtime (nomos_flutter) drives.

You normally depend on nomos_flutter (which re-exports Reception) rather than this package directly. Licensed under the Nomos Pre-Release License — see LICENSE.

What belongs in this package

nomos_client is a THIN client. It is the language-native presentation of a Peer Office, and it decides nothing the office decides. Only these belong here:

• the generated protobuf types and the RuntimeRequest / RuntimeResponse / RuntimeEvent transport to a Peer Office (runtime_v2_transport.dart, reception/peer_office_connection.dart, node_runner_transport.dart);
• the physical effect executors a platform shell answers — HTTP, git smart-HTTP, custody probes, device identity, credential refresh, law package;
• the generated facade binding (generated_call.dart, nms_generated_runtime.dart, application_framework_calls.dart);
• typed refusal decoding, and the projections that only fold events the office already published (sync_status_projection.dart, operation_receipts.dart, result_usda.dart);
• the test harness (test_harness.dart, dev_cloud.dart, testing/).

These do NOT belong here, and a review should refuse them: workspace lifecycle decisions, ceremony sequencing, retry/fallback/backoff policy, custody or sync orchestration, model-lifecycle decisions, workspace name-prefix logic, and JSON probes of the host. They belong to a named Peer Office desk. architecture/reception_peer_office_boundary.md carries the trap table of patterns already removed and the short list of office procedure still resident here; add to that list rather than adding a second client-side lane.