Use Explain This Output from a QCDR Page Scan

Explain This Output turns a Page Scan row into the normal Discovery selection workflow. QCDR selects that actual DOM element, builds its fingerprint and page context, ranks local runtime evidence, and—while the Discovery authorization is still valid—checks relevant stored Joomla/QCDR evidence.

The goal is evidence-based attribution, not an automatic claim that one candidate definitely owns the output.

Open a Scan Result

  1. Run Scan this page.
  2. Filter until you find the output you want to understand.
  3. Choose Explain This Output.
  4. QCDR closes the scan panel, selects the result's actual page element, and opens the standard inspector.
  5. Read Target Fingerprint, Page Context, and Source Evidence as separate sections.

What Happens in the Inspector

The selected element receives the same treatment as a direct click selection. QCDR records the selected value and useful DOM attributes, captures route/render context, builds a Target Fingerprint, and adds any exact private runtime boundaries or late-DOM evidence.

It then requests stored evidence through a private same-session POST. Candidate sources can include the current article and custom fields, exact module records, active menu data, Joomla language strings, template override/shell candidates, and stored QCDR Rule/Token definitions.

Use the Confidence Labels

PROVEN evidence means QCDR observed an exact runtime boundary or event. HIGH is a strong match/correlation. MEDIUM and LOW are progressively weaker candidates. A template override existing on disk, for example, can be a useful MEDIUM candidate without proving which line generated the selected element.

Late DOM Evidence Stays Distinct

If Dynamic DOM Watch previously observed the element changing, Explain This Output carries that timing evidence into the inspector. QCDR can say the DOM changed after the watch began; it still does not invent a JavaScript filename, network response, or call stack.

If Stored Lookup Is Unavailable

Browser/runtime evidence can still be shown when the backend lookup cannot run. If the signed Discovery session has expired, however, relaunch Discovery before relying on stored-source evidence or attempting the Draft Rule handoff.

Move from Explanation to a Rule Carefully

After you understand the evidence, refine the find value, review the fingerprint, optionally enter a replacement, and open the Draft Rule. Discovery does not save or enable anything from the explanation step.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.