{
 "schemaVersion": "1.0.0",
 "constitutionVersion": "1.0.0",
 "createdAt": "2026-08-12T00:00:00Z",
 "description": "Append-only Evidence Passport records. Old revisions are immutable; corrections create a new revision and preserve the previous permalink.",
 "entity": {
  "type": "project",
  "id": "washington-dc-311",
  "title": "DC 311 and the Open311 API It Started",
  "canonicalUrl": "https://1001smartcities.org/projects/washington-dc-311/"
 },
 "currentRevisionId": "2026-08-21-source-dates",
 "revisions": [
  {
   "id": "2026-08-20-claim-baseline",
   "createdAt": "2026-08-21T10:05:00Z",
   "effectiveAt": "2026-07-26",
   "changeType": "baseline",
   "summary": "Created the first structured Evidence Passport with 10 claims and 13 source dossiers.",
   "preparedBy": {
    "type": "automation",
    "label": "AI-assisted evidence preparation",
    "humanApproved": false
   },
   "review": {
    "status": "unreviewed",
    "by": null,
    "date": null,
    "note": "Awaiting operator and domain-expert review; publication of this revision implies neither."
   },
   "changes": [
    {
     "operation": "add",
     "path": "/evidencePassport",
     "summary": "Added claim-level evidence mapping and source dossiers."
    },
    {
     "operation": "add",
     "path": "/revisionHistory",
     "summary": "Established a permanent, hash-addressed baseline revision."
    }
   ],
   "snapshotHash": "sha256:6b5d502aa249f3f225c7ead86a680808f256d6f56d3c89b08058461ee620524f",
   "snapshot": {
    "asOf": "2026-07-26",
    "projectFingerprint": "sha256:f81c8b28e30ef973f90b401fe3e47a1620be42a71f112c4ae6e60086e047bfcf",
    "assurance": {
     "status": "unreviewed",
     "scope": "evidence-passport-revision",
     "statement": "AI-assisted structural preparation. This revision has not been reviewed by a human or subject-matter expert.",
     "machineChecks": [
      "schema",
      "publication-diff-contract",
      "material-project-fingerprint",
      "claim-text-drift",
      "source-reference-resolution",
      "complete-source-dossier",
      "snapshot-hash"
     ]
    },
    "projectState": {
     "status": "live",
     "outcome": "scaled-back",
     "evidenceGrade": "official",
     "timeline": {
      "started": 2000,
      "ended": null
     }
    },
    "governance": {
     "operator": "District of Columbia Office of Unified Communications (OUC); data published by the Office of the Chief Technology Officer (OCTO)",
     "actorTypes": [
      "city-government"
     ],
     "fundingModel": "public",
     "fundingDescription": "District of Columbia appropriations, through the Office of Unified Communications",
     "cost": null,
     "ownership": null,
     "decisionRights": null,
     "exitConditions": null
    },
    "claims": [
     {
      "id": "clm-76624b68fdfac6c8",
      "field": "snippet",
      "text": "Washington introduced a 311 line in 2000",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-dceafae72137bc56"
      ],
      "supportNote": "The only source found that dates the launch states 'DC's 311 line was introduced in 2000', at first used exclusively for reporting non-emergencies requiring a police response, with 202-727-1000 handling other services.",
      "caveat": "The start year rests on this single press source and is the weakest field in the entry; neither operator page carries a launch date.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-ca9341802a77623d",
      "field": "snippet",
      "text": "has run it through the Office of Unified Communications since 2004",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-464bd76d95226712"
      ],
      "supportNote": "The agency's own history: 'On October 1, 2004, management of the PSCC changed from a joint operation of the Metropolitan Police Department (MPD) and Fire and Emergency Medical Services (FEMS) departments to the Office of Unified Communications (OUC)', whose responsibilities 'include all 911 and 311 call-taking, as well as police, fire, and medical dispatch'.",
      "caveat": null,
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-acd95913fe8ababa",
      "field": "snippet",
      "text": "moving the case system onto a cloud platform in 2018",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-471ec368f59b9f14"
      ],
      "supportNote": "The operator's 2018 announcement records the District replacing its 'server-based 311 system' with a cloud platform handling '1.8 million calls per year' and 'more than 120 types of service channels'.",
      "caveat": "The same release claims call wait times fell 'from an average of seven minutes to 31 seconds'. That figure is deliberately not used in the entry: it is an unaudited claim in a vendor-partnered announcement.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-2819bf7a265c1742",
      "field": "snippet",
      "text": "Open311 says its standard began as an API for D.C.'s 311",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-f05480ff1d361c23",
       "src-d782e12a6203541e"
      ],
      "supportNote": "Open311's own account: 'Open311 first began with an API for Washington D.C.'s 311 system, but it became a community when the leadership of San Francisco and the support of organizations like OpenPlans, Code for America, and even the White House brought many cities, companies, and organizations together into a productive collaboration.' The July 2009 post places the District's API before the shared standard: it had by then 'released a draft for the second version of it's Open 311 API'.",
      "caveat": "Attributed to Open311, not asserted as fact by the atlas. A direct fetch of the About page returned page furniture without that paragraph; the sentence was confirmed through search, the same handling this desk gave it in the San Francisco 311 entry.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-140d37224d76eac0",
      "field": "snippet",
      "text": "by May 2010 D.C. and San Francisco were the two cities agreeing the GeoReport v2 specification together",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-1995479a7d0204ff"
      ],
      "supportNote": "Fetched directly and the strongest support for the authorship claim: 'The two cities currently driving this forward the most, San Francisco and Washington D.C., have come together to agree on and fully interoperate with a new Open311 GeoReport v2 specification.' The post also records the District accepting API key requests at api.dc.gov/key.",
      "caveat": null,
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-abc30a003194f219",
      "field": "snippet",
      "text": "The District now publishes every request as annual files back to 2009, plus a rolling last-90-days layer",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-bf562279c388efb7"
      ],
      "supportNote": "The service carries one layer per calendar year from 'All Service Requests — 2009' to 'All Service Requests — 2026', plus 'Last 90 Days', 'Snow' and 'Current Fiscal Year' — annual snapshots with a rolling recent layer, not a single live feed.",
      "caveat": null,
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-23388fa9fc25553f",
      "field": "snippet",
      "text": "the Open311 endpoint still listed for D.C. no longer answers — it timed out on 26 July 2026, while San Francisco's keeps serving records",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-b63a53c197f2a8f6"
      ],
      "supportNote": "The registry still publishes 'http://app.311.dc.gov/cwi/Open311/v2/services.xml' for jurisdiction id 'dc.gov' among the official gov-domain endpoints. The currency check run on 26 July 2026 found that URL and .../v2/requests.xml both returning HTTP 522 with Retry-After 120, twice.",
      "caveat": "No source anywhere announces a retirement or a replacement endpoint, so the entry reports the measurement and not a cause. status.open311.org/cities/dc is not usable as counter-evidence: the D.C. requests it shows are seeded dummy records titled 'Shoes & Beauty' and 'Sports & Outdoors'.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-89244efbe6ee3474",
      "field": "impact",
      "text": "440,600 service requests in calendar 2025, counted directly from the District's own published service-request layer on 26 July 2026",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-bf562279c388efb7"
      ],
      "supportNote": "Layer 18 of the service identifies itself as 'All Service Requests — 2025'; a returnCountOnly query run on 26 July 2026 returned a count of 440,600.",
      "caveat": "A count taken from the published layer by this desk, not a figure the District states in prose. It will move if the District revises the layer.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-50a7a8307868e4a9",
      "field": "lesson",
      "text": "it carries a due date and a resolution date but no field for the channel a request arrived through",
      "statementKind": "descriptive",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-bf562279c388efb7"
      ],
      "supportNote": "The layer's fields are SERVICEREQUESTID, SERVICECODE, SERVICECODEDESCRIPTION, ORGANIZATIONACRONYM, ADDDATE, RESOLUTIONDATE, SERVICEDUEDATE, SERVICEORDERSTATUS, INSPECTIONFLAG, INSPECTIONDATE, PRIORITY, WARD and coordinates — a due date and a resolution date, and no attribute recording which channel a request arrived through.",
      "caveat": "The federal catalogue record for the same data describes intake by phone, web, mail 'or via other methods of communication', so the channels exist; they are simply not published per request.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-9e88f559eeac530c",
      "field": "lesson",
      "text": "no independent audit has ever checked whether a case marked closed was actually fixed",
      "statementKind": "descriptive",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-46d8406b32c871a2",
       "src-bf562279c388efb7"
      ],
      "supportNote": "The public mapping tool shows requests 'by location, date (2 days, 7 days and 30 days) and status', updated hourly, and the underlying layer records a status and a resolution date. Neither the tool nor the data carries any verification of the closure, and no audit of D.C. closures was found in this review.",
      "caveat": "A negative finding: the absence of an audit in this review is not proof that none exists.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     }
    ],
    "sources": [
     {
      "id": "src-2ded523aa53ca31c",
      "title": "OUC — About 311 (operator)",
      "url": "https://ouc.dc.gov/page/311-about",
      "publisher": {
       "name": null,
       "domain": "ouc.dc.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "background",
      "claimRefs": [],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "Operator page for the running service: 'Call DC 311 at 311 24 hours a day, 7 days a week', open '24 hours a day, 365 days a year', with texting to 32311, @311DCGov, an online portal at 311.dc.gov, a mobile app and live chat 8AM-5:15PM. The page carries no launch date and no volume figures, which is why neither is sourced here.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-464bd76d95226712",
      "title": "OUC — History of OUC",
      "url": "https://ouc.dc.gov/page/history-ouc",
      "publisher": {
       "name": null,
       "domain": "ouc.dc.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-ca9341802a77623d"
      ],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "Establishes the operating agency and its date: 'On October 1, 2004, management of the PSCC changed from a joint operation of the Metropolitan Police Department (MPD) and Fire and Emergency Medical Services (FEMS) departments to the Office of Unified Communications (OUC)', whose 'responsibilities include all 911 and 311 call-taking, as well as police, fire, and medical dispatch'. The Unified Communications Center opened September 2006 and 'includes 911 and 311 services'. No earlier 311 launch date is given.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-dceafae72137bc56",
      "title": "TheDCLine.org — DC shifts to 311 for non-emergency police calls (31 January 2019)",
      "url": "https://thedcline.org/2019/01/31/dc-shifts-to-311-for-non-emergency-police-calls-capping-a-contentious-history-of-policy-changes/",
      "publisher": {
       "name": null,
       "domain": "thedcline.org",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-76624b68fdfac6c8"
      ],
      "temporal": {
       "publishedAt": "2019-01-31",
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "publication-and-record-dates-recorded"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The only source found that dates the launch: 'DC's 311 line was introduced in 2000', at first 'used exclusively for reporting non-emergencies requiring a police response', with 202-727-1000 handling other services. Also records the 2008 Fenty-era redirect of police calls back to 911, the 2012 911 Purity Amendment Act, and the January 2019 return of non-emergency police calls to 311, plus 1.5 million 911 calls in 2018 of which about a fifth were non-emergencies. yearStart 2000 rests on this single press source and is the weakest field in the entry.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-471ec368f59b9f14",
      "title": "OUC — Washington, DC Modernizes its 311 System on Salesforce (23 October 2018)",
      "url": "https://ouc.dc.gov/release/washington-dc-office-unified-communications-modernizes-its-311-system-salesforce",
      "publisher": {
       "name": null,
       "domain": "ouc.dc.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-acd95913fe8ababa"
      ],
      "temporal": {
       "publishedAt": "2018-10-23",
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "publication-and-record-dates-recorded"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "Dates the 2018 platform change and gives the operator's own scale figures: the District replaced its 'server-based 311 system' with a cloud platform, handling '1.8 million calls per year' and 'more than 120 types of service channels'. The same release claims call wait times fell 'from an average of seven minutes to 31 seconds'; that figure is deliberately not used in the entry, being an unaudited claim in a vendor-partnered announcement.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-f05480ff1d361c23",
      "title": "Open311 — About",
      "url": "https://www.open311.org/about/",
      "publisher": {
       "name": null,
       "domain": "open311.org",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-2819bf7a265c1742"
      ],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The origin statement the entry attributes rather than asserts: 'Open311 first began with an API for Washington D.C.'s 311 system, but it became a community when the leadership of San Francisco and the support of organizations like OpenPlans, Code for America, and even the White House brought many cities, companies, and organizations together into a productive collaboration.' Direct fetch of this page returned the page furniture without that paragraph; the sentence was confirmed via search, the same handling this desk gave it in the sf-311 entry.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-1995479a7d0204ff",
      "title": "Open311 — GeoReport v2 Established and GeoReport v1 Goes Live (6 May 2010)",
      "url": "https://www.open311.org/2010/05/open311-georeport-v2-established-georeport-v1-goes-live/",
      "publisher": {
       "name": null,
       "domain": "open311.org",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-140d37224d76eac0"
      ],
      "temporal": {
       "publishedAt": "2010-05-06",
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "publication-and-record-dates-recorded"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "Fetched directly and the strongest support for D.C.'s authorship claim: 'The two cities currently driving this forward the most, San Francisco and Washington D.C., have come together to agree on and fully interoperate with a new Open311 GeoReport v2 specification.' The post also records that D.C. was accepting API key requests at api.dc.gov/key.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-d782e12a6203541e",
      "title": "Open311 — NYC, Boston, and D.C. Make Strides to Improve 311 Services (July 2009)",
      "url": "https://www.open311.org/2009/07/nyc-boston-and-dc-make-strides-to-improve-311-services/",
      "publisher": {
       "name": null,
       "domain": "open311.org",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-2819bf7a265c1742"
      ],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "Places D.C.'s API before the shared standard: by July 2009 the District had 'released a draft for the second version of it's Open 311 API', with draft documentation hosted at octolabs.pbworks.com and the Apps for Democracy contest closing that month. A first version therefore existed before GeoReport v1 went live in May 2010.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-b297b38d3b7cff52",
      "title": "Open311 wiki — Washington D.C.",
      "url": "http://wiki.open311.org/Washington_D.C",
      "publisher": {
       "name": null,
       "domain": "wiki.open311.org",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "background",
      "claimRefs": [],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The community's own record of what D.C.'s API did: 'Metadata services to provide list of types of requests handled by 311', 'Structured service request data', 'Asynchronous submission — on submission of new ticket, API returns temporary token' and 'Anonymous submission'. Notes the District 'Ran apps for democracy contest in Spring 09' and later migrated between CRM systems.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-b63a53c197f2a8f6",
      "title": "Open311 wiki — GeoReport v2 Servers (the registry entry that no longer resolves)",
      "url": "https://wiki.open311.org/GeoReport_v2/Servers/",
      "publisher": {
       "name": null,
       "domain": "wiki.open311.org",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-23388fa9fc25553f"
      ],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The endpoint still published for the District: 'http://app.311.dc.gov/cwi/Open311/v2/services.xml', jurisdiction id 'dc.gov', XML only, listed among the official gov-domain endpoints. The currency check, run on 26 July 2026: both that URL and .../v2/requests.xml returned HTTP 522 with Retry-After 120, twice. No source found anywhere announces a retirement or a replacement endpoint, so the entry reports the measurement and not a cause. status.open311.org/cities/dc is not usable as counter-evidence: the D.C. requests it shows are seeded dummy records titled 'Shoes & Beauty' and 'Sports & Outdoors'.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-bf562279c388efb7",
      "title": "DCGIS — ServiceRequests MapServer (the open data itself)",
      "url": "https://maps2.dcgis.dc.gov/dcgis/rest/services/DCGIS_DATA/ServiceRequests/MapServer?f=json",
      "publisher": {
       "name": null,
       "domain": "maps2.dcgis.dc.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-abc30a003194f219",
       "clm-89244efbe6ee3474",
       "clm-50a7a8307868e4a9",
       "clm-9e88f559eeac530c"
      ],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "Establishes the shape of the archive and the source of the impact figure. The service carries one layer per calendar year from 'All Service Requests — 2009' to 'All Service Requests — 2026', plus 'Last 90 Days', 'Snow' and 'Current Fiscal Year' — annual snapshots with a rolling recent layer, not a single live feed. Layer 18 identifies itself as 'All Service Requests — 2025'; a returnCountOnly query on 26 July 2026 returned {'count':440600}. Its fields are SERVICEREQUESTID, SERVICECODE, SERVICECODEDESCRIPTION, ORGANIZATIONACRONYM, ADDDATE, RESOLUTIONDATE, SERVICEDUEDATE, SERVICEORDERSTATUS, INSPECTIONFLAG, INSPECTIONDATE, PRIORITY, WARD and coordinates — a due date and a resolution date, but no attribute recording which channel a request arrived through.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-7e3864816cd00609",
      "title": "DC.gov — Terms and Conditions of Use for District Data (licence position)",
      "url": "https://dc.gov/page/terms-and-conditions-use-district-data",
      "publisher": {
       "name": null,
       "domain": "dc.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "background",
      "claimRefs": [],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The District's own instrument, and the one that governs: 'Unless otherwise noted, the data on the Sites is public domain and made available with a Creative Commons CC0 1.0 Universal dedication', waiving rights worldwide including for commercial use 'all without asking permission'. Credit is requested, not required: 'While not required, we ask that you give proper credit when using data from the Sites in your own work.' District logos are carved out. The District’s catalogue metadata does not consistently match this instrument — that discrepancy is documented in the atlas entry on D.C.’s open data programme.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-7ad6e5992e4826ed",
      "title": "data.gov — 311 City Service Requests in 2026 (the conflicting licence label)",
      "url": "https://catalog.data.gov/dataset/311-city-service-requests-in-2026",
      "publisher": {
       "name": null,
       "domain": "catalog.data.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "background",
      "claimRefs": [],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The harvested federal catalogue record contradicts the District's own terms: its license field reads 'https://creativecommons.org/licenses/by/4.0', an attribution licence, where D.C.'s portal terms dedicate the same data to the public domain under CC0. Publisher is the Office of Unified Communications; last modified 21 July 2026. Description: 'Requests are received by the Office of Unified Communications (OUC) through the Mayor's Call Center (311), citizens web intake at 311.dc.gov, electronic and US mail service or via other methods of communication.'",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-46d8406b32c871a2",
      "title": "OCTO — DC 311 Mapping",
      "url": "https://octo.dc.gov/service/dc-311-mapping",
      "publisher": {
       "name": null,
       "domain": "octo.dc.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-9e88f559eeac530c"
      ],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-21",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The public-facing live view: the tool 'allows the public to see 311 service requests by location, date (2 days, 7 days and 30 days) and status', with data 'automatically accessed and updated every hour Monday to Sunday'. No Open311 or API reference appears anywhere on the page.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     }
    ],
    "coverage": {
     "claimsTotal": 10,
     "claimsMapped": 10,
     "sourcesTotal": 13,
     "sourcesUsedByClaims": 9,
     "sourcesWithPublicationDate": 3,
     "sourcesWithArchive": 0,
     "sourcesWithExactLocator": 0,
     "sourcesWithContentHash": 0
    },
    "limits": [
     "Publisher names and source languages have not yet been classified; domains are recorded without guessing.",
     "Existing source notes are descriptive locators, not page- or paragraph-exact citations.",
     "A missing archive, publication date or content hash is shown as null rather than inferred.",
     "The project-level evidence grade ranks the strongest source in the entry; it is not a truth score for every claim."
    ]
   }
  },
  {
   "id": "2026-08-21-source-dates",
   "createdAt": "2026-08-22T02:42:00Z",
   "effectiveAt": "2026-07-26",
   "changeType": "update",
   "summary": "Record the publication date of each source that states one; a source that publishes no date is marked null, and one that shows only a revision carries `updated` instead.",
   "preparedBy": {
    "type": "automation",
    "label": "AI-assisted evidence preparation",
    "humanApproved": false
   },
   "review": {
    "status": "unreviewed",
    "by": null,
    "date": null,
    "note": "Awaiting operator and domain-expert review; publication of this revision implies neither."
   },
   "changes": [
    {
     "operation": "replace",
     "path": "/snapshot/projectFingerprint",
     "summary": "Updated projectFingerprint to the current sourced project record."
    },
    {
     "operation": "replace",
     "path": "/snapshot/sources",
     "summary": "Updated sources to the current sourced project record."
    }
   ],
   "snapshotHash": "sha256:a368895d0714f0752510bf929750fa2f575a6a61d7e01363a9ae0b0a4afbd272",
   "snapshot": {
    "asOf": "2026-07-26",
    "projectFingerprint": "sha256:8286ace66e09e8e0fa38464d5cac78350d41246165c812ed7f88e2699319a363",
    "assurance": {
     "status": "unreviewed",
     "scope": "evidence-passport-revision",
     "statement": "AI-assisted structural preparation. This revision has not been reviewed by a human or subject-matter expert.",
     "machineChecks": [
      "schema",
      "publication-diff-contract",
      "material-project-fingerprint",
      "claim-text-drift",
      "source-reference-resolution",
      "complete-source-dossier",
      "snapshot-hash"
     ]
    },
    "projectState": {
     "status": "live",
     "outcome": "scaled-back",
     "evidenceGrade": "official",
     "timeline": {
      "started": 2000,
      "ended": null
     }
    },
    "governance": {
     "operator": "District of Columbia Office of Unified Communications (OUC); data published by the Office of the Chief Technology Officer (OCTO)",
     "actorTypes": [
      "city-government"
     ],
     "fundingModel": "public",
     "fundingDescription": "District of Columbia appropriations, through the Office of Unified Communications",
     "cost": null,
     "ownership": null,
     "decisionRights": null,
     "exitConditions": null
    },
    "claims": [
     {
      "id": "clm-76624b68fdfac6c8",
      "field": "snippet",
      "text": "Washington introduced a 311 line in 2000",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-dceafae72137bc56"
      ],
      "supportNote": "The only source found that dates the launch states 'DC's 311 line was introduced in 2000', at first used exclusively for reporting non-emergencies requiring a police response, with 202-727-1000 handling other services.",
      "caveat": "The start year rests on this single press source and is the weakest field in the entry; neither operator page carries a launch date.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-ca9341802a77623d",
      "field": "snippet",
      "text": "has run it through the Office of Unified Communications since 2004",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-464bd76d95226712"
      ],
      "supportNote": "The agency's own history: 'On October 1, 2004, management of the PSCC changed from a joint operation of the Metropolitan Police Department (MPD) and Fire and Emergency Medical Services (FEMS) departments to the Office of Unified Communications (OUC)', whose responsibilities 'include all 911 and 311 call-taking, as well as police, fire, and medical dispatch'.",
      "caveat": null,
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-acd95913fe8ababa",
      "field": "snippet",
      "text": "moving the case system onto a cloud platform in 2018",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-471ec368f59b9f14"
      ],
      "supportNote": "The operator's 2018 announcement records the District replacing its 'server-based 311 system' with a cloud platform handling '1.8 million calls per year' and 'more than 120 types of service channels'.",
      "caveat": "The same release claims call wait times fell 'from an average of seven minutes to 31 seconds'. That figure is deliberately not used in the entry: it is an unaudited claim in a vendor-partnered announcement.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-2819bf7a265c1742",
      "field": "snippet",
      "text": "Open311 says its standard began as an API for D.C.'s 311",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-f05480ff1d361c23",
       "src-d782e12a6203541e"
      ],
      "supportNote": "Open311's own account: 'Open311 first began with an API for Washington D.C.'s 311 system, but it became a community when the leadership of San Francisco and the support of organizations like OpenPlans, Code for America, and even the White House brought many cities, companies, and organizations together into a productive collaboration.' The July 2009 post places the District's API before the shared standard: it had by then 'released a draft for the second version of it's Open 311 API'.",
      "caveat": "Attributed to Open311, not asserted as fact by the atlas. A direct fetch of the About page returned page furniture without that paragraph; the sentence was confirmed through search, the same handling this desk gave it in the San Francisco 311 entry.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-140d37224d76eac0",
      "field": "snippet",
      "text": "by May 2010 D.C. and San Francisco were the two cities agreeing the GeoReport v2 specification together",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-1995479a7d0204ff"
      ],
      "supportNote": "Fetched directly and the strongest support for the authorship claim: 'The two cities currently driving this forward the most, San Francisco and Washington D.C., have come together to agree on and fully interoperate with a new Open311 GeoReport v2 specification.' The post also records the District accepting API key requests at api.dc.gov/key.",
      "caveat": null,
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-abc30a003194f219",
      "field": "snippet",
      "text": "The District now publishes every request as annual files back to 2009, plus a rolling last-90-days layer",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-bf562279c388efb7"
      ],
      "supportNote": "The service carries one layer per calendar year from 'All Service Requests — 2009' to 'All Service Requests — 2026', plus 'Last 90 Days', 'Snow' and 'Current Fiscal Year' — annual snapshots with a rolling recent layer, not a single live feed.",
      "caveat": null,
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-23388fa9fc25553f",
      "field": "snippet",
      "text": "the Open311 endpoint still listed for D.C. no longer answers — it timed out on 26 July 2026, while San Francisco's keeps serving records",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-b63a53c197f2a8f6"
      ],
      "supportNote": "The registry still publishes 'http://app.311.dc.gov/cwi/Open311/v2/services.xml' for jurisdiction id 'dc.gov' among the official gov-domain endpoints. The currency check run on 26 July 2026 found that URL and .../v2/requests.xml both returning HTTP 522 with Retry-After 120, twice.",
      "caveat": "No source anywhere announces a retirement or a replacement endpoint, so the entry reports the measurement and not a cause. status.open311.org/cities/dc is not usable as counter-evidence: the D.C. requests it shows are seeded dummy records titled 'Shoes & Beauty' and 'Sports & Outdoors'.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-89244efbe6ee3474",
      "field": "impact",
      "text": "440,600 service requests in calendar 2025, counted directly from the District's own published service-request layer on 26 July 2026",
      "statementKind": "quantitative",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-bf562279c388efb7"
      ],
      "supportNote": "Layer 18 of the service identifies itself as 'All Service Requests — 2025'; a returnCountOnly query run on 26 July 2026 returned a count of 440,600.",
      "caveat": "A count taken from the published layer by this desk, not a figure the District states in prose. It will move if the District revises the layer.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-50a7a8307868e4a9",
      "field": "lesson",
      "text": "it carries a due date and a resolution date but no field for the channel a request arrived through",
      "statementKind": "descriptive",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-bf562279c388efb7"
      ],
      "supportNote": "The layer's fields are SERVICEREQUESTID, SERVICECODE, SERVICECODEDESCRIPTION, ORGANIZATIONACRONYM, ADDDATE, RESOLUTIONDATE, SERVICEDUEDATE, SERVICEORDERSTATUS, INSPECTIONFLAG, INSPECTIONDATE, PRIORITY, WARD and coordinates — a due date and a resolution date, and no attribute recording which channel a request arrived through.",
      "caveat": "The federal catalogue record for the same data describes intake by phone, web, mail 'or via other methods of communication', so the channels exist; they are simply not published per request.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     },
     {
      "id": "clm-9e88f559eeac530c",
      "field": "lesson",
      "text": "no independent audit has ever checked whether a case marked closed was actually fixed",
      "statementKind": "descriptive",
      "textMode": "verbatim-from-project-record",
      "mappingStatus": "mapped",
      "sourceRefs": [
       "src-46d8406b32c871a2",
       "src-bf562279c388efb7"
      ],
      "supportNote": "The public mapping tool shows requests 'by location, date (2 days, 7 days and 30 days) and status', updated hourly, and the underlying layer records a status and a resolution date. Neither the tool nor the data carries any verification of the closure, and no audit of D.C. closures was found in this review.",
      "caveat": "A negative finding: the absence of an audit in this review is not proof that none exists.",
      "interpretation": {
       "added": false,
       "interpolation": false,
       "note": "The passport copies the published claim and its recorded source mapping without adding a conclusion."
      }
     }
    ],
    "sources": [
     {
      "id": "src-2ded523aa53ca31c",
      "title": "OUC — About 311 (operator)",
      "url": "https://ouc.dc.gov/page/311-about",
      "publisher": {
       "name": null,
       "domain": "ouc.dc.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "background",
      "claimRefs": [],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "Operator page for the running service: 'Call DC 311 at 311 24 hours a day, 7 days a week', open '24 hours a day, 365 days a year', with texting to 32311, @311DCGov, an online portal at 311.dc.gov, a mobile app and live chat 8AM-5:15PM. The page carries no launch date and no volume figures, which is why neither is sourced here.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-464bd76d95226712",
      "title": "OUC — History of OUC",
      "url": "https://ouc.dc.gov/page/history-ouc",
      "publisher": {
       "name": null,
       "domain": "ouc.dc.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-ca9341802a77623d"
      ],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "Establishes the operating agency and its date: 'On October 1, 2004, management of the PSCC changed from a joint operation of the Metropolitan Police Department (MPD) and Fire and Emergency Medical Services (FEMS) departments to the Office of Unified Communications (OUC)', whose 'responsibilities include all 911 and 311 call-taking, as well as police, fire, and medical dispatch'. The Unified Communications Center opened September 2006 and 'includes 911 and 311 services'. No earlier 311 launch date is given.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-dceafae72137bc56",
      "title": "TheDCLine.org — DC shifts to 311 for non-emergency police calls (31 January 2019)",
      "url": "https://thedcline.org/2019/01/31/dc-shifts-to-311-for-non-emergency-police-calls-capping-a-contentious-history-of-policy-changes/",
      "publisher": {
       "name": null,
       "domain": "thedcline.org",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-76624b68fdfac6c8"
      ],
      "temporal": {
       "publishedAt": "2019-01-31",
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "publication-and-record-dates-recorded"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The only source found that dates the launch: 'DC's 311 line was introduced in 2000', at first 'used exclusively for reporting non-emergencies requiring a police response', with 202-727-1000 handling other services. Also records the 2008 Fenty-era redirect of police calls back to 911, the 2012 911 Purity Amendment Act, and the January 2019 return of non-emergency police calls to 311, plus 1.5 million 911 calls in 2018 of which about a fifth were non-emergencies. yearStart 2000 rests on this single press source and is the weakest field in the entry.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-471ec368f59b9f14",
      "title": "OUC — Washington, DC Modernizes its 311 System on Salesforce (23 October 2018)",
      "url": "https://ouc.dc.gov/release/washington-dc-office-unified-communications-modernizes-its-311-system-salesforce",
      "publisher": {
       "name": null,
       "domain": "ouc.dc.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-acd95913fe8ababa"
      ],
      "temporal": {
       "publishedAt": "2018-10-23",
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "publication-and-record-dates-recorded"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "Dates the 2018 platform change and gives the operator's own scale figures: the District replaced its 'server-based 311 system' with a cloud platform, handling '1.8 million calls per year' and 'more than 120 types of service channels'. The same release claims call wait times fell 'from an average of seven minutes to 31 seconds'; that figure is deliberately not used in the entry, being an unaudited claim in a vendor-partnered announcement.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-f05480ff1d361c23",
      "title": "Open311 — About",
      "url": "https://www.open311.org/about/",
      "publisher": {
       "name": null,
       "domain": "open311.org",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-2819bf7a265c1742"
      ],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The origin statement the entry attributes rather than asserts: 'Open311 first began with an API for Washington D.C.'s 311 system, but it became a community when the leadership of San Francisco and the support of organizations like OpenPlans, Code for America, and even the White House brought many cities, companies, and organizations together into a productive collaboration.' Direct fetch of this page returned the page furniture without that paragraph; the sentence was confirmed via search, the same handling this desk gave it in the sf-311 entry.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-1995479a7d0204ff",
      "title": "Open311 — GeoReport v2 Established and GeoReport v1 Goes Live (6 May 2010)",
      "url": "https://www.open311.org/2010/05/open311-georeport-v2-established-georeport-v1-goes-live/",
      "publisher": {
       "name": null,
       "domain": "open311.org",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-140d37224d76eac0"
      ],
      "temporal": {
       "publishedAt": "2010-05-06",
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "publication-and-record-dates-recorded"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "Fetched directly and the strongest support for D.C.'s authorship claim: 'The two cities currently driving this forward the most, San Francisco and Washington D.C., have come together to agree on and fully interoperate with a new Open311 GeoReport v2 specification.' The post also records that D.C. was accepting API key requests at api.dc.gov/key.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-d782e12a6203541e",
      "title": "Open311 — NYC, Boston, and D.C. Make Strides to Improve 311 Services (July 2009)",
      "url": "https://www.open311.org/2009/07/nyc-boston-and-dc-make-strides-to-improve-311-services/",
      "publisher": {
       "name": null,
       "domain": "open311.org",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-2819bf7a265c1742"
      ],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "Places D.C.'s API before the shared standard: by July 2009 the District had 'released a draft for the second version of it's Open 311 API', with draft documentation hosted at octolabs.pbworks.com and the Apps for Democracy contest closing that month. A first version therefore existed before GeoReport v1 went live in May 2010.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-b297b38d3b7cff52",
      "title": "Open311 wiki — Washington D.C.",
      "url": "http://wiki.open311.org/Washington_D.C",
      "publisher": {
       "name": null,
       "domain": "wiki.open311.org",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "background",
      "claimRefs": [],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The community's own record of what D.C.'s API did: 'Metadata services to provide list of types of requests handled by 311', 'Structured service request data', 'Asynchronous submission — on submission of new ticket, API returns temporary token' and 'Anonymous submission'. Notes the District 'Ran apps for democracy contest in Spring 09' and later migrated between CRM systems.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-b63a53c197f2a8f6",
      "title": "Open311 wiki — GeoReport v2 Servers (the registry entry that no longer resolves)",
      "url": "https://wiki.open311.org/GeoReport_v2/Servers/",
      "publisher": {
       "name": null,
       "domain": "wiki.open311.org",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-23388fa9fc25553f"
      ],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The endpoint still published for the District: 'http://app.311.dc.gov/cwi/Open311/v2/services.xml', jurisdiction id 'dc.gov', XML only, listed among the official gov-domain endpoints. The currency check, run on 26 July 2026: both that URL and .../v2/requests.xml returned HTTP 522 with Retry-After 120, twice. No source found anywhere announces a retirement or a replacement endpoint, so the entry reports the measurement and not a cause. status.open311.org/cities/dc is not usable as counter-evidence: the D.C. requests it shows are seeded dummy records titled 'Shoes & Beauty' and 'Sports & Outdoors'.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-bf562279c388efb7",
      "title": "DCGIS — ServiceRequests MapServer (the open data itself)",
      "url": "https://maps2.dcgis.dc.gov/dcgis/rest/services/DCGIS_DATA/ServiceRequests/MapServer?f=json",
      "publisher": {
       "name": null,
       "domain": "maps2.dcgis.dc.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-abc30a003194f219",
       "clm-89244efbe6ee3474",
       "clm-50a7a8307868e4a9",
       "clm-9e88f559eeac530c"
      ],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "Establishes the shape of the archive and the source of the impact figure. The service carries one layer per calendar year from 'All Service Requests — 2009' to 'All Service Requests — 2026', plus 'Last 90 Days', 'Snow' and 'Current Fiscal Year' — annual snapshots with a rolling recent layer, not a single live feed. Layer 18 identifies itself as 'All Service Requests — 2025'; a returnCountOnly query on 26 July 2026 returned {'count':440600}. Its fields are SERVICEREQUESTID, SERVICECODE, SERVICECODEDESCRIPTION, ORGANIZATIONACRONYM, ADDDATE, RESOLUTIONDATE, SERVICEDUEDATE, SERVICEORDERSTATUS, INSPECTIONFLAG, INSPECTIONDATE, PRIORITY, WARD and coordinates — a due date and a resolution date, but no attribute recording which channel a request arrived through.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-7e3864816cd00609",
      "title": "DC.gov — Terms and Conditions of Use for District Data (licence position)",
      "url": "https://dc.gov/page/terms-and-conditions-use-district-data",
      "publisher": {
       "name": null,
       "domain": "dc.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "background",
      "claimRefs": [],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The District's own instrument, and the one that governs: 'Unless otherwise noted, the data on the Sites is public domain and made available with a Creative Commons CC0 1.0 Universal dedication', waiving rights worldwide including for commercial use 'all without asking permission'. Credit is requested, not required: 'While not required, we ask that you give proper credit when using data from the Sites in your own work.' District logos are carved out. The District’s catalogue metadata does not consistently match this instrument — that discrepancy is documented in the atlas entry on D.C.’s open data programme.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-7ad6e5992e4826ed",
      "title": "data.gov — 311 City Service Requests in 2026 (the conflicting licence label)",
      "url": "https://catalog.data.gov/dataset/311-city-service-requests-in-2026",
      "publisher": {
       "name": null,
       "domain": "catalog.data.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "background",
      "claimRefs": [],
      "temporal": {
       "publishedAt": "2025-12-29",
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "publication-and-record-dates-recorded"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The harvested federal catalogue record contradicts the District's own terms: its license field reads 'https://creativecommons.org/licenses/by/4.0', an attribution licence, where D.C.'s portal terms dedicate the same data to the public domain under CC0. Publisher is the Office of Unified Communications; last modified 21 July 2026. Description: 'Requests are received by the Office of Unified Communications (OUC) through the Mayor's Call Center (311), citizens web intake at 311.dc.gov, electronic and US mail service or via other methods of communication.'",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     },
     {
      "id": "src-46d8406b32c871a2",
      "title": "OCTO — DC 311 Mapping",
      "url": "https://octo.dc.gov/service/dc-311-mapping",
      "publisher": {
       "name": null,
       "domain": "octo.dc.gov",
       "classification": "not-classified"
      },
      "sourceType": "web-page",
      "language": "und",
      "role": "claim-evidence",
      "claimRefs": [
       "clm-9e88f559eeac530c"
      ],
      "temporal": {
       "publishedAt": null,
       "updatedAt": null,
       "sourceCheckedAt": null,
       "recordLastVerifiedAt": "2026-07-26",
       "dossierCreatedAt": "2026-08-22",
       "retrievedAt": null,
       "status": "record-date-only"
      },
      "locator": {
       "type": "descriptive-source-note",
       "value": "The public-facing live view: the tool 'allows the public to see 311 service requests by location, date (2 days, 7 days and 30 days) and status', with data 'automatically accessed and updated every hour Monday to Sunday'. No Open311 or API reference appears anywhere on the page.",
       "exact": false
      },
      "preservation": {
       "archiveUrl": null,
       "archivedAt": null,
       "contentHash": null,
       "status": "not-captured"
      }
     }
    ],
    "coverage": {
     "claimsTotal": 10,
     "claimsMapped": 10,
     "sourcesTotal": 13,
     "sourcesUsedByClaims": 9,
     "sourcesWithPublicationDate": 4,
     "sourcesWithArchive": 0,
     "sourcesWithExactLocator": 0,
     "sourcesWithContentHash": 0
    },
    "limits": [
     "Publisher names and source languages have not yet been classified; domains are recorded without guessing.",
     "Existing source notes are descriptive locators, not page- or paragraph-exact citations.",
     "A missing archive, publication date or content hash is shown as null rather than inferred.",
     "The project-level evidence grade ranks the strongest source in the entry; it is not a truth score for every claim."
    ]
   }
  }
 ]
}