Trace

See every governed call in this project as a tree, with what the gate decided about each one.

This panel collects nothing. The capability gateway already files every call it governs, with the run it belongs to, its place inside that run, the rule that decided it and the arguments the decision was bound to; the policy kernel files every answer a person gave beside it. Trace reads that back and draws it, so a project that ran an agent last week has its runs the moment this extension is installed.

What you can do

• See the runs — newest first, each named after the capability the run is, with who started it, when, how many calls it made and whether any were stopped.
• Open a run — the calls as a tree in the order they began, each with the gate's verdict, its duration, and the rule's own sentence when it was stopped.
• See the decisions — who approved or declined a held call, and with what scope, under the run it was about.
• Filter by who asked — one chip per actor that started a run, so the calls an external client made over ivyx serve read apart from the window's own agent.
• Ask programmatically — trace.read returns the same runs through the capability gateway, for an evidence package, an agent asked what it did, or another panel: the Monitor draws its span tree from it. With io: true each call carries a bounded summary of what it was given and what it answered.

Getting started

Open the panel from the palette (Trace: Open), through the trace.open capability, or from the Trace row in the agent window's rail. In IVYX Studio it opens in the content drawer beside whatever is on screen; in the agent window it opens as a tab in the side panel. Escape closes it.

The panel follows the trail while it is open: a call that finishes while you are looking appears without a click.

What it does not do

It does not list its own reads. A run rooted at trace.open or trace.read, or at the reveal of this panel, is left out — a reading of the trail is not something that happened in the project, and listing it would make opening the panel history.

It does not read revocations. Every approval on ivyx is followed by a revocation a millisecond later by design (a once-grant minted around the single retry), so a panel that listed them would say "approved, then withdrawn" about every approved call it ever saw.

Where the rules come from

The fold is the CLI's (ivyx runs list): the audit timestamp is a completion, so a run's root is the call whose parent is outside the run and never the earliest record; a decision is not a call; a refusal is not a failure. They are carried here rather than called because this window reads the trail in-process and sees the in-memory ring the CLI cannot.