News, Documentary & Investigative Source Integrity
GPRCC-ILL-2000-MS-805829-NDIS
Review scope: source provenance, confidentiality handling, corroboration plan.
4 review controls0 open items
Illustrative fee · USD$3,650
View review details ↓Middle East & Global Security · Publication and program dossier
By Marjane Satrapi

This illustrative file covers 10 program records, 38 review controls and 0 open items. Select a program for its review details, document checklist and next action.
All submitted documents are accepted in this scenario. No outstanding requirements remain.
38 / 38 completedGPRCC-ILL-2000-MS-805829-NDIS
Review scope: source provenance, confidentiality handling, corroboration plan.
4 review controls0 open items
Illustrative fee · USD$3,650
View review details ↓GPRCC-ILL-2000-MS-805829-IMRC
Review scope: fact and opinion boundaries, non-affiliation wording, edition-specific publicity.
4 review controls0 open items
Illustrative fee · USD$2,100
View review details ↓GPRCC-ILL-2000-MS-805829-CBCS
Review scope: market scope, edition variations, partner checks.
4 review controls0 open items
Illustrative fee · USD$2,600
View review details ↓GPRCC-ILL-2000-MS-805829-RCCR
Review scope: belief and attribution, translation sensitivity, promotional framing.
3 review controls0 open items
Illustrative fee · USD$3,150
View review details ↓GPRCC-ILL-2000-MS-805829-TFRR
Review scope: translation grant, translator rights, terminology control.
5 review controls0 open items
Illustrative fee · USD$3,650
View review details ↓GPRCC-ILL-2000-MS-805829-IDLC
Review scope: agreement inventory, license boundaries, accounting and reporting.
4 review controls0 open items
Illustrative fee · USD$2,100
View review details ↓GPRCC-ILL-2000-MS-805829-IRTC
Review scope: chain of title, territory and format scope, edition history.
3 review controls0 open items
Illustrative fee · USD$2,600
View review details ↓GPRCC-ILL-2000-MS-805829-CAVR
Review scope: visual asset provenance, format reuse, credit requirements.
4 review controls0 open items
Illustrative fee · USD$3,150
View review details ↓GPRCC-ILL-2000-MS-805829-IBEM
Review scope: protected assets, authorized channels, control verification.
4 review controls0 open items
Illustrative fee · USD$3,650
View review details ↓GPRCC-ILL-2000-MS-805829-AVRR
Review scope: audio grant, performer agreement, audio-only material.
3 review controls0 open items
Illustrative fee · USD$2,350
View review details ↓For the proposed scope of Persepolis, trace research inputs to their origin and document verification limits. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, separate public references from material requiring restricted access. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, identify which claims would need independent corroboration. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, define version controls for any required redactions. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, separate editorial interpretation from independently checkable claims in proposed publicity. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, review references to people and institutions for unintended endorsement implications. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, align retailer summaries and campaign copy with the edition proposed for release. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, define which disputed statements would require specialist review before reuse. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, identify the proposed distribution markets before country-specific review. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, track any proposed market-specific changes separately from the source edition. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, document proposed distribution partner responsibilities. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, record market-specific prerequisites before release authorization. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, distinguish an author’s interpretation from an attributed community position. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, flag terms that could change meaning across languages. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, preserve distinctions between discussion, criticism and affiliation. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, identify language, territory and format boundaries for a proposed translation. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, document translator credit, assignment and permitted reuse. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, prepare a terminology guide appropriate to the work’s subject area. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, separate faithful translation from abridgment or local adaptation. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, define the approval process for translated covers and descriptions. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, identify proposed publisher, distributor and retail permissions for the named work. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, map term, format, territory, language and sublicensing limits. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, document royalty reporting intervals, deductions and audit provisions. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, define takedown, stock sell-off and rights reversion responsibilities. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, identify the party authorized to grant rights and reconcile contributor assignments. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, map languages, formats, exclusivity and reserved territories without assuming worldwide rights. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, separate original publication rights from revised-edition and supplementary-material rights. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, record the source and permitted use of cover and interior visual assets. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, check proposed visual reuse across print, ebook, audio and promotion. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, record mandatory image credits and license conditions. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, track the approved cover version for each proposed edition. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, separate protectable text and artwork from third-party names and lawful references. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, distinguish approved editions and sellers from items that need verification. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, identify who may authorize use of the proposed author and publication branding. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, specify evidence capture and rights-holder approval before any proposed notice. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, separate narration and audio distribution rights from print rights. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, define narrator credit, recording use and permitted reuse. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
For the proposed scope of Persepolis, identify proposed introductions, music and other added audio assets. Apply this check in the context of conflict terminology, historical attribution and regional context.
Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.
A modeled evidence schedule for Persepolis. These are document requirements and scenario states, not uploaded attachments or manuscript citations.
| Control reference | Document requirement | Scenario state |
|---|---|---|
| NDIS-101 | Source provenance register | Completed · submitted and reviewed |
| NDIS-102 | Source handling matrix | Completed · submitted and reviewed |
| NDIS-103 | Corroboration worksheet | Completed · submitted and reviewed |
| NDIS-105 | Redaction and access log | Completed · submitted and reviewed |
| IMRC-101 | Publicity claim and source ledger | Completed · submitted and reviewed |
| IMRC-102 | Non-affiliation wording sheet | Completed · submitted and reviewed |
| IMRC-104 | Campaign and jacket-copy comparison | Completed · submitted and reviewed |
| IMRC-105 | Media review escalation plan | Completed · submitted and reviewed |
| CBCS-101 | Target-market schedule | Completed · submitted and reviewed |
| CBCS-103 | Market edition comparison | Completed · submitted and reviewed |
| CBCS-104 | Partner responsibility matrix | Completed · submitted and reviewed |
| CBCS-105 | Market release checklist | Completed · submitted and reviewed |
| RCCR-102 | Belief and attribution map | Completed · submitted and reviewed |
| RCCR-103 | Cultural terminology sheet | Completed · submitted and reviewed |
| RCCR-105 | Cross-cultural publicity review | Completed · submitted and reviewed |
| TFRR-101 | Foreign-rights grant matrix | Completed · submitted and reviewed |
| TFRR-102 | Translator agreement checklist | Completed · submitted and reviewed |
| TFRR-103 | Translation terminology brief | Completed · submitted and reviewed |
| TFRR-104 | Translation change-control sheet | Completed · submitted and reviewed |
| TFRR-105 | Foreign edition approval checklist | Completed · submitted and reviewed |
| IDLC-101 | Distribution agreement inventory | Completed · submitted and reviewed |
| IDLC-102 | Distribution license matrix | Completed · submitted and reviewed |
| IDLC-104 | Royalty and reporting schedule | Completed · submitted and reviewed |
| IDLC-105 | Termination and reversion checklist | Completed · submitted and reviewed |
| IRTC-101 | Ownership and contributor assignment schedule | Completed · submitted and reviewed |
| IRTC-102 | Territory, language and format matrix | Completed · submitted and reviewed |
| IRTC-103 | Edition and rights chronology | Completed · submitted and reviewed |
| CAVR-101 | Cover and artwork provenance register | Completed · submitted and reviewed |
| CAVR-103 | Visual reuse permission matrix | Completed · submitted and reviewed |
| CAVR-104 | Visual credit-line sheet | Completed · submitted and reviewed |
| CAVR-105 | Cover version approval log | Completed · submitted and reviewed |
| IBEM-101 | Protected asset inventory | Completed · submitted and reviewed |
| IBEM-102 | Authorized edition and channel register | Completed · submitted and reviewed |
| IBEM-104 | Brand and account control checklist | Completed · submitted and reviewed |
| IBEM-105 | Evidence capture and escalation protocol | Completed · submitted and reviewed |
| AVRR-101 | Audio rights matrix | Completed · submitted and reviewed |
| AVRR-102 | Narrator agreement checklist | Completed · submitted and reviewed |
| AVRR-103 | Audio asset permission register | Completed · submitted and reviewed |
| Program | Illustrative status | Open items | Next action |
|---|---|---|---|
| NDIS | Approved | 0 | Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. |
| IMRC | Approved | 0 | Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. |
| CBCS | Approved | 0 | Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. |
| RCCR | Approved | 0 | Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. |
| TFRR | Approved | 0 | Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. |
| IDLC | Approved | 0 | Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. |
| IRTC | Approved | 0 | Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. |
| CAVR | Approved | 0 | Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. |
| IBEM | Approved | 0 | Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. |
| AVRR | Approved | 0 | Maintain the documented scope. A new edition, rights grant or material campaign change would trigger reassessment. |
Generated milestones showing how this workflow could progress; these events did not occur for the named author.
| Scenario date | Modeled milestone |
|---|---|
| 8 November 2000 – 7 December 2000 (release day unverified) | Registration modeled |
| 13 November 2000 – 12 December 2000 (release day unverified) | Evidence package submitted · scenario |
| 25 November 2000 – 24 December 2000 (release day unverified) | Submitted evidence reviewed · scenario |
| 9 December 2000 – 7 January 2001 (release day unverified) | Scoped approval modeled |
The original illustrative case total is allocated across the 10 programs below. These example amounts are not payment receipts or quotations.
| Program | Program name | Allocated fee (USD) |
|---|---|---|
| NDIS | News, Documentary & Investigative Source Integrity | $3,650 |
| IMRC | International Media & Reputation Clearance File | $2,100 |
| CBCS | Cross-Border Contract & Restricted-Territory Screening | $2,600 |
| RCCR | Religious & Cultural Content Review | $3,150 |
| TFRR | Translation & Foreign Rights Record | $3,650 |
| IDLC | International Distribution & Licensing Compliance File | $2,100 |
| IRTC | International Rights & Territory Control File | $2,600 |
| CAVR | Cover, Artwork & Visual Asset Rights Record | $3,150 |
| IBEM | International Brand Enforcement & Monitoring File | $3,650 |
| AVRR | Audiobook, Narration & Voice Rights Record | $2,350 |
Total illustrative fees · USD$29,000
These restored case allocations are separate from the planning bands for new quotes. A written scope and quote determine the charge for an actual matter.
This sequence describes the modeled approved workflow only.
Illustrative scope. The author and publication identify a library entry. Review details and registration milestones are synthetic; book publication dates are sourced; the page makes no claim that the author applied, supplied evidence, paid fees or received a determination.
Program references. GPRCC-ILL identifiers label scenarios, not statutory registrations. Document states and allocated fees are not proof of review or payment.
Publication context. The modeled status makes no finding about the publication’s legality, accuracy, ownership or suitability. Real determinations require a submitted record and an authorized review.
Author Case Library