Files
mesh-sdk/src/index.ts
T
jschoubben 0d546d37f3 T-1, T-2: W1.11: the TypeScript side holds a seat as the Go side does
A TypeScript holder, the forge module first, must judge a verb's caller by the runtime's proof, say its seat's events
and answer its first views' read and ask-again tools (design 47, The forge module's tools come from mesh-sdk's
TypeScript side; G-F1 option A). The stdio session now hands each tool the caller and call id the runtime wrote in
_meta (callers.callerOf, the Go rules for Callers and VerbCallers), binds the runtime for seatPublish over
mesh/seat.publish and config, and views gains the Follower and its two status tools over the state first-views.
@novox/mesh-sdk 0.1.19.

Builds: design 47 G §196, §200, §336

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
2026-11-11 10:51:07 +01:00

19 lines
995 B
TypeScript

// @novox/mesh-sdk — the stable spine a module's own code builds against (novox/hq ADR 0039).
//
// Import the area you need directly (`@novox/mesh-sdk/tools`, `/provider-loop`, …) or the whole
// surface from here. Everything specific to one module — its API client, its tool implementations,
// its create-a-resource adapter — lives in the module, never here.
export * from "./contracts/index.js";
export * as tools from "./tools/index.js";
export * as providerLoop from "./provider-loop/index.js";
/** @deprecated The provider loop's name before design 57 (novox/hq issue 678): `providerLoop`. */
export * as provisioner from "./provider-loop/index.js";
export * as messaging from "./messaging/index.js";
export * as events from "./events/index.js";
export * as primitives from "./primitives/index.js";
export * as state from "./state/index.js";
export * as runtime from "./runtime/index.js";
export * as callers from "./callers/index.js";
export * as views from "./views/index.js";