Dashboard
Command center for link trading, verification, retention, and intelligence
A dense operations surface for the full workflow: discovery, requests, pending states, verification evidence, active monitoring, CPU-only scoring, recommendation logic, and persistent workflow state.
Intelligence-ranked inbox
Prioritized requests
Requests are scored from partner trust, category fit, target quality, freshness, and suspicious pattern adjustments.
| Partner | Anchor | Priority |
|---|---|---|
| velvetindex | bulk trade monitoring | 84 |
| orionpublisher | technology exchange platform | 83 |
| orionpublisher | technology exchange platform | 83 |
| camrankvault | enterprise link exchange platform | 80 |
| darkpartnergrid | trade verification workflow | 66 |
Repair queue
Break-risk trades
Active trades are ranked by health score so broken or degraded positions surface first.
| Trade | Partner | Health |
|---|---|---|
| trade-004 | darkpartnergrid | 71 |
| trade-1773427438141 | orionpublisher | 91 |
| trade-003 | orionpublisher | 91 |
Attention routing
Live alerts
Persistent workflow state now feeds the alert center directly.
Score engine live
Partner intelligence snapshot
Trust and risk are explainable, auditable, and computed without a local LLM runtime.
Trust score92
StrongAcceptance87
Completion96
Verification97
Risk score14
WatchBroken trades19
Disputes8
Hidden ratio20
Repair-first prioritization
Trade health breakdown
Critical workflows stay evidence-backed and deterministic, with intelligence only augmenting the queue order and recommendations.
Health score71
RiskPartner trust63
Page quality84
Status66
Recent workflow pressure
Request activity trend
Recent request events are bucketed from persisted state history.
Recent scoring activity
Trade health trend
Health snapshots show how often trade state is being recalculated or remediated.
Execution impact
Campaign outcomes
Campaign completion and delivered outcomes are aggregated from live persisted campaign state.
Operational throughput
Bulk efficiency
Bulk run volume and target coverage are tracked from execution logs.
Execution routing
Bulk scope distribution
Scoped runs show where the operational engine is spending effort.
History-derived load
Operational state movement
State and score history continue to drive the command center as real persisted workload grows.