Agent-ready workflow · server
Second-Order Queue Trace
Follow stored data through workers, retries, exports, and delayed interpreters with unique stage canaries.
Entry contract
Enter with artifacts, leave with evidence.
Use when
- delayed callback
- scheduled job
- export
- moderation
- notification
Prerequisites
- controlled object
- known trigger action
- private listener if callbacks are used
MCP retrieval
Agents can search this workflow, retrieve the complete graph, or request one stage through the read-only Vulns.co MCP connector.
Draw the asynchronous dataflow
Map source, storage, transform, queue, worker, sink, retry, and cleanup.
Inputs
- observed create and recall actions
Outputs
- dataflow diagram
- Evidence gate
- Each stage has a timestamp and controlled object reference.
- Negative control
- Immediate front-end behavior is separated from worker behavior.
- Stop condition
- Do not trigger shared production jobs without permission.
Assign stage canaries
Use unique inert markers for each field and transform hypothesis.
Inputs
- controlled fields
Outputs
- transformation ledger
- Evidence gate
- Returned markers identify which path and transform occurred.
- Negative control
- One marker is stored but never recalled.
- Stop condition
- Do not use active payloads before the sink context is known.
Apply one sink discriminator
Choose callback, harmless markup, parser error, or other bounded signal appropriate to the observed sink.
Inputs
- supported sink hypothesis
Outputs
- raw sink evidence
- Evidence gate
- The signal is unique to one stage and cannot come from the initial request.
- Negative control
- Encoded or delimiter-free variant remains quiet.
- Stop condition
- No output exfiltration or uncontrolled viewer effects.
Model retries and report
Group repeated events by job attempt and state each proven edge separately.
Inputs
- event ledger
Outputs
- retry model
- bounded chain report
- Evidence gate
- Repeated callbacks are not counted as separate victims or sinks without evidence.
- Negative control
- Ambient and unsubmitted tokens remain quiet.
- Stop condition
- Clean up the controlled object and stop further retries where possible.
Related methods
Continue with the right depth.
Sources