QR Studio Ultra · Phase 18

Intelligence Methodology Studio

A transparent metric dictionary for the reporting system: what each score means, how it is calculated, where the data comes from, and what the limits of interpretation are.

Score Studio Executive Brief Report Hub Dashboard

Model chain

Data path

  • Scan event starts in the QR redirect flow.
  • Scan stats are aggregated into dynamic_qr_scan_stats.
  • StatsModel normalises totals, time series, and ranking buckets.
  • Studios read the model and build reports without mutating live dashboard state.

Interpretation rule

No hidden magic

Every intelligence view should be traceable back to StatsModel fields. The reporting layer can rank, aggregate, classify, and export, but it should not silently invent measurements that do not exist in the scan data.

Metric dictionary

Core definitions

Metric Formula / Source Meaning Limit

Campaign score

Weighted model

  • volume: 30%
  • velocity: 22%
  • spread: 14%
  • momentum: 16%
  • audience: 10%
  • attribution: 8%
  • risk penalty: subtractive

Classes

Score bands

  • Elite 85-100
  • Strong 70-84
  • Developing 50-69
  • Weak 30-49
  • Dormant below 30 or dead

Attribution

Source logic

  • Direct means no usable HTTP referrer.
  • Referral - domain means a referrer host was present.
  • Search, social, messaging, and email labels are derived from referrer host patterns.
  • Camera-app scans commonly register as Direct.

Client profile

Device/browser/OS

  • Device, browser, and OS come from the request user-agent.
  • Bot and preview services may appear as Bot / Preview.
  • The system stores a hash rather than raw user-agent text.
  • Client detection is useful for aggregate patterns, not personal identification.

Governance

Reporting constraints

The standalone studios are intentionally isolated from the live dashboard. They should fetch models, render reports, export files, and stop. They should not introduce dashboard observers, live sync loops, DOM mutation engines, or database writes.