Signal Column Flow
Column-based explanation surface showing how raw session signal becomes attributed entities and then clearer actions.
Skill Proof Run
wf1 · testing whether a left-to-right column view can make reduction feel visible instead of magical.
Many raw signals feed a smaller attribution layer and then resolve into a readable action vocabulary without pretending everything is equally authoritative.
Authority Rail
Evidence To Action Canvas
Raw Signal
dense evidence substrate
Actor / Entity
smaller attribution layer
Action
user-readable explanation
Path Inspector
Selected Path
MCP tool call path
A protocol-observed MCP request combines with app-reported tool semantics to become the clearer action label `Call MCP tool`.
Strongest Source
Observed via MCP request/response evidence.
Supporting Sources
Agent OTEL `tool_result` adds semantic naming and duration.
Reduced MCP server entity keeps the path readable.
Outcome column, when enabled, anchors the action to a concrete resource.
Explanation Notes
What the page proves
The same session can be described as evidence, entities, and actions without changing the underlying story.
Why the shape works
The middle column absorbs complexity so the right side can read like explanation instead of log playback.
What to watch
Moving right should mean more legible, not automatically more true.