Crate heddle_thread_api 

Native v2 client design. Endpoint ownership, credentials and connection discovery belong to the application; this crate never obtains a Weft token.

Modules

authority

The same client-minted Biscuit rules at device and hosted boundaries. The application supplies roots already attached to the owner/account and a resolved spool path. No key or authority is minted by this verifier.

authority_admission

boundary_acceptance

Structural acceptance evidence matching, never executor trust or fresh authority.

collaboration

Portable collaboration commands. Original parent records reconstruct both causal frontiers; callers never translate UI version tokens into proofs.

content

Bounded full-blob reads at one exact revision. Large/ranged transfers use the same generated ContentServiceReadContent stream and a caller-owned sink.

contract

Frozen Thread-oriented contract; endpoint support is negotiated.

creation

Prepare creation once and retain the original signed identity for retries and later replication. Preparation performs no network or repository I/O.

credentials

Caller-supplied request credentials, independent of repository storage.

evidence

Typed immutable evidence codecs shared by hosted and device callers. Signature verification does not establish current account or Spool authority.

fetch

Native source downloads retain original Thread identities and causal proofs. Pack chunks are staging bytes: install only after the verified Complete frame.

live_replication

Continuous, bounded replication on caller-authenticated protobuf streams. One feed is shared by every observer/replicator of a local Thread. Incoming metadata writes never move a checkout or install unrequested source blobs.

observation

Deliver bounded, committed changes; never expose half a snapshot as a view.

pairing

Pairing proves each actual receiver key, never independent account authority.

publication

Flow-controlled source publication. Sending and receiving run together so server checkpoints cannot block an upload on a full response stream.

replication

A bounded, transport-neutral causal exchange shared by device and hosted endpoints. The RPC adapter supplies the verified request scope.

replication_rpc

Known-Thread replication on a directly authenticated Iroh connection. The host supplies its resolved owner/account authority and admission facets. Unknown Thread creation and source-object transfer have separate boundaries.

request_proof

Portable v2 request PoP. Hosts supply the effective key from an already verified Biscuit and separately enforce account attachment, scope, current revocation and durable nonce consumption. This check grants no authority.

root_attachment

Portable evidence that a root-derived credential holder owns an Iroh endpoint. The credential is private verification input, never part of the public record. An attachment establishes a locator binding, not permission for future work: verify each current request’s complete Biscuit chain and revocations separately.

rpc

Typed operations derived from the protobuf method descriptors.

thread_control

Prepare portable Thread edits directly from an observed field frontier. Signing is local; the resulting typed request is retained unchanged for retries.

thread_ownership

Exact ownership proof framing. Verification never enrolls its carried keys.

transport

Transport-neutral credentials and errors for typed Thread RPC clients.

Structs

Remote

One authenticated source. A combined Thread retains one source per endpoint; a hosted action is sent directly to the Weft source, never via a device.

Thread

Traits

Rpc

Functions

is_reopen_retryable

Weft fail-fasts a stale exact selection with these retryable signals. A bare resend of the same selection would observe the same Aborted.