Ghost Wars

Master case overview

Master file reference

GPRCC-ILL-2004-SC-323680

Illustrative status

Registration Declined

Author / reference identity

Steve Coll

Subject area

Middle East & Global Security

Work

Ghost Wars

Review focus

Conflict terminology, historical attribution and regional context. Program questions are selected for this subject area; no passage-level findings are asserted.

Proposed formats · scenario

Print and ebook

Proposed market scope · scenario

Domestic release with a proposed translation-rights package

Book release date

2004
Publication history ↗

Registration date · illustrative

8 January 2004 – 7 January 2005 (release day unverified)

Publication and registration basis

Ghost Wars: Original Penguin Press book, not the later paperback. Release day unverified. The modeled registration is seven days after release. Where a source gives only a month or year, dates are shown as a range rather than inventing a day.

Modeled review date

8 February 2004 – 7 February 2005 (release day unverified)

Source basis

Library title, author, subject mapping and catalog program definitions; no manuscript examined.

Programs & status

This illustrative file covers 9 program records, 33 review controls and 23 open items. Select a program for its review details, document checklist and next action.

Program reference

GPRCC-ILL-2004-SC-323680-NDIS

Master file

GPRCC-ILL-2004-SC-323680

Review scope

Print and ebook

Evidence position

2 of 5 controls complete in scenario

Publication context

Ghost Wars by Steve Coll · Conflict terminology, historical attribution and regional context

Submission review and rejected requirements 5

1. NDIS-101

   Source provenance

   For the proposed scope of Ghost Wars, trace research inputs to their origin and document verification limits. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries.

2. NDIS-102

   Confidentiality handling

   For the proposed scope of Ghost Wars, separate public references from material requiring restricted access. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope.

3. NDIS-103

   Corroboration plan

   For the proposed scope of Ghost Wars, 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 was accepted in this scenario; the application was declined because other requirements failed review.

4. NDIS-104

   Interview permission

   For the proposed scope of Ghost Wars, document the scope of any proposed interview reuse. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Completed · scenario. Submitted evidence was accepted in this scenario; the application was declined because other requirements failed review.

5. NDIS-105

   Redaction control

   For the proposed scope of Ghost Wars, define version controls for any required redactions. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries.

Submission results 5

• Source provenance registerRejectedSubmitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries. Reference: NDIS-101.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Source handling matrixRejectedSubmitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope. Reference: NDIS-102.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Corroboration worksheetCompletedSubmitted evidence was accepted in this scenario; the application was declined because other requirements failed review. Reference: NDIS-103.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Interview permission checklistCompletedSubmitted evidence was accepted in this scenario; the application was declined because other requirements failed review. Reference: NDIS-104.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Redaction and access logRejectedSubmitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries. Reference: NDIS-105.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2004-SC-323680-IMRC

Master file

GPRCC-ILL-2004-SC-323680

Review scope

Print and ebook

Evidence position

0 of 4 controls complete in scenario

Publication context

Ghost Wars by Steve Coll · Conflict terminology, historical attribution and regional context

Submission review and rejected requirements 4

1. IMRC-101

   Fact and opinion boundaries

   For the proposed scope of Ghost Wars, separate editorial interpretation from independently checkable claims in proposed publicity. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope.

2. IMRC-103

   Interview preparation

   For the proposed scope of Ghost Wars, prepare source-backed responses and distinguish the author’s position from promotional paraphrases. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation.

3. IMRC-104

   Edition-specific publicity

   For the proposed scope of Ghost Wars, 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.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope.

4. IMRC-105

   Escalation protocol

   For the proposed scope of Ghost Wars, define which disputed statements would require specialist review before reuse. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope.

Submission results 4

• Publicity claim and source ledgerRejectedSubmitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope. Reference: IMRC-101.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Interview and media briefingRejectedSubmitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation. Reference: IMRC-103.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Campaign and jacket-copy comparisonRejectedSubmitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope. Reference: IMRC-104.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Media review escalation planRejectedSubmitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope. Reference: IMRC-105.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2004-SC-323680-CBCS

Master file

GPRCC-ILL-2004-SC-323680

Review scope

Print and ebook

Evidence position

1 of 3 controls complete in scenario

Publication context

Ghost Wars by Steve Coll · Conflict terminology, historical attribution and regional context

Submission review and rejected requirements 3

1. CBCS-101

   Market scope

   For the proposed scope of Ghost Wars, 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 was accepted in this scenario; the application was declined because other requirements failed review.

2. CBCS-104

   Partner checks

   For the proposed scope of Ghost Wars, document proposed distribution partner responsibilities. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries.

3. CBCS-105

   Release gates

   For the proposed scope of Ghost Wars, record market-specific prerequisites before release authorization. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation.

Submission results 3

• Target-market scheduleCompletedSubmitted evidence was accepted in this scenario; the application was declined because other requirements failed review. Reference: CBCS-101.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Partner responsibility matrixRejectedSubmitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries. Reference: CBCS-104.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Market release checklistRejectedSubmitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation. Reference: CBCS-105.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2004-SC-323680-RCCR

Master file

GPRCC-ILL-2004-SC-323680

Review scope

Print and ebook

Evidence position

1 of 3 controls complete in scenario

Publication context

Ghost Wars by Steve Coll · Conflict terminology, historical attribution and regional context

Submission review and rejected requirements 3

1. RCCR-101

   Cultural context

   For the proposed scope of Ghost Wars, identify contextual notes needed for cross-cultural presentation. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope.

2. RCCR-102

   Belief and attribution

   For the proposed scope of Ghost Wars, distinguish an author’s interpretation from an attributed community position. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation.

3. RCCR-103

   Translation sensitivity

   For the proposed scope of Ghost Wars, 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 was accepted in this scenario; the application was declined because other requirements failed review.

Submission results 3

• Cultural context review briefRejectedSubmitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope. Reference: RCCR-101.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Belief and attribution mapRejectedSubmitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation. Reference: RCCR-102.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Cultural terminology sheetCompletedSubmitted evidence was accepted in this scenario; the application was declined because other requirements failed review. Reference: RCCR-103.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2004-SC-323680-TFRR

Master file

GPRCC-ILL-2004-SC-323680

Review scope

Print and ebook

Evidence position

2 of 4 controls complete in scenario

Publication context

Ghost Wars by Steve Coll · Conflict terminology, historical attribution and regional context

Submission review and rejected requirements 4

1. TFRR-101

   Translation grant

   For the proposed scope of Ghost Wars, 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 was accepted in this scenario; the application was declined because other requirements failed review.

2. TFRR-102

   Translator rights

   For the proposed scope of Ghost Wars, document translator credit, assignment and permitted reuse. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation.

3. TFRR-103

   Terminology control

   For the proposed scope of Ghost Wars, 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.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope.

4. TFRR-105

   Foreign edition approval

   For the proposed scope of Ghost Wars, 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 was accepted in this scenario; the application was declined because other requirements failed review.

Submission results 4

• Foreign-rights grant matrixCompletedSubmitted evidence was accepted in this scenario; the application was declined because other requirements failed review. Reference: TFRR-101.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Translator agreement checklistRejectedSubmitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation. Reference: TFRR-102.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Translation terminology briefRejectedSubmitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope. Reference: TFRR-103.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Foreign edition approval checklistCompletedSubmitted evidence was accepted in this scenario; the application was declined because other requirements failed review. Reference: TFRR-105.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2004-SC-323680-IDLC

Master file

GPRCC-ILL-2004-SC-323680

Review scope

Print and ebook

Evidence position

0 of 3 controls complete in scenario

Publication context

Ghost Wars by Steve Coll · Conflict terminology, historical attribution and regional context

Submission review and rejected requirements 3

1. IDLC-102

   License boundaries

   For the proposed scope of Ghost Wars, map term, format, territory, language and sublicensing limits. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries.

2. IDLC-104

   Accounting and reporting

   For the proposed scope of Ghost Wars, document royalty reporting intervals, deductions and audit provisions. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation.

3. IDLC-105

   Termination controls

   For the proposed scope of Ghost Wars, define takedown, stock sell-off and rights reversion responsibilities. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries.

Submission results 3

• Distribution license matrixRejectedSubmitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries. Reference: IDLC-102.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Royalty and reporting scheduleRejectedSubmitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation. Reference: IDLC-104.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Termination and reversion checklistRejectedSubmitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries. Reference: IDLC-105.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2004-SC-323680-IRTC

Master file

GPRCC-ILL-2004-SC-323680

Review scope

Print and ebook

Evidence position

0 of 3 controls complete in scenario

Publication context

Ghost Wars by Steve Coll · Conflict terminology, historical attribution and regional context

Submission review and rejected requirements 3

1. IRTC-101

   Chain of title

   For the proposed scope of Ghost Wars, 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.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation.

2. IRTC-102

   Territory and format scope

   For the proposed scope of Ghost Wars, 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.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries.

3. IRTC-103

   Edition history

   For the proposed scope of Ghost Wars, 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.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope.

Submission results 3

• Ownership and contributor assignment scheduleRejectedSubmitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation. Reference: IRTC-101.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Territory, language and format matrixRejectedSubmitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries. Reference: IRTC-102.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Edition and rights chronologyRejectedSubmitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope. Reference: IRTC-103.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2004-SC-323680-CAVR

Master file

GPRCC-ILL-2004-SC-323680

Review scope

Print and ebook

Evidence position

3 of 4 controls complete in scenario

Publication context

Ghost Wars by Steve Coll · Conflict terminology, historical attribution and regional context

Submission review and rejected requirements 4

1. CAVR-101

   Visual asset provenance

   For the proposed scope of Ghost Wars, 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 was accepted in this scenario; the application was declined because other requirements failed review.

2. CAVR-102

   Designer permissions

   For the proposed scope of Ghost Wars, separate designer deliverables from third-party stock and font licenses. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation.

3. CAVR-103

   Format reuse

   For the proposed scope of Ghost Wars, 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 was accepted in this scenario; the application was declined because other requirements failed review.

4. CAVR-104

   Credit requirements

   For the proposed scope of Ghost Wars, 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 was accepted in this scenario; the application was declined because other requirements failed review.

Submission results 4

• Cover and artwork provenance registerCompletedSubmitted evidence was accepted in this scenario; the application was declined because other requirements failed review. Reference: CAVR-101.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Designer and supplier rights checklistRejectedSubmitted evidence was reviewed but rejected in this scenario: the supporting record did not substantiate the requested confirmation. Reference: CAVR-102.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Visual reuse permission matrixCompletedSubmitted evidence was accepted in this scenario; the application was declined because other requirements failed review. Reference: CAVR-103.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Visual credit-line sheetCompletedSubmitted evidence was accepted in this scenario; the application was declined because other requirements failed review. Reference: CAVR-104.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2004-SC-323680-IBEM

Master file

GPRCC-ILL-2004-SC-323680

Review scope

Print and ebook

Evidence position

1 of 4 controls complete in scenario

Publication context

Ghost Wars by Steve Coll · Conflict terminology, historical attribution and regional context

Submission review and rejected requirements 4

1. IBEM-101

   Protected assets

   For the proposed scope of Ghost Wars, 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.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope.

2. IBEM-102

   Authorized channels

   For the proposed scope of Ghost Wars, distinguish approved editions and sellers from items that need verification. Apply this check in the context of conflict terminology, historical attribution and regional context.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries.

3. IBEM-104

   Control verification

   For the proposed scope of Ghost Wars, 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.

   Rejected · scenario. Submitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope.

4. IBEM-105

   Notice readiness

   For the proposed scope of Ghost Wars, 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 was accepted in this scenario; the application was declined because other requirements failed review.

Submission results 4

• Protected asset inventoryRejectedSubmitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope. Reference: IBEM-101.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Authorized edition and channel registerRejectedSubmitted evidence was reviewed but rejected in this scenario: the supplied version did not reconcile the identified rights or review boundaries. Reference: IBEM-102.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Brand and account control checklistRejectedSubmitted evidence was reviewed but rejected in this scenario: the evidence did not establish the requested scope. Reference: IBEM-104.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative
• Evidence capture and escalation protocolCompletedSubmitted evidence was accepted in this scenario; the application was declined because other requirements failed review. Reference: IBEM-105.Submission attempt 1 · 13 January 2004 – 12 January 2005 (release day unverified) · reviewed 8 February 2004 – 7 February 2005 (release day unverified) · illustrative

↑ Back to programs

Evidence and document index

A modeled evidence schedule for Ghost Wars. These are document requirements and scenario states, not uploaded attachments or manuscript citations.

Consolidated program status

Illustrative review history

Generated milestones showing how this workflow could progress; these events did not occur for the named author.

Program fee breakdown

The original illustrative case total is allocated across the 9 programs below. These example amounts are not payment receipts or quotations.

Total illustrative fees · USD$29,500

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.

Next steps

1. Identify the requirements remaining unresolved at the modeled decision stage.
2. Consult the applicable notice and review process before proposing a further submission.
3. Prepare a response addressing each unresolved control; a fee or revised document alone would not guarantee approval.

This sequence describes the modeled registration declined workflow only.