Skip to content

README.md

Latest commit

 

History

History
62 lines (43 loc) · 2.41 KB

README.md

File metadata and controls

62 lines (43 loc) · 2.41 KB
Raw

Protocol overview

Draft normative document. Subject to breaking change before the first release.

ThreadMesh defines coordination semantics between addressable tasks. It does not prescribe a network transport.

The draft is executable but incomplete. Schemas and fixtures cover envelopes, capabilities, dispositions, grants, summaries, audit events, adapter submission receipts, and selected state transitions. The remaining milestone and review gates are summarized in the project status.

Required concepts

A conforming implementation provides:

  • stable task identities;
  • an advertised capability document;
  • explicit task relationships or authorization grants;
  • message envelopes with provenance and expiry;
  • idempotent delivery;
  • receiver dispositions;
  • freshness checks for steer and interrupt;
  • an audit trail for state-changing requests;
  • explicit unsupported behavior.

Intent semantics

notify

Informational. A receiver MAY display or store it without making it model-visible. It MUST NOT change the active objective merely by being delivered.

suggest

Advisory. A receiver MUST retain the right to accept, reject, defer, or mark it stale. Peer coordination defaults to this intent.

steer

State-changing. A receiver MUST verify authorization and freshness before submitting it to an active run. Delivery alone is not adapter submission.

interrupt

Cancellation request. A receiver MUST verify elevated authority and report whether cancellation succeeded, failed, or was only requested. It MUST NOT be downgraded to ordinary prompt text.

Documents

Current conformance boundary

npm test validates schema compilation, 55 positive/negative fixture cases, 7 transition cases, an authenticated serialized JSON-RPC path, a restart-safe local event stream and redacting provenance inspector, crash-safe submission reconciliation, typed partial interruption, real Ed25519 attestation verification against a pinned conformance trust anchor, and two mock harness profiles. It does not yet validate production network authentication, trust-store operations, or real-product cross-harness behavior.