Processing Core

Flow Debugger

The debugger should teach the chain first, then let you inspect one trace and one stage at a time.

Trace Surface

Understand the chain, select one trace, then inspect the exact stage that is missing or degraded.

This page now emphasizes the runtime chain and the selected trace rather than leading with a wide technical table.

Trace rows

current query

Sample trace

summary surface

Warnings

selected trace

Semantic findings

selected trace

How the chain works

The main path is fixed and explicit: source change or scheduled research enters one shared chain, then AI and human execution branch and merge back into result, feedback, and evaluation.

source_change or scheduled_research_trigger -> Analysis -> Signals -> Routing -> Targets -> Tasks -> Execution Decision -> AI/Human branch -> Result Event -> Feedback -> Evaluation

Trace filters

Use explicit filters and pager controls; mobile no longer depends on hover or table scan to debug a trace.

Trace source

Trace value

Artifact filter

Artifact value

View mode

Overall state

Anchor type

Stage presence

Time window (h)

0 trace rows

Trace index

Trace rows are now card-based so you can scan anchor, state, completeness, and reason quickly.

page=1/1

No traces for this selection

The current filters do not match any trace rows, or the platform is still empty.

Pipeline trace

Select one stage to inspect evidence, provenance, lineage, and semantic audit.

Execution Decision branches here

Branches merge into Result Event