{
  "metadata": {
    "language": "en",
    "last_checked": "2026-08-12",
    "item_count": 4,
    "procedure": "2026/0207/NLE",
    "procedure_status": "ongoing",
    "council_document": "ST 11890/26 ADD 1",
    "milestone": 316,
    "target": 325
  },
  "section": {
    "kicker": "Territorial Observatory",
    "title": "Which digital capabilities can be verified publicly?",
    "intro": "CATUC creates its own multi-year implementation calendar. In parallel, the Council annex of 17 July 2026 in the still-ongoing Romanian RRP amendment procedure describes an earlier Q2 2026 set of capabilities for the Territorial Observatory digital platform. We treat them as observable tests, not as automatic proof of implementation.",
    "method_note": "Each status answers a simple question: what public evidence can be observed today? “Not publicly verified” does not mean “does not exist”.",
    "procedure_note": "Important: EU procedure 2026/0207/NLE is still marked “Ongoing”. ST 11890/26 ADD 1 is a Council negotiation document, not an already adopted final replacement decision.",
    "download_label": "Download the evidence matrix"
  },
  "tests": [
    {
      "id": "pnrr-public-access",
      "title": "Public access to planning documents",
      "promise": "The platform should allow public access to spatial and territorial planning documents issued by territorial administrative units.",
      "status_key": "observed",
      "status_label": "Publicly observed",
      "evidence": [
        "DateLocale has a public planning-document register and maps for consulting compliant documents; the 5 May 2026 update explicitly describes the land-use map and improved publication interfaces."
      ],
      "caveat": "Observed public access does not by itself prove formal fulfilment of the RRP milestone.",
      "next_evidence": "An official acceptance/evaluation document tying the observed public functionality to milestone 316.",
      "source_refs": [
        "pnrr-council-2026",
        "datelocale-update-2026",
        "datelocale-register"
      ],
      "aliases": [
        "planning documents online",
        "PUG PUZ register",
        "Territorial Observatory public access"
      ]
    },
    {
      "id": "pnrr-certificates",
      "title": "Issuing urban-planning certificates",
      "promise": "The platform should give local public authorities the possibility to issue urban-planning certificates.",
      "status_key": "unverified",
      "status_label": "Not publicly verified",
      "evidence": [
        "DateLocale’s current public description lists PLANURB, participatory planning and the local transport-network register; in the public documentation reviewed for this edition we did not identify an end-to-end urban-planning-certificate issuance workflow."
      ],
      "caveat": "This is a limit of the public evidence found, not a claim that the function does not exist behind authentication or in another system.",
      "next_evidence": "A documented certificate-issuance workflow, official technical documentation, or an acceptance record demonstrating the capability.",
      "source_refs": [
        "pnrr-council-2026",
        "datelocale-about"
      ],
      "aliases": [
        "urban planning certificate online",
        "certificate issuance",
        "national platform certificate"
      ]
    },
    {
      "id": "pnrr-interoperability",
      "title": "Interoperable data",
      "promise": "Data should be available in a format interoperable with other public authorities’ databases.",
      "status_key": "partial",
      "status_label": "Partial evidence",
      "evidence": [
        "MDLPA publishes GIS templates, validation rules and standardised PUG/PUZ workflows; the validator checks common structures and geometries."
      ],
      "caveat": "Standardisation and validation enable interoperability, but do not demonstrate live data exchange with other public databases.",
      "next_evidence": "API/data-service documentation, demonstrated integration with another register, or an official interoperability acceptance record.",
      "source_refs": [
        "pnrr-council-2026",
        "datelocale-validator",
        "datelocale-technical"
      ],
      "aliases": [
        "GIS interoperability",
        "Territorial Observatory API",
        "interoperable data"
      ]
    },
    {
      "id": "pnrr-cloud",
      "title": "Government Cloud readiness",
      "promise": "The platform should be designed cloud-ready, including technical capability to support Government Cloud.",
      "status_key": "unverified",
      "status_label": "Not publicly verified",
      "evidence": [
        "The requirement is explicit in the Council document; the public DateLocale materials reviewed for this edition did not provide technical or acceptance evidence for the cloud architecture."
      ],
      "caveat": "Lack of public evidence does not prove the architecture or an internal integration is absent.",
      "next_evidence": "Published architecture, an acceptance/commissioning document, or official evidence of Government Cloud integration/readiness.",
      "source_refs": [
        "pnrr-council-2026",
        "pnrr-procedure-2026"
      ],
      "aliases": [
        "Government Cloud",
        "Territorial Observatory cloud ready",
        "government cloud"
      ]
    }
  ],
  "target_325": {
    "title": "Target 325: at least 100 documents",
    "text": "The same annex sets a Q2 2026 target of at least 100 spatial planning, urban planning and sustainable urban mobility documents published on the Territorial Observatory platform.",
    "status_label": "Formal verification needed",
    "evidence": "DateLocale already publishes a substantial volume of standardised documents. We do not mark the target as achieved merely by summing public counters: eligible categories, the reference moment and formal acceptance of the target need to be checked in the RRP assessment.",
    "source_refs": [
      "pnrr-council-2026",
      "datelocale-register"
    ]
  },
  "source_refs": [
    "pnrr-council-2026",
    "pnrr-procedure-2026",
    "datelocale-about",
    "datelocale-register",
    "datelocale-update-2026",
    "datelocale-validator",
    "datelocale-technical"
  ]
}