nomos_types 0.1.2

Pure kernel wire/data types for Nomos Dart frontends — no transport, no bridge, no runtime. The hand-written serde-JSON-compatible types plus the offer codec, reactive read engine, schema validation, [...]

0.1.2

• Activity-feed runtime types: ActivityEvent (the shared activity row — kind/actor/occurredAt, rendered title+message, stable titleKey/messageKey + params for localization, typed refs, category/icon/ severity, domain/directiveId provenance), ActivityRef, ActivitySeverity, renderActivityTemplate. Consumed by the generated renderActivity/describe/describeHistory. Purely additive.

0.1.1

• Add t.foreignRef runtime types: ForeignRef<T> (a typed cross-workspace locator), NomosForeignReader / NomosForeignWorkspaceReader, the sealed ForeignResolveResult<T> (ForeignFound/ForeignNotFound/ ForeignDenied/ForeignUnreachable), and ForeignAttestation. Generated read models type a foreignRef field as ForeignRef<Target>; .resolve/.resolveResult/.watch/.exists are the informational lookup, .attest is gated on the attested-read lane. Purely additive.

0.1.0

• Initial release. The pure-data core split out of nomos_client: kernel wire types, the offer codec, NomosReads, the tri-state NomosSlot, aggregate metadata, schema validation, and the data-only error/trace types (NomosBridgeError, NomosErrorInfo, NomosTraceContext) plus the typed diagnostics. No transport, no bridge, no runtime — generated per-domain TYPES files depend on only this.