The Shallows

Master case overview

Master file reference

GPRCC-ILL-2010-NC-784881

Illustrative status

Approved

Author / reference identity

Nicholas Carr

Subject area

Technology & Society

Work

The Shallows

Review focus

Technology terminology, data provenance and time-sensitive technical claims. Program questions are selected for this subject area; no passage-level findings are asserted.

Proposed formats · scenario

Ebook and library editions

Proposed market scope · scenario

English-language release; foreign editions subject to separate review

Book release date

7 June 2010
Open Library ↗

Registration date · illustrative

14 June 2010

Publication and registration basis

The Shallows: Earliest dated catalog edition in the recorded first-publication year; editions may vary. 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

15 July 2010

Source basis

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

Programs & status

This illustrative file covers 8 program records, 31 review controls and 0 open items. Select a program for its review details, document checklist and next action.

Program reference

GPRCC-ILL-2010-NC-784881-DPCP

Master file

GPRCC-ILL-2010-NC-784881

Review scope

Ebook and library editions

Evidence position

3 of 3 controls complete in scenario

Publication context

The Shallows by Nicholas Carr · Technology terminology, data provenance and time-sensitive technical claims

Review controls and scoped outcome 3

1. DPCP-101

   Personal-data inventory

   For the proposed scope of The Shallows, identify any personal information proposed for reproduction. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

2. DPCP-103

   Minimization

   For the proposed scope of The Shallows, consider whether unnecessary identifying details can be removed. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

3. DPCP-104

   Access controls

   For the proposed scope of The Shallows, separate public material from restricted review records. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 3

• Personal-data inventoryCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: DPCP-101.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Minimization and redaction worksheetCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: DPCP-103.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Review access planCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: DPCP-104.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2010-NC-784881-AICP

Master file

GPRCC-ILL-2010-NC-784881

Review scope

Ebook and library editions

Evidence position

5 of 5 controls complete in scenario

Publication context

The Shallows by Nicholas Carr · Technology terminology, data provenance and time-sensitive technical claims

Review controls and scoped outcome 5

1. AICP-101

   Content provenance

   For the proposed scope of The Shallows, identify whether any proposed publication assets use generated material. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

2. AICP-102

   Human review

   For the proposed scope of The Shallows, define responsibility for checking any generated passages or visual assets. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

3. AICP-103

   Input rights

   For the proposed scope of The Shallows, document permission boundaries for inputs used in proposed generation workflows. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

4. AICP-104

   Reader disclosure

   For the proposed scope of The Shallows, draft proportionate disclosure for any applicable generated contribution. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

5. AICP-105

   Version history

   For the proposed scope of The Shallows, track edited outputs and the responsible human reviewer. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 5

• AI-use declaration checklistCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: AICP-101.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Human review protocolCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: AICP-102.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Input provenance registerCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: AICP-103.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• AI contribution disclosure sheetCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: AICP-104.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Generation and revision logCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: AICP-105.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2010-NC-784881-NDIS

Master file

GPRCC-ILL-2010-NC-784881

Review scope

Ebook and library editions

Evidence position

3 of 3 controls complete in scenario

Publication context

The Shallows by Nicholas Carr · Technology terminology, data provenance and time-sensitive technical claims

Review controls and scoped outcome 3

1. NDIS-102

   Confidentiality handling

   For the proposed scope of The Shallows, separate public references from material requiring restricted access. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

2. NDIS-103

   Corroboration plan

   For the proposed scope of The Shallows, identify which claims would need independent corroboration. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

3. NDIS-105

   Redaction control

   For the proposed scope of The Shallows, define version controls for any required redactions. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 3

• Source handling matrixCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: NDIS-102.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Corroboration worksheetCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: NDIS-103.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Redaction and access logCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: NDIS-105.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2010-NC-784881-FCRS

Master file

GPRCC-ILL-2010-NC-784881

Review scope

Ebook and library editions

Evidence position

5 of 5 controls complete in scenario

Publication context

The Shallows by Nicholas Carr · Technology terminology, data provenance and time-sensitive technical claims

Review controls and scoped outcome 5

1. FCRS-101

   Claim inventory

   For the proposed scope of The Shallows, classify factual, historical and statistical claims selected for the review scope. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

2. FCRS-102

   Source traceability

   For the proposed scope of The Shallows, record author, date, edition and location of supporting references. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

3. FCRS-103

   Context and limitations

   For the proposed scope of The Shallows, retain qualifications and avoid widening conclusions beyond their sources. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

4. FCRS-104

   Data reproduction

   For the proposed scope of The Shallows, reconcile quoted figures with their source tables and units. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

5. FCRS-105

   Correction control

   For the proposed scope of The Shallows, track the edition in which a proposed correction would take effect. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 5

• Claim-to-source ledgerCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: FCRS-101.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Source bibliography and locator indexCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: FCRS-102.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Claim qualification scheduleCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: FCRS-103.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Statistical reproduction worksheetCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: FCRS-104.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Correction and version logCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: FCRS-105.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2010-NC-784881-PDTC

Master file

GPRCC-ILL-2010-NC-784881

Review scope

Ebook and library editions

Evidence position

3 of 3 controls complete in scenario

Publication context

The Shallows by Nicholas Carr · Technology terminology, data provenance and time-sensitive technical claims

Review controls and scoped outcome 3

1. PDTC-102

   Terms mapping

   For the proposed scope of The Shallows, map the proposed release against documented platform requirements. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

2. PDTC-104

   Access and files

   For the proposed scope of The Shallows, specify file validation and accessibility checks before delivery. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

3. PDTC-105

   Change handling

   For the proposed scope of The Shallows, assign responsibility for updates, corrections and withdrawal requests. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 3

• Platform requirements checklistCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: PDTC-102.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Digital file validation checklistCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: PDTC-104.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Platform change-control planCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: PDTC-105.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2010-NC-784881-IDLC

Master file

GPRCC-ILL-2010-NC-784881

Review scope

Ebook and library editions

Evidence position

3 of 3 controls complete in scenario

Publication context

The Shallows by Nicholas Carr · Technology terminology, data provenance and time-sensitive technical claims

Review controls and scoped outcome 3

1. IDLC-101

   Agreement inventory

   For the proposed scope of The Shallows, identify proposed publisher, distributor and retail permissions for the named work. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

2. IDLC-102

   License boundaries

   For the proposed scope of The Shallows, map term, format, territory, language and sublicensing limits. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

3. IDLC-103

   Retail metadata

   For the proposed scope of The Shallows, reconcile title, author credit, edition description and rights-holder attribution. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 3

• Distribution agreement inventoryCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IDLC-101.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Distribution license matrixCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IDLC-102.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Retail metadata approval sheetCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IDLC-103.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2010-NC-784881-IRTC

Master file

GPRCC-ILL-2010-NC-784881

Review scope

Ebook and library editions

Evidence position

5 of 5 controls complete in scenario

Publication context

The Shallows by Nicholas Carr · Technology terminology, data provenance and time-sensitive technical claims

Review controls and scoped outcome 5

1. IRTC-101

   Chain of title

   For the proposed scope of The Shallows, identify the party authorized to grant rights and reconcile contributor assignments. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

2. IRTC-102

   Territory and format scope

   For the proposed scope of The Shallows, map languages, formats, exclusivity and reserved territories without assuming worldwide rights. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

3. IRTC-103

   Edition history

   For the proposed scope of The Shallows, separate original publication rights from revised-edition and supplementary-material rights. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

4. IRTC-104

   Quotation permissions

   For the proposed scope of The Shallows, record the basis for reuse of any third-party extracts in the proposed edition. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

5. IRTC-105

   Reversion and reservations

   For the proposed scope of The Shallows, identify expired grants, reserved uses and conflicting options. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 5

• Ownership and contributor assignment scheduleCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IRTC-101.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Territory, language and format matrixCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IRTC-102.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Edition and rights chronologyCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IRTC-103.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Third-party permissions registerCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IRTC-104.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Prior grants and reversion scheduleCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: IRTC-105.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2010-NC-784881-CAVR

Master file

GPRCC-ILL-2010-NC-784881

Review scope

Ebook and library editions

Evidence position

4 of 4 controls complete in scenario

Publication context

The Shallows by Nicholas Carr · Technology terminology, data provenance and time-sensitive technical claims

Review controls and scoped outcome 4

1. CAVR-101

   Visual asset provenance

   For the proposed scope of The Shallows, record the source and permitted use of cover and interior visual assets. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

2. CAVR-103

   Format reuse

   For the proposed scope of The Shallows, check proposed visual reuse across print, ebook, audio and promotion. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

3. CAVR-104

   Credit requirements

   For the proposed scope of The Shallows, record mandatory image credits and license conditions. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

4. CAVR-105

   Edition approval

   For the proposed scope of The Shallows, track the approved cover version for each proposed edition. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. Submitted evidence accepted; this requirement is completed within the scenario’s approved scope.

Completed requirements 4

• Cover and artwork provenance registerCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: CAVR-101.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Visual reuse permission matrixCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: CAVR-103.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Visual credit-line sheetCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: CAVR-104.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative
• Cover version approval logCompletedSubmitted evidence accepted; this requirement is completed within the scenario’s approved scope. Reference: CAVR-105.Submission attempt 1 · 19 June 2010 · reviewed 15 July 2010 · illustrative

↑ Back to programs

Evidence and document index

A modeled evidence schedule for The Shallows. 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 8 programs below. These example amounts are not payment receipts or quotations.

Total illustrative fees · USD$28,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. Retain the edition, format and rights schedules modeled in this record.
2. Check proposed changes against each program’s maintenance standard.
3. Reassess new translations, licenses or substantial promotional changes before extending scope.

This sequence describes the modeled approved workflow only.