Skip to main content

Ledger

Every paranet keeps a ledger: the permanent record of every conversation between its actors. Where Netflow shows what is happening now, the Ledger holds what happened — and it keeps it after the run has finished and the page has been closed.

Use it to review activity, investigate a failure, or trace an exchange end to end.

The conversation list​

Opening the Ledger shows conversations in a table:

  • Conversation ID
  • State
  • Created at
  • Requester — the actor that made the request, with its version
  • Fulfiller — the actor that answered it, with its version
  • Subject
  • Action

Results are paged. Use the controls beneath the table to move through them, and select any row to open that conversation.

Filtering​

Narrow the list from the left panel:

  • State — completed, in progress, failed, canceled
  • From and to timestamps — a date range
  • Requester and fulfiller — by actor, and optionally by version
  • Subject and action — the skill involved. Choosing a subject narrows the available actions to that subject's.

The active filter is held in the page address, so a filtered view can be bookmarked or shared and it will open the same way for whoever follows the link.

The conversation page​

Selecting a conversation opens its full record, beginning with:

  • Conversation ID
  • Parent ID, if it was opened from inside another conversation
  • Children, if it opened others in turn
  • Creation time, state, subject and action
  • Requester and fulfiller

Parent and child links are worth following. A conversation with a parent is one actor delegating to another, and walking the chain shows how a single request spread across your paranet.

Control Flow​

A UML sequence representation of the conversation: who sent what, to whom, in what order. This is the quickest way to understand the shape of an exchange, especially one that involved several actors.

Data Flow​

A canvas of the same conversation drawn across the actors involved, with the contextual data attached to each step. Use it when the question is what was exchanged rather than in what order.

Message list​

Every message in the conversation, with its ID, time, sender and type. Select one to expand it:

  • Match strategy — how the request was routed to its fulfiller
  • Action
  • Data — as a JSON viewer or as raw text
  • Callback

For a failed conversation, the error message carries the reason the fulfilling actor reported. That is usually the fastest answer to "why did this stop".

Working with ledger data directly​

The ledger is a database, and the console is one view of it. For reporting, trend analysis, or connecting a BI tool, query it directly rather than paging through the table — the console is built for finding and reading individual conversations, not for aggregation.

Speak to your node operator for read access.