ReadonlychunkOrdered storage shared by the node's reader and writer.
ReadonlynodeOwning node map, or null for a standalone node.
Low-level consuming cursor; prefer next for typed values.
Codec registry currently used at the application boundary.
Low-level producing cursor; prefer put for typed values.
Iterate typed values until finality, closure, or failure.
Tee stored writes to a transport; send admission is not peer delivery.
Cancel both halves of this local node object.
Stop this node's independent consuming cursor.
Abandon queued writes and stop the producing cursor.
Consume and deserialize exactly one whole unary value.
Consume exactly one whole value's fragment and validate its terminator.
Use this for unary action ports; streaming ports should call next.
End the sequence: mark the logical end of the data, and close the writer.
The one call an ordinary producer needs. value is written as the final
fragment; omitting it (or passing null/undefined) writes a null
terminator instead, which is the form to use once the last visible value
has already gone out with put. Unless close is false the writer
is closed too, so readers waiting for data that can no longer arrive are
released and a peer's mirror of the node closes as well.
It does not wait: the write and the close are carried out by the writer's
own pump, so a producer can finalise and move on. Nothing is swallowed -- a
failed write or close is reported through getWriterStatus. Pass
wait: true to resolve only once the store has confirmed both.
Optionalvalue: unknownReturn the stable id used by fragments, actions, and sessions.
Copy the current independent read-cursor options.
Current independent read-cursor status.
Structured writer-abort status, or null.
Copy the current buffered writer options.
Current buffered writer status.
Whether the producing half can accept another value.
Read the next raw fragment, or null at the clean end of sequence.
OptionaltimeoutMs: numberSerialize and persist one application value, respecting writer backpressure.
Persist a fragment carrying its own sequence and continuation marker.
Replace and rewind the independent read cursor, optionally from an offset.
Optionaloptions: ChunkStoreReaderOptionsSet default MIME/type constraints for subsequent typed reads.
OptionalexpectedTag: stringReplace options used by the next reader reset.
Replace the codecs used by subsequent typed reads and writes.
Replace writer policy before any write has started.
Await outstanding writes without closing or adding a final marker.
StaticcreateCreate a backing store for nodeId, then build its reader and writer.
StaticfromBuild a node over an existing store, preserving its data and id.
One ordered, typed value sequence flowing through an A11 application.
Action inputs and outputs are AsyncNodes. The writer serializes application values into sequenced chunks, persists them through a ChunkStore, and optionally tees stored fragments over a wire stream. The reader follows that same ordered log and deserializes values as they arrive, so an agent can expose tokens, audio frames, tool events, or a unary result through one protocol.
End the sequence with finalize: it marks the logical end of the data and closes storage. Finality and closure remain two distinct facts -- see the AsyncNode lifecycle guide -- and close is the rarer half on its own, for a producer that cannot say which chunk was last. Failures should use abortWithStatus so local and remote readers see why the sequence ended.
Example: Write values and read them one-by-one.