Review transactions and errors
Inspect observed steps, failure details and verification results.
#Transaction summary
Review the actual starting point, significant observed steps and outcome. The summary is prepared from source records; it is not a new LLM interpretation. Expand cards to inspect inputs, outputs, models, sources, tools and explanations.
#All records
Use All records for technical review. Filter by AI, HTTP, lifecycle or error observations, and use the first/last-record controls to navigate. Original content can contain more detail than the shortened summary.
#Understand an error
Consider the error type, recorded explanation, service, time and related step together. ReadTimeout indicates that reading a response did not complete within the timeout. RemoteProtocolError identifies a remote protocol problem. If only the error type was supplied, Sigillum does not invent a root cause.
A dependency failure may remain in the trace even when a later retry succeeds. Distinguish an individual step failure from the transaction’s final outcome.
#Hashes and technical identifiers
Hashes, span IDs and model-file revisions may appear in technical details. Collapsing these fields in the summary changes presentation, not the underlying evidence.
#Verification tools
Record integrity checks the recorded content against its seals. Compare with institution record checks selected fields against the source. Download transaction evidence provides historical verification material. These results have different meanings.