← Workspace

RDX Playground Queries — Workability Cross-Reference

March 23, 2026

Copy-paste these into rdx-federation-stage.smecloudops.com/playground/

Run them in order. Screenshot any results.

---

PRIORITY 1: Clearance Queries (SAA/SAMP proof point)

These are the money shots. If ANY of these return clearance data

while Runway shows "Unknown," that's the gap made visible.

Sheff G — "Him" (hip-hop = high sample probability)

{
  clearancesForIsrc(isrc: "USRC12600343") {
    nodes {
      status
      clearanceType
      originalWork
      rightsHolder
    }
  }
}

Ray Vaughn feat. Ty Dolla $ign — "Water" (FEATURE = SAA relevance)

{
  clearancesForIsrc(isrc: "USRC12600494") {
    nodes {
      status
      clearanceType
      originalWork
      rightsHolder
    }
  }
}

Osé feat. Victony — "Bother Me" (FEATURE = SAA relevance)

{
  clearancesForIsrc(isrc: "USRC12600224") {
    nodes {
      status
      clearanceType
      originalWork
      rightsHolder
    }
  }
}

horsegiirL — "that's my beach!" (your proof-point artist)

{
  clearancesForIsrc(isrc: "USRC12600092") {
    nodes {
      status
      clearanceType
      originalWork
      rightsHolder
    }
  }
}

Sleepy Hallow — "Young & Dumb" (hip-hop = sample probability)

{
  clearancesForIsrc(isrc: "USRC12600495") {
    nodes {
      status
      clearanceType
      originalWork
      rightsHolder
    }
  }
}

NOTE: If these error on the sub-fields, try just:

```graphql

{ clearancesForIsrc(isrc: "USRC12600343") { __typename } }

```

That tells you if the query resolves at all.

---

PRIORITY 2: Mega-Query for Same Date Range

Compare what RDX returns vs. what the export shows.

Using the same window: March 27 – May 18.

{
  mktTimeline(fromDate: "2026-03-27", toDate: "2026-05-18") {
    nodes {
      mktProducts {
        nodes {
          title
          artistName
          streetDate
          workability {
            score
            kpis {
              nodes {
                name
                status
                weighting
              }
            }
          }
          alerts {
            alertType
            daysUntilRelease
          }
        }
      }
    }
  }
}

What to look for:

- Do the workability scores match what the export shows?

- Are there AT_RISK or WARNING alerts on the March 27 releases?

- Does RDX show any KPI statuses that differ from the export?

---

PRIORITY 3: Repertoire / Contributor Data (SAA source)

If clearance queries come back empty, try the repertoire angle.

These look for contributor/participant data that could fill SAA.

Search for Sheff G in repertoire

{
  participantSearch(name: "Sheff G") {
    nodes {
      name
      role
      recordingProjects {
        nodes {
          title
          status
        }
      }
    }
  }
}

Search for A$AP Rocky in repertoire

{
  participantSearch(name: "ASAP Rocky") {
    nodes {
      name
      role
      recordingProjects {
        nodes {
          title
          status
        }
      }
    }
  }
}

Search for Ray Vaughn (has a feature = SAA)

{
  participantSearch(name: "Ray Vaughn") {
    nodes {
      name
      role
      recordingProjects {
        nodes {
          title
          status
        }
      }
    }
  }
}

NOTE: If participantSearch errors, try introspecting first:

```graphql

{ __type(name: "Query") { fields { name } } }

```

Then Ctrl+F for "participant" or "repertoire" in the results.

---

PRIORITY 4: SCUBA / Spotify Catalog (Artist Insights angle)

Less about workability, more about proving the data pipe works.

If these return rich metadata, it proves SCUBA can replace

manual data pulls for Crawley's insights decks.

horsegiirL Spotify (you know this artist's data)

{
  spotifyArtistById(id: "4TXzFwKOHVRMPSiamcrya0") {
    name
    popularity
    genres
    followers
  }
}

Sleepy Hallow Spotify

{
  spotifyArtistById(id: "0rPFhJknwkFaMb4tOUdKJ4") {
    name
    popularity
    genres
    followers
  }
}

A$AP Rocky Spotify

{
  spotifyArtistById(id: "13ubrt8QOOCPljQ2FL1Kg8") {
    name
    popularity
    genres
    followers
  }
}

If these return data, screenshot them. That's a same-day

deliverable for Crawley: "I can pull this in 10 seconds

instead of you doing it manually."

---

WHAT TO DO WITH RESULTS

If clearance queries return data:

Screenshot it. Put it next to the workability snapshot showing

"Unknown." That's your one-slide proof: "The data exists. Nobody

is reading it." Send to Jordan immediately.

If clearance queries return empty:

That's expected in STAGE. Note it and move on. The query WORKS —

you just need production data. Message to Jordan:

"Query confirmed, need production access to see real data."

If mega-query workability scores differ from export:

That's actually MORE interesting — it means data is updating

in one system but not flowing to the other. Screenshot both.

If Spotify/SCUBA returns rich data:

Screenshot it and save for Crawley. This is a Week 2 deliverable:

"I can automate the data pull for your insights decks."

---

ISRCs FROM EXPORT — FULL REFERENCE

Releases with Features (SAA-relevant)

This Week (Mar 27)

Next Week (Apr 3)

Active Projects Artists (Apr 17)

Later Releases