STRUCTURED CONTENT / CONNECTED CONSEQUENCES
One credit.
Every connection.
Follow a film credit to its source. Change a local copy.
See exactly which views feel the impact.
A person's name is stored once.
Their credits can appear everywhere.
02 / Trace a credit
SOURCE SNAPSHOTCHECK THE EVIDENCE
Real references. An honest boundary.
This app reads factual credits from Sanity's public movie demo. It does not own the dataset or its schema. Simulations are browser-local projections, not predictions of a successful database mutation.
Sanity normally protects strong references from target deletion. The disappearance scenario illustrates unresolved content after a bad import or incomplete fetch; it does not bypass that protection.
Source, snapshot and query
- Project / dataset
- ppsg7ml5 / movies
- Fetched at
- 2026-10-03T02:13:19.715Z
- API version
- 2021-10-21
Static Astro build, fetched from the real Content Lake. It does not refresh live in this page. Run the source-fetch script and rebuild to update it.
Inspect the exact public query{"movies":*[_type=="movie"]|order(title){_id,title,releaseDate,releaseYear,castMembers[]{_key,characterName,person{_ref,_weak}},crewMembers[]{_key,job,department,person{_ref,_weak}}},"people":*[_type=="person"]{_id,name},"screenings":*[_type=="screening"]{_id,title,movie{_ref,_weak},beginAt}}Attribution and provenance
Data: Sanity public movies demonstration dataset, supplied by Sanity as sample content for app development. The original movie schema is Sanity’s; this app adds its own diagnostic graph and local experiments. Credit facts only; no posters, plot descriptions or biographies are copied. The sample archive is not claimed to be wholly covered by the CLI code license. Contest acceptance remains the organizers’ decision.
Sanity's GROQ and reference documentation